On Fri, 17 Dec 2004, Joel CARNAT wrote: > 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).
You're lucky, Chris Pascoe just fixed it in -current. Go try it! ;-)
