keepalived does not honor use_vmac directive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
keepalived (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
As of precise/quantal, keepalived does not honor the use_vmac directive. Expected behavior is for keepalived to synthesize a virtual mac address to go along with the virtual IP address. This is important in situations where systems do not accept gratuitous ARP as a means to fail over a virtual IP address.
I have built a version against the latest upstream (1.2.7), which does honor the use_vmac directive as expected. below follows an example of how it should look (see 6:):
1: lo: <LOOPBACK,
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,
link/ether 08:00:27:36:14:4f brd ff:ff:ff:ff:ff:ff
inet 192.168.4.105/24 brd 192.168.4.255 scope global eth0
inet6 fe80::a00:
valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,
link/ether a2:20:3b:c0:e0:1a brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
6: vrrp.90@eth0: <BROADCAST,
link/ether 00:00:5e:00:01:5a brd ff:ff:ff:ff:ff:ff
inet 192.168.4.200/32 scope global vrrp.90
inet6 fe80::200:
valid_lft forever preferred_lft forever
Changed in keepalived (Ubuntu): | |
status: | Incomplete → New |
importance: | Undecided → Medium |
I should add that this didn't work quite as expected - although the mac addresses were set as expected, the interfaces in question did not respond to pings or function as HA IPs. So there may be more going on.