From owner-freebsd-net@FreeBSD.ORG  Wed Dec  9 15:23:58 2009
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 8670C10656A7
	for <freebsd-net@freebsd.org>; Wed,  9 Dec 2009 15:23:58 +0000 (UTC)
	(envelope-from cjeker@diehard.n-r-g.com)
Received: from diehard.n-r-g.com (diehard.n-r-g.com [62.48.3.9])
	by mx1.freebsd.org (Postfix) with ESMTP id F04328FC22
	for <freebsd-net@freebsd.org>; Wed,  9 Dec 2009 15:23:57 +0000 (UTC)
Received: (qmail 30969 invoked by uid 1001); 9 Dec 2009 15:23:56 -0000
Date: Wed, 9 Dec 2009 16:23:56 +0100
From: Claudio Jeker <cjeker@diehard.n-r-g.com>
To: freebsd-net@freebsd.org
Message-ID: <20091209152356.GA31932@diehard.n-r-g.com>
Mail-Followup-To: Claudio Jeker <cjeker@diehard.n-r-g.com>,
	freebsd-net@freebsd.org
References: <4B1FB7A2.2020801@tomjudge.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4B1FB7A2.2020801@tomjudge.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: carp(4) and VRRP on the same segment
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Dec 2009 15:23:58 -0000

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.

-- 
:wq Claudio