From owner-freebsd-net@FreeBSD.ORG Sat Mar 3 22:44:06 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 BDC2D16A401 for ; Sat, 3 Mar 2007 22:44:06 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 3622113C491 for ; Sat, 3 Mar 2007 22:44:06 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 2593 invoked from network); 3 Mar 2007 22:16:24 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 3 Mar 2007 22:16:24 -0000 Message-ID: <45E9FA3C.5030404@freebsd.org> Date: Sat, 03 Mar 2007 23:44:12 +0100 From: Andre Oppermann User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Yar Tikhiy References: <45E8BB39.9030602@incunabulum.net> <20070303213406.GA40430@comp.chem.msu.su> In-Reply-To: <20070303213406.GA40430@comp.chem.msu.su> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Sat, 03 Mar 2007 22:44:06 -0000 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. > Thank you for paying attention to that! -- Andre