Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dev is set on virtual_ipaddress when use_vmac is enabled #215

Closed
ghost opened this issue Jun 2, 2020 · 2 comments
Closed

dev is set on virtual_ipaddress when use_vmac is enabled #215

ghost opened this issue Jun 2, 2020 · 2 comments

Comments

@ghost
Copy link

ghost commented Jun 2, 2020

Context:

<%= ip %> dev <%= @virtual_ipaddress_int || @interface %>

The current template does set dev for a virtual_ipaddress in any case. But this is not needed nor in every case desired.

Given the (working excerpt) of a VI:

vrrp_instance VI_1 {
  interface                 lan0
  state                     BACKUP
  virtual_router_id         1
  priority                  100
  advert_int                1
  garp_master_delay         0

  garp_master_refresh       60


  use_vmac
  vmac_xmit_base

  virtual_ipaddress {
    10.100.2.254/32
  }

  mcast_src_ip 10.100.2.252
}

The virtual_ipaddress will be assigned to vrrp.1@lan0.

But this puppet module sets

  • if using only interface
  virtual_ipaddress {
    10.100.2.254/32 dev lan0
  }
  • and virtual_ipaddress_int to vrrp.1@lan0 does not work as intended.

I propose to just drop adding dev to the virtual_ipaddress except the user explicit stats it. At least on Linux, the kernel handles this just fine.

@ghost
Copy link
Author

ghost commented Jun 2, 2020

Sorry I published the draft and now need to edit the issue multiple times.

@ghost
Copy link
Author

ghost commented Jun 2, 2020

Pardon me, this is already fixed in https://github.com/voxpupuli/puppet-keepalived/tree/v2.2.0

@ghost ghost closed this as completed Jun 2, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants