2.3.3-RELEASE-p1IPv6 CARP issue (dual master)
I've got trouble with a setup where two HA pfSenses get dual master for IPv6 after 10 minute or so. Short after reboot of the slave everything seems to be fine, some minutes later the slave sets himself to master for the IPv6 CARP addresses. However IPv4 CARP addresses on the same Interfaces are running fine. This problem seems to exist since the upgrade from 2.3.3 to 2.3.3-p1.
To confirm the idea that this problem depends on the release I upgraded a working second HA-CARP pair of pfSenses and shortly after the upgrade the situation on the second pair is the same. A dual master IPv6 CARP setup where IPv4 remains working. Any bugs that roughly match the description for BSD or pfSense I found are a few years old, and the solutions don't seem to work.
I should mention, that both setups are in a virtual KVM-environment but worked before the update. I have updates waiting for two physical pfSenses, but don't want to loose IPv6 on them, so I can't test it with them.
Anybody else recognized some different behavior of IPv6 CARP since 2.3.3-RELEASE-p1?