Date: Fri, 8 Sep 2006 21:28:51 +0400 From: Gleb Smirnoff <glebius@FreeBSD.org> To: Denis Peplin <den@FreeBSD.org> Cc: freebsd-net@FreeBSD.org Subject: Re: ng_ether and interface naming (bug or feature?) Message-ID: <20060908172851.GM40020@FreeBSD.org> In-Reply-To: <45011B31.1080103@FreeBSD.org> References: <45011B31.1080103@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 08, 2006 at 11:26:41AM +0400, Denis Peplin wrote: D> I have found, that changing interface names from rc.conf D> can break ng_ether when it loaded from loader.conf or D> compiled into kernel. D> D> For example, when mpd is used as PPPoE server, rc.conf D> contain ifconfig_fxp0_name="net1" and /boot/loader.conf D> contain ng_ether_load="YES", the mpd logs: D> D> exec: /sbin/ifconfig net1 up D> Cannot send a netgraph message: net1::No such file or directory D> Error in creation ng_pppoe node on net1: D> D> There only two workarounds: avoid using interface naming, or D> loading ng_ether after renaming interfaces. D> D> Is this a bug or a feature, that just wait somebody to document it? This is probably a bug, not a feature. We have several PRs about this. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060908172851.GM40020>