Added by Chris Buechler over 11 years ago. Updated over 11 years ago.
100%
Description
radvd.conf where a CARP IP is chosen results in an invalid config file, as it omits the interface entirely (where it used to be something like wan_vipX).
working on this
The conf file problem is fixed. Since CARP no longer has its own interface, we'll need to start/stop radvd along with CARP status if CARP VIPs are selected in the RA config.
To Renato since he's starting for the day soon and I'm running short on time for the day.
Renato: test setup available, bounce through 172.27.44.25 to 192.0.2.202 (primary) and .203 (secondary). See DHCPv6 config on LAN.
Applied in changeset commit:a693440176e8bd4a783a9ccb75d2cd57629b5699.
Applied in changeset commit:52b5a22363d34bbd621b9eb555cf849782318dda.
this is mostly fixed. Where CARP goes to backup status, it seems fine. But if the CARP VIPs are completely gone, it fails to stop radvd (appears to just restart it). If you use the "temporarily disable CARP" button under Status>CARP, it breaks. Other things, like OpenVPN client instances bound to CARP VIPs, stop fine in the same circumstance.
also noticed some gettext in 'function get_carp_interface_status' that could break this and just seems wrong in general.
return gettext("MASTER");
return gettext("BACKUP");
return gettext("INIT");
running short on time for today, back to Renato to finish up the last of this.
Applied in changeset commit:8e24d1dacd80fd539cc9dd6a5f0a7c8953bcffd0.
Applied in changeset commit:9b527a7931795466ab7286f0caadd7bef082d002.
fixed
Also available in: Atom