Hi guys, I have a laptop, where I mostly use my wireless - but I have both. I use the wireless-config ebuild from the forums (0.2.4) and using it, I simply copy (or symlink) /etc/init.d/net.eth0 to /etc/init.d/net.wlan0. The problem I'm seeing, is that if I start f.ex. /etc/init.d/ntp-client (and other services too) that need net - they insist on starting net.eth0 - even though net.wlan0 is started. this leads me to conclude that starting the net.wlan0 for some reason does not fullfill the net dependency, which it should. Reproducible: Always Steps to Reproduce: 1. be sure to have two interfaces net.eth0 net.if0 2. stop net.eth0 3. start ntp-client Actual Results: net.eth0 is started. Expected Results: ntp-client should just have started - as net.if0 was up. (my net.wlan0).
I have the same problem. I have found a hard coded net.eth0 in /var/lib/init.d, but it is dynamicly created and I don't know where...
Is net.eth0 in your default runlevel? Also, check the setting of RC_NET_STRICT_CHECKING in /etc/conf.d/rc as this controlls the behaviour you are seeing.
Hi - RF_NET_STRICT_CHECKING was set to no (default) which should mean one net started is enough. I have the same problem with the fact that I use ifplugd (because eth0 is not always cabled, and Gentoo currently can't be told to "start eth0 if there's a cable - otherwise try wlan0" which is IMHO a big lack :( When I restart f.ex. slapd on my portable (or any other service that depends on net) it INSISTS on starting my net.wlan0 (as it is the only one set to be started upon boot - eth0 is handled by ifplugd). Problem is - when I'm using eth0 - my net.wlan0 is usually not up - and so I have to wait for that to timeout :( I'd like portage to resolve the dependency so EITHER net.eth0 or net.wlan0 resolves the dependency on net.. AFAIK this is a missing feature in Gentoo's init system. Perhaps the best way was to make ifplugd work with gentoo's init system - or make gentoos init handle the above mentioned "start this if this=true else try this".
This may be fixed by bug #77839 - however you will need baselayout-1.11.8 (any -rx version included) to apply the patch
Fixed by baselayout-1.11.9
