Comment 4 for bug 213937

Revision history for this message
Robert (robrwo) wrote :

Looking at /var/log/syslog, it appears that ifplugd is being run for my network devices, but it's failing.
Right after the kernel startup (machinename and mac addresses changed):

Apr 28 21:18:26 machinename kernel: [ 2.732334] udev: renamed network interface eth1_rename to eth0
Apr 28 21:18:26 machinename ifplugd.agent[11836]: Invoking ifplugd for eth1
Apr 28 21:18:26 machinename ifplugd(eth1)[11910]: ifplugd 0.28 initializing.
Apr 28 21:18:26 machinename ifplugd(eth1)[11910]: Warning: Could not get interface address.
Apr 28 21:18:26 machinename kernel: [ 2.901159] ADDRCONF(NETDEV_UP): eth1: link is not ready
Apr 28 21:18:27 machinename ifplugd(eth1)[11910]: Using interface eth1/01:23:45:67:89:ac with driver <ipw2200> (version: 1.2.2kmprq)
Apr 28 21:18:27 machinename ifplugd(eth1)[11910]: Initialization complete, link beat not detected.
Apr 28 21:18:27 machinename dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 11256
Apr 28 21:18:27 machinename dhclient: killed old client process, removed PID file
Apr 28 21:18:27 machinename dhclient: Internet Systems Consortium DHCP Client V3.0.6
Apr 28 21:18:27 machinename dhclient: Copyright 2004-2007 Internet Systems Consortium.
Apr 28 21:18:27 machinename dhclient: All rights reserved.
Apr 28 21:18:27 machinename dhclient: For info, please visit http://www.isc.org/sw/dhcp/
Apr 28 21:18:27 machinename dhclient:
Apr 28 21:18:27 machinename dhclient: Listening on LPF/eth0/01:23:45:67:89:ab
Apr 28 21:18:27 machinename dhclient: Sending on LPF/eth0/01:23:45:67:89:ab
Apr 28 21:18:27 machinename dhclient: Sending on Socket/fallback
Apr 28 21:18:27 machinename dhclient: DHCPRELEASE on eth0 to 192.168.1.1 port 67
Apr 28 21:18:27 machinename dhclient: send_packet: Network is unreachable
Apr 28 21:18:27 machinename dhclient: send_packet: please consult README file regarding broadcast address.
Apr 28 21:18:27 machinename kernel: [ 3.324396] ADDRCONF(NETDEV_UP): eth0: link is not ready

Could this be a udev-related problem?