| View previous topic :: View next topic |
| Author |
Message |
widremann
Veteran
Joined: 14 Mar 2005
Posts: 1314
|
 Posted: Sun Feb 05, 2006 6:55 pm Post subject: How do you make ifplugd work? |
 |
|
It never brings up any interfaces. It starts and then nothing ever happens. I have to bring up the interfaces manually.
I'm using the default settings and I did etc-update. I added ifplugd to my default runlevel and removed net.eth0. I see the message saying that ifplugd is starting and I see where it say that it is running it for interface eth0, but, eth0 never comes up.
I have never ever gotten ifplugd to work, so I'm wondering why this is happening, especially with default settings. It seems like it should "just work" for something as straightforward as an ethernet interface. But it isn't. Any help? |
|
| Back to top |
|
 |
chunderbunny
Veteran
Joined: 31 May 2004
Posts: 1281
Location: 51°24'27" N, 0°57'15" W
|
| Posted: Sun Feb 05, 2006 10:58 pm Post subject: |
|
|
It depends which version of baselayout you are using. I'm not sure whether the "stable" baselayout has ifplugd incorporated,but I know the unstable version has. Anyway, for the newer baselayout you will need the following:
An /etc/conf.d/net file which is similar t this: | Code: | | config_eth0=( "dhcp" ) |
No other information is necessary (in fact you could have a blank /etc/conf.d/net file but init will spit warnings at you if you do). Next, configure /etc/conf.d/ifplugd so that it contains the line This will make ifplugd control all wired network interfaces which are found in /proc/net/dev. Next, remove ifplugd AND net.eth0 from your runlevels. Your network interfaces will be brought up at the same time as net.lo.
And that should be it! Note that init will no longer explicitly state that your eht0 device is being started, you will get a message about "selecting the best interface" when net.lo starts. You may also need coldplug in your boot runlevel to make sure that the appropriate kernel modules have been loaded before net.lo tries to start. |
|
| Back to top |
|
|
widremann
Veteran
Joined: 14 Mar 2005
Posts: 1314
|
| Posted: Mon Feb 06, 2006 12:08 am Post subject: |
|
|
| I'm using the older (1.11.x) releases of baselayout. Does it not work with earlier versions? If so, I'll just go back to net.eth0 and wait until the new baselayout is stable. |
|
| Back to top |
|
|
mlybarger
Guru
Joined: 04 Sep 2002
Posts: 480
|
| Posted: Tue Feb 14, 2006 4:31 am Post subject: |
|
|
i have been having similar issues. i just want my networking to work with the "best" network interface that's available, and i don't want to have to manually type something when i plug in / come across a particular available interface. i still want the flexability to tell it not to connect to a network i can't get an ip address from (blacklist certain ap's).
for the longest time, my one laptop would constantly connect to my neighbours ap. tonight, i upgraded to the 1.12 baselayout and ran dispatch-conf to pull in the numerous config changes. so far, it seems to be respecting my blacklist. that's very nice and a step further.
here's my problem. i had my laptop is connected to a wired network when it boots. it got an ip just fine and was "connected". then i unplugged the wire, and soon the net.eth0 showed no ip address. next i plugged in the wi-fi card (usb card). it obtained an ip address from _my_ ap (big whoot's there). a few pings to test it out, and i then unplug the wifi card. the net.wlan0 soon does not have an ip address. good still. i then plug in my wired connection again. wait... wait... wait... and it never gets an ip address again. |
|
| Back to top |
|
|
|
Networking & Security
