We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
virtual_ipaddress
use_vmac
Context:
puppet-keepalived/templates/vrrp_instance.erb
Line 139 in 4bdd57a
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:
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.
vrrp.1@lan0
But this puppet module sets
interface
virtual_ipaddress { 10.100.2.254/32 dev lan0 }
virtual_ipaddress_int
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.
The text was updated successfully, but these errors were encountered:
Sorry I published the draft and now need to edit the issue multiple times.
Sorry, something went wrong.
Pardon me, this is already fixed in https://github.com/voxpupuli/puppet-keepalived/tree/v2.2.0
No branches or pull requests
Context:
puppet-keepalived/templates/vrrp_instance.erb
Line 139 in 4bdd57a
The current template does set
dev
for avirtual_ipaddress
in any case. But this is not needed nor in every case desired.Given the (working excerpt) of a
VI
:The
virtual_ipaddress
will be assigned tovrrp.1@lan0
.But this puppet module sets
interface
virtual_ipaddress_int
tovrrp.1@lan0
does not work as intended.I propose to just drop adding
dev
to thevirtual_ipaddress
except the user explicit stats it. At least on Linux, the kernel handles this just fine.The text was updated successfully, but these errors were encountered: