On Fri, 17 Dec 2004, Joel CARNAT wrote: > my test is pinging 192.168.10.200 (the carp interface). > it's OK until I "brconfig bridge0 up". > from then, I can see (tcpdump) "echo request" on bge0 and bge1 but nowhere > else (and no ack anywhere). > then I "brconfig bridge0 down" and the ping works back. > > that's why I'm pretty sure the bug is the bridge (or @least the way I > configured it ;)... > I thought, maybe, setting the bridge confuses carp because paquets are > first forwarded from bge0 to bge1 and as carp0 is linked to bge0, it > doesn't work on the paquet (yes, I already tried to set carp0 on bge1 > and same error occurs).
It's something I'm working on at the moment. The bridge does not recognize that the CARP MAC address is destined for itself (bge0), and tries to bridge it to no avail. At the moment there is no simple solution.
