Comment 16 for bug 93576

Revision history for this message
eppy 1 (choppy121212) wrote :

Killing those two processes (and nm-applet, just in case) solved the problem for me too. I could then do 'sudo ifup eth0' to get my network back.

before killing:
chris@promax:~$ sudo ifup eth0
ifup: interface eth0 already configured
$ sudo ifdown eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 17362
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:08:a1:5f:14:7b
Sending on LPF/eth0/00:08:a1:5f:14:7b
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.2 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
$ sudo ifdown eth0
ifdown: interface eth0 not configured
$ sudo ifdown eth0
ifdown: interface eth0 not configured
$ sudo ifup eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

after killing:
$ sudo ifup eth0
There is already a pid file /var/run/dhclient.eth0.pid with pid 134993416
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:08:a1:5f:14:7b
Sending on LPF/eth0/00:08:a1:5f:14:7b
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPOFFER from 192.168.1.2
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.2
bound to 192.168.1.101 -- renewal in 33169 seconds.