From owner-freebsd-net@FreeBSD.ORG Sun Mar 4 06:10:22 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0ADB616A403 for ; Sun, 4 Mar 2007 06:10:22 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id 56E5C13C474 for ; Sun, 4 Mar 2007 06:10:21 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.4) with ESMTP id l246AILK047312; Sun, 4 Mar 2007 09:10:19 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.4/Submit) id l246ADaV047307; Sun, 4 Mar 2007 09:10:13 +0300 (MSK) (envelope-from yar) Date: Sun, 4 Mar 2007 09:10:13 +0300 From: Yar Tikhiy To: Andre Oppermann Message-ID: <20070304061012.GF40430@comp.chem.msu.su> References: <45E8BB39.9030602@incunabulum.net> <20070303213406.GA40430@comp.chem.msu.su> <45E9FA3C.5030404@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45E9FA3C.5030404@freebsd.org> User-Agent: Mutt/1.5.9i Cc: freebsd-net@freebsd.org, Bruce M Simpson Subject: Re: CARP behaviour 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, 04 Mar 2007 06:10:22 -0000 On Sat, Mar 03, 2007 at 11:44:12PM +0100, Andre Oppermann wrote: > Yar Tikhiy wrote: > >On Sat, Mar 03, 2007 at 12:03:05AM +0000, Bruce M Simpson wrote: > >>During testing of M_PROMISC I noticed a couple of issues with our CARP. > >> > >>1. carp doesn't seem to maintain input/output statistics on its ifnet. > > > >This should be OK. A carp(4) interface is just a place for CARP > >settings to live. No real traffic passes through it. > > > >>2. carp doesn't seem to detect that the underlying route to the subnet > >> its address is exposed on changed to another interface. > > > >I seem to recollect that I ran into this issue, too. Of course, > >it's a bug. CARP apparently caches the old route forever. It > >should track such a change if it doesn't yet. We have a sort of > >notification for the event, don't we? The userland has the routing > >socket for that, but I don't remember about the kernel. > > We shouldn't cache route pointers anywhere anymore. It has been completely > removed from the PCBs and things like gif and others. Sounds like a good way to go, too! :-) Thanks! -- Yar