Date: Thu, 19 Mar 2009 00:32:47 +0100 From: Stefan Bethke <stb@lassitu.de> To: Sam Leffler <sam@freebsd.org> Cc: bz@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org>, jamie@freebsd.org, Andrew Thompson <thompsa@freebsd.org> Subject: Re: ifconfig bridge0 does not list bridge data? Message-ID: <2F12B7AC-BCB3-4E2D-AFD9-C59E6C8A7BA4@lassitu.de> In-Reply-To: <49C17DDB.5030800@freebsd.org> References: <4C8BEF98-B6EF-4B26-9649-F0666A837230@lassitu.de> <20090318225422.GC79077@citylink.fud.org.nz> <49C17DDB.5030800@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 19.03.2009 um 00:03 schrieb Sam Leffler: > Andrew Thompson wrote: >> On Wed, Mar 18, 2009 at 11:47:39PM +0100, Stefan Bethke wrote: >> >>> I've just set up a new home router with current. I'm using >>> if_bridge(4) to bridge an OpenVPN connection to the local >>> ethernet. Although everything seems to be working fine, ifconfig >>> does not show bridge parameters: >>> >>> # ifconfig bridge0 >>> bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric >>> 0 mtu 1500 >>> ether 3a:30:67:76:af:05 >>> inet 10.0.0.1 netmask 0xffffffc0 broadcast 10.0.0.63 >>> >>> In a VMware sandbox with a 10-day old -current, I get the expected >>> output: >>> >>> # ifconfig bridge0 >>> bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric >>> 0 mtu 1500 >>> ether ca:26:3c:e3:7e:00 >>> inet 10.0.0.14 netmask 0xffffffc0 broadcast 10.0.0.63 >>> id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 >>> maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 >>> root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 >>> member: em0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> >>> ifmaxaddr 0 port 1 priority 128 path cost 20000 >>> member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP> >>> ifmaxaddr 0 port 4 priority 128 path cost 2000000 >>> >>> I also have two vlans hanging off em0. >>> >>> Any ideas? >>> >> >> This means that one of the BRDGGCACHE, BRDGGTO or BRDGPARAM ioctls >> has >> failed so bridge_status() in sbin/ifconfig/ifbridge.c exits early >> (the >> function that prints the info you are missing). Is it possible your >> sources are out of sync? If you look at it with kdump then the actual >> ioctl these are wrapped in is called SIOCGDRVSPEC >> >> > Try backing out r189864. That appears to be the culprit. I've just rebuilt ifconfig, and without this change, it displays the bridge info. Stefan -- Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2F12B7AC-BCB3-4E2D-AFD9-C59E6C8A7BA4>