ng_ether and interface naming (bug or feature?)

Gleb Smirnoff glebius at FreeBSD.org
Fri Sep 8 10:28:54 PDT 2006


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


More information about the freebsd-net mailing list