From owner-freebsd-stable@FreeBSD.ORG Thu Aug 7 17:27:06 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2261E106570E for ; Thu, 7 Aug 2008 17:27:06 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from pele.citylink.co.nz (pele.citylink.co.nz [202.8.44.226]) by mx1.freebsd.org (Postfix) with ESMTP id D31A88FC13 for ; Thu, 7 Aug 2008 17:27:05 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by pele.citylink.co.nz (Postfix) with ESMTP id C53F82BD94; Fri, 8 Aug 2008 04:57:18 +1200 (NZST) X-Virus-Scanned: Debian amavisd-new at citylink.co.nz Received: from pele.citylink.co.nz ([127.0.0.1]) by localhost (pele.citylink.co.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C3DKAj5VRwtY; Fri, 8 Aug 2008 04:57:13 +1200 (NZST) Received: from citylink.fud.org.nz (unknown [202.8.44.45]) by pele.citylink.co.nz (Postfix) with ESMTP; Fri, 8 Aug 2008 04:57:13 +1200 (NZST) Received: by citylink.fud.org.nz (Postfix, from userid 1001) id E2E6A11430; Fri, 8 Aug 2008 04:57:12 +1200 (NZST) Date: Thu, 7 Aug 2008 09:57:12 -0700 From: Andrew Thompson To: Pete French Message-ID: <20080807165712.GA37969@citylink.fud.org.nz> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Cc: stable@freebsd.org Subject: Re: should looking at an interface with 'ifconfig' trigger a change ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Aug 2008 17:27:06 -0000 On Thu, Aug 07, 2008 at 05:27:53PM +0100, Pete French wrote: > I have a very odd problem here - two interfaces bundled using lagg > in 'failover' mode, so one interface is active and the other not being > used. if the carrier drops on the active one I expect it to > failover, but it doesnt. > > ...until I type 'ifconfig bce0' to look at the status of the interface > which has gone down. At which point it fails over properly! > > This is most odd - how can simply looking at the config of an > interface trigger the failover ? It wont fail over otherwise either - you > can leave it as long as you like and lagg wont realise that the active > has gone down. > > The interfaces here are 'bce' by the way, if that make a difference.... The bce driver is not properly generating link state events. Andrew