Date: Thu, 19 Mar 2009 16:42:24 -0600 From: Jamie Gritton <jamie@FreeBSD.org> To: FreeBSD Current <freebsd-current@FreeBSD.org> Cc: "Bjoern A. Zeeb" <bz@FreeBSD.org>, Andrew Thompson <thompsa@FreeBSD.org>, Stefan Bethke <stb@lassitu.de>, Sam Leffler <sam@FreeBSD.org> Subject: Re: ifconfig bridge0 does not list bridge data? Message-ID: <49C2CA50.8000406@FreeBSD.org> In-Reply-To: <20090319072312.S67075@maildrop.int.zabbadoz.net> 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> <20090319072312.S67075@maildrop.int.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Bjoern A. Zeeb wrote: > On Thu, 19 Mar 2009, Stefan Bethke wrote: >>>> 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. A fix for this is forthcoming, probably to the kernel and not to ifconfig. In the meantime, backing out r189864 will work fine. - Jamie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49C2CA50.8000406>