| View previous topic :: View next topic |
| Author |
Message |
JensK
n00b
Joined: 04 Aug 2005
Posts: 29
|
 Posted: Thu Aug 04, 2005 9:20 am Post subject: net.eth1 starts automatically when eth1 associates to an AP |
 |
|
I am in the process of setting up my laptop (HP nc6120) with Gentoo. I use the ipw2200-1.0.3 driver for my wireless adapter eth1.
What bothers me is that as soon as eth1 associates with any access point, the init script /etc/init.d/net.eth1 is started. I already tried to stop the driver from associating with an AP by using "modprobe ipw2200 associate=0" when loading the module, but this seems not to have any effect for me. So I would at least like to stop net.eth1 from starting (because having the script started messes up the logic of a network profile script I have written).
It is not linked in any runlevel. In fact, this happens whenever the interface comes up, not only during boot, and I tried booting with a minimal configuration, so I can rule out dependencies from other scripts. I set RC_NET_STRICT_CHECKING to "lo" since I don't want scripts depending on net trying to bring up interfaces when I am on the road with no network connection available.
The relevant parts of my /etc/conf.d/net:
| Code: | config_eth1=( "192.168.2.202 netmask 255.255.255.0" )
modules=( "wpa_supplicant" )
wpa_supplicant_eth1="-Dipw"
wpa_timeout_eth1=60 |
I noticed a similar effect lately on my server, where I have a custom bridge script ("lan-wlan-bridge") bringing up a bridge interface br0. There was an old script net.br0 lying around (not used any more), and everytime I started my script and br0 came up, the system would start /etc/init.d/net.br0 all by itself in the background.
I can only ascertain WHEN the script is started by putting something like "echo NOW >/dev/vc/1" into the start() function of the script, otherwise no output is seen. Thus, I couldn't yet locate which process is bringing up the scripts.
Does anyone know how I can disable this functionality? |
|
| Back to top |
|
 |
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
| Posted: Thu Aug 04, 2005 9:32 am Post subject: |
|
|
It's probably hotplug.
You can stop hotplug from doing this by removing the /etc/hotplug/net.agent script |
|
| Back to top |
|
|
JensK
n00b
Joined: 04 Aug 2005
Posts: 29
|
| Posted: Thu Aug 04, 2005 9:49 am Post subject: |
|
|
Thanks for the quick answer! Seems you're right, just tried it.
I never thought about hotplug as a possible cause because I didn't even start the hotplug script. Just now, upon closer investigation, I just noticed that /etc/init.d/hotplug does nothing at all to enable or disable hotplugging. |
|
| Back to top |
|
|
UberLord
Retired Dev
Joined: 18 Sep 2003
Posts: 6835
Location: Blighty
|
| Posted: Thu Aug 04, 2005 10:42 am Post subject: |
|
|
Correct.
The "hotplug" program (which can also be udevsend) is setup in /sbin/rc which works it all out from the programs you have installed. |
|
| Back to top |
|
|
|
Networking & Security
