I'm not really sure what your problem is? When you have more than one VHID on an interface you have an error in your design.
My understanding was, for each virtual CARP address I need an unique VHID. If I want to have multiple WAN IPs handled each as a virtual IP I need unique VHID groups for each of them?Thats how I did it in the past. And I did not reuse the VHID for an other interface. When I use the same VHID Groups on WAN for two different addresses it leads to problems like IPsec tunnels do not work because the first address of each VHID group is used as identifier not the configured one. Just an example. The reason I ask is I stumbled over a fucked up configuration where VHID where used multiple times. On WAN it came to the behaviour that IPSec did not work as configured and choose the wrong identifier. While cleaning the configuration the way it worked for me in the past I asked myself if the unique identifier only needs to be unique per interface or system wide.
Quote from: mimugmail on March 24, 2020, 06:52:34 amI'm not really sure what your problem is? When you have more than one VHID on an interface you have an error in your design.Or IPv6 running. Version 19.x allowed to use same VHID for IPv4 and IPv6. Used it to force common failover of both ip families.20.X does not allow use of same VHID for IPv4 and IPv6. So need to waste more (double) VHIDs. I hope it just must be unique per interface. Else with many vlans, ipv6 and other vrrp/carp devices in network that must not overlap, 256 VHIDs are depleted pretty wuick.
The VHID for each virtual IP address must be unique across the broadcast domain of the network interface.
Quote from: hbc on March 24, 2020, 09:07:32 amQuote from: mimugmail on March 24, 2020, 06:52:34 amI'm not really sure what your problem is? When you have more than one VHID on an interface you have an error in your design.Or IPv6 running. Version 19.x allowed to use same VHID for IPv4 and IPv6. Used it to force common failover of both ip families.20.X does not allow use of same VHID for IPv4 and IPv6. So need to waste more (double) VHIDs. I hope it just must be unique per interface. Else with many vlans, ipv6 and other vrrp/carp devices in network that must not overlap, 256 VHIDs are depleted pretty wuick.Really? Do you have a link to the issue why this was changed?
since the internal key is per interface+vhid it won't support overlap