Date: Thu, 19 Mar 2009 07:24:20 +0000 (UTC) From: "Bjoern A. Zeeb" <bz@FreeBSD.org> To: Stefan Bethke <stb@lassitu.de> Cc: Sam Leffler <sam@freebsd.org>, Andrew Thompson <thompsa@freebsd.org>, jamie@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: ifconfig bridge0 does not list bridge data? Message-ID: <20090319072312.S67075@maildrop.int.zabbadoz.net> In-Reply-To: <2F12B7AC-BCB3-4E2D-AFD9-C59E6C8A7BA4@lassitu.de> References: <4C8BEF98-B6EF-4B26-9649-F0666A837230@lassitu.de> <20090318225422.GC79077@citylink.fud.org.nz> <49C17DDB.5030800@freebsd.org> <2F12B7AC-BCB3-4E2D-AFD9-C59E6C8A7BA4@lassitu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 19 Mar 2009, Stefan Bethke wrote: Hi, >>> 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. Heh. ok. I had tested that as well with a few setups but obviously not enough. I'll look into this. -- Bjoern A. Zeeb The greatest risk is not taking one.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090319072312.S67075>