From owner-freebsd-net@FreeBSD.ORG Sun Dec 16 01:53:38 2007 Return-Path: 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 1CCC716A419; Sun, 16 Dec 2007 01:53:38 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.freebsd.org (Postfix) with ESMTP id 0016E13C455; Sun, 16 Dec 2007 01:53:37 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 4F7667A81C; Sat, 15 Dec 2007 20:53:37 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Sat, 15 Dec 2007 20:53:37 -0500 X-Sasl-enc: i0i26hJIk+C1cE7IweXItrQkKeDv1sFLAc7IRl1mE99g 1197770017 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 8AEFEC1D6; Sat, 15 Dec 2007 20:53:36 -0500 (EST) Message-ID: <4764851F.1000304@FreeBSD.org> Date: Sun, 16 Dec 2007 01:53:35 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.6 (X11/20070928) MIME-Version: 1.0 To: Max Laier References: <47628E11.7030803@tomjudge.com> <4762AC1E.3030101@FreeBSD.org> <200712142030.14728.max@love2party.net> In-Reply-To: <200712142030.14728.max@love2party.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Tom Judge , freebsd-net , freebsd-pf@freebsd.org Subject: Re: Spurious error from i[pf]_carp X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Dec 2007 01:53:38 -0000 Max Laier wrote: > Alternatively you could change IPPROTO_CARP in netinet/in.h to another > unused protocol number. This is really the preferred way of dealing with > mixed CARP and VRRP environments as the CARP packets might in turn > irritate the VRRP routers, too. > This sounds like a common use case. Perhaps there is motivation for making the protocol number used by CARP a loader tunable? [I'd really like it if we had a kernel API for adding the virtual MAC addresses to ifnet too, then again I'd like the cheat for infinite chocolate fudge sundaes in life, bed and breakfast at The Savoy with my choice of actress, etc] > /* no comment */ > No disrespect to anyone intended, just that CARP does duplicate the functionality of VRRP. It's worth reiterating that this is what happens when software patents are allowed to creep in to the nuts and bolts of the operational Internet -- and thus, CARP was born, and thus Tom runs into the issue he has seen. later BMS