If an interface participating in a CARP cluster becomes a member of a bridge,
it loses the ability to communicate on the CARP IP when it becomes the master.
System: FreeBSD lorax.kcilink.com 10.0-RELEASE-p6 FreeBSD 10.0-RELEASE-p6 #2 r267868: Wed Jun 25 09:49:14 EDT 2014 firstname.lastname@example.org:/u/lorax1/usr10/obj/u/lorax1/usr10/src/sys/KCI64 amd64
ifconfig em0 alias vhid 205 advskew 100 pass dnsprv 192.168.97.97/23
-> on other host, bring down CARP or set the advskew to 200 to allow this
host to become master.
at the point, you are able to ping and access services on 192.168.97.97 just
Restore the other member as the CARP master by adjusting advskew on the other
host back to below 100.
Now, do this:
ifconfig tap0 create
ifconfig bridge0 create
ifconfig bridge0 addm tap0 addm em0 up
And again, bring this host to be the master by adjusting advskew on the other
host > 100. The CARP member of em0 will show it is MASTER, but you cannot
ping or access 192.168.97.97 on this machine at all.
none known. workaround is to avoid using a bridge, but I need that for a bhyve
Over to maintainers.
Is this still a problem? Is it related to 200319?