From owner-freebsd-net@FreeBSD.ORG Mon Mar 6 02:07:19 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28D7216A420; Mon, 6 Mar 2006 02:07:19 +0000 (GMT) (envelope-from freebsdnik@j2d.lam.net.au) Received: from ichimail.justnet.info (ichiban.broadband.sublimeip.com [203.217.17.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id A34FF43D45; Mon, 6 Mar 2006 02:07:18 +0000 (GMT) (envelope-from freebsdnik@j2d.lam.net.au) Received: from localhost (unknown [127.0.0.1]) by ichiban-mailfilter.justnet.info (Postfix) with ESMTP id B637368A7B; Mon, 6 Mar 2006 13:07:16 +1100 (EST) Received: from ichimail.justnet.info ([127.0.0.1]) by localhost (ichiban.justnet.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 37894-07; Mon, 6 Mar 2006 13:07:15 +1100 (EST) Received: from [192.168.0.231] (dhcp1 [192.168.0.231]) by ichimail.justnet.info (Postfix) with ESMTP id C00CA688F7; Mon, 6 Mar 2006 13:07:10 +1100 (EST) Message-ID: <440B994F.9020401@j2d.lam.net.au> Date: Mon, 06 Mar 2006 13:07:11 +1100 From: Nik Lam User-Agent: Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: Andrew Thompson References: <440683E2.8000009@j2d.lam.net.au> <440B4759.6010106@j2d.lam.net.au> <20060305204051.GA44857@heff.fud.org.nz> <440B6644.3050800@j2d.lam.net.au> <20060306002341.GB44857@heff.fud.org.nz> In-Reply-To: <20060306002341.GB44857@heff.fud.org.nz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at ichiban.justnet.info Cc: freebsd-net@freebsd.org Subject: Re: configuring if_bridge with stp at boot in /etc/rc.conf 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: Mon, 06 Mar 2006 02:07:19 -0000 Andrew Thompson wrote: > > It may be possible that the link-up notification is not happening for > em2 or we are somehow missing the first one. > > Can you try this patch and see if stp on em2 kicks into life. Can you > also test unplugging/plugging the network cable for em2 and see if you > get link change messages in your dmesg. > > > Andrew > That patch has done the job Andrew. Thanks. Under the patched kernel, if I log in straight away after boot up, at first I see em1 listening and em2 disabled. About 5 or 10 seconds later em2 goes into listening state and some time after that forwarding across the bridge starts. As an aside in case anyone notices, I just got a sinking feeling that I'd given you a red herring - I realised that there was an error in my rc.conf: ifconfig_bridge0="addm em1 stp em1 addm em2 stp em2 ifpriority em1 10 ifpriority em2 20 ifpathcost em1 10 ifpathcost 20 hellotime 2 maxage 5 fwddelay 6 priority 10 up" I left out the "em2" in defining the path cost for that member interface. However, I was able to reproduce the problem even after I corrected the rc.conf and booted using the unpatched kernel. Using the patched kernel it works either way. Regards, Nik