Re: Network adapter management in laptop

[Bob Alexander <bob@ngi.it>]

Jochen Schulz wrote:
> If I were you I would double check that ifplugd starts up correctly at
> boot time and then experiment with running it from the command line
> after boot.

Jochen and other friends thank you very much.

I might have "accused" ifplugd without having done enough prob.
determination. :( Unfortunately I am still stuck in an unconfigured 
network situation.

Here is the situation. I had a system with hotplug/udev and ifplugd
which worked just fine. After the latest sid sw upgrade (about 10 days
ago) when boot finishes I am left with an eth0 without IP configuration.
I need to manually run ifup eth0 and the dhclient starts just fine and
configures IP.

At boot ifplugd (0.26-2) process is up and running and if I manually
unplug/plug the cable I have ifplugd doing it's job. It seems like
during boot this is not working ...

Follows some more debug data.

Thank you for any help,
Bob

t40:/home/bob# cat /etc/network/interfaces
auto lo
iface lo inet loopback
iface eth0 inet dhcp

Situation at boot end (I am in Gnome desktop by now):
bob@t40:~$ sudo ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:09:6B:53:12:F1
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:487 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:53249 (52.0 KiB)  TX bytes:0 (0.0 b)
          Base address:0x8000 Memory:c0220000-c0240000
bob@t40:~$ ps aux |grep ifplugd
root      2760  0.0  0.0   1604   524 ?        S<s  09:31   0:00 
/usr/sbin/ifplugd -i eth0 -q -f -u0 -d10 -w -I

I can wait forever but eth0 is not brought up.

I now unplug the cable, wait 10 secs, replug the cable and wait 10 secs:

bob@t40:~$ sudo ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:09:6B:53:12:F1
          inet addr:9.132.182.56  Bcast:9.132.182.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:655 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:73638 (71.9 KiB)  TX bytes:692 (692.0 b)
          Base address:0x8000 Memory:c0220000-c0240000

Good ifplugd in itself works fine. Why is it not triggering during boot ????

Here are some lines extracted from /var/log/boot
Tue Apr 12 11:31:43 2005: Loading e1000 module.
Tue Apr 12 11:31:48 2005: Setting up 
resolvconf.../dev/shm/resolvconf/...done.
Tue Apr 12 11:31:48 2005: Running 0dns-down to make sure resolv.conf is 
ok...done.
Tue Apr 12 11:31:48 2005: Setting up networking...done.
Tue Apr 12 11:31:48 2005: Starting hotplug subsystem:
Tue Apr 12 11:31:51 2005:      e1000: already loaded
Tue Apr 12 11:31:53 2005: Setting up IP spoofing protection: rp_filter.
Tue Apr 12 11:31:53 2005: Configuring network interfaces...done.
Tue Apr 12 11:31:53 2005: Starting "Shorewall firewall": done.
Tue Apr 12 09:32:04 2005: Starting Network Interface Plugging 
Daemon:Sorry, there is already an instance of ifplugd for eth0 running.
Tue Apr 12 09:32:04 2005:  eth0.

Note that I have always had the warning about ifplugd already loaded 
even when things worked just fine.