carp(4) and VRRP on the same segment

[Tom Judge]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Claudio Jeker wrote:
> On Wed, Dec 09, 2009 at 02:43:46PM +0000, Tom Judge wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi,
>>
>> We have had some issues with running both carp and VRRP in the same
>> physical segment.  It has mostly caused issues with the embedded devices
>> running VRRP.  One other side affect is the hugely verbose output on the
>> FreeBSD side where carp is complaining about corrupt PDU's.
>>
>> To work around this I changed the carp protocol number from the VRRP
>> allocated number to an unassigned number (241). Simple patches can be
>> found here:
>> http://svn.tomjudge.com/freebsd/patches/carp-vrrp-interop/
>>
>>
>> Maybe this can be made into a sysctl for carp, so that the administrator
>> can select a different protocol number at boot/runtime if desired.
>>
> 
> I think you will hit the other issues with this.
> Normaly it is sufficent to ensure that the carp vhid and the VRRP vrid are
> not equal.
> 

This works for the most part but I have seen one device in particular
barf when it receives a carp frame.

This change also significantly reduces the logging output from the VRRP
and CARP devices.

I understand that there are issues with migration, and interop out there
but this is a useful change to reduce junk log messages and random
crashes of embedded vrrp devices.

Tom
- --
TJU13-ARIN
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLH8PuAAoJEMSwVS7lr0OdZp0H/3cqKL/5qCPXew6rGCMDbdtC
KHuGnAPuPyp3pY3c3jBrMEWNLR/IsymQjAhm/61mGLHERK0gKixNkgespO0Zr/gz
fTstlSc/LUC1FfpVVzSDkASsrE7fU+pZu3g9RGjsKLyT/YwMx2GsA4NjONMLDRe3
iTIElTUEwKxr2h1T8eDiQLN//bOxkZm+BXHKOUnJmLw1NEyZXVHhh0ixnhAYFHpf
0378mxE0sPPBiTzBD1ClwmHPV6pzb/mSjzg7zZrmxjVqybO4Adi/KkLBiwyci36X
89wGmaOzuu23LDhZHgRwuFm/Rd1rIrPwOZEZj68R4nh8EJ7GylF6doBUFUz8X/o=
=S+YK
-----END PGP SIGNATURE-----