Ethernet Connection doesn't work if cable is connected AFTER boot

[lighthouse_keeper]

Hi, this is my first post here. I have this problems with kubuntu.

If I connect the ethernet cable AFTER the boot up the ethernet interface doesn't work and there is no way (for example ifconfig) to make it work.
If I start the OS with the cable already connected there is no problem and the DHCP works perfectly. What is the problem?

My Notebook is an Acer Aspire 9420 with Kubuntu Feisty Fawn.

Tell me if I have to post other infos, i'm totally a newbie. And Sorry for my poor English

thx

[penguin.ch]

Re: Ethernet Connection doesn't work if cable is connected AFTER boot

How about sudo /etc/init.d/networking restart ...?

[lighthouse_keeper]

Re: Ethernet Connection doesn't work if cable is connected AFTER boot

How about sudo /etc/init.d/networking restart ...?

No way. Here is the output on the terminal:

* Reconfiguring network interfaces...                     There is already a pid file /var/run/dhclient.eth0.pid with pid 4366
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 [url]http://www.isc.org/sw/dhcp/[/url]

Listening on LPF/eth0/00:16:d3:4e:be:8c
Sending on  LPF/eth0/00:16:d3:4e:be:8c
Sending on  Socket/fallback
DHCPRELEASE on eth0 to 10.0.1.6 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
There is already a pid file /var/run/dhclient.eth1.pid with pid 4394
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 [url]http://www.isc.org/sw/dhcp/[/url]

Listening on LPF/eth1/00:18:de:6e:46:9b
Sending on  LPF/eth1/00:18:de:6e:46:9b
Sending on  Socket/fallback
DHCPRELEASE on eth1 to 10.0.1.6 port 67
send_packet: Network is unreachable
send_packet: please consult README file regarding broadcast address.
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 [url]http://www.isc.org/sw/dhcp/[/url]

Listening on LPF/eth0/00:16:d3:4e:be:8c
Sending on  LPF/eth0/00:16:d3:4e:be:8c
Sending on  Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
There is already a pid file /var/run/dhclient.eth1.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 [url]http://www.isc.org/sw/dhcp/[/url]

Listening on LPF/eth1/00:18:de:6e:46:9b
Sending on  LPF/eth1/00:18:de:6e:46:9b
Sending on  Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
eth2: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.eth2.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 [url]http://www.isc.org/sw/dhcp/[/url]

SIOCSIFADDR: No such device
eth2: ERROR while getting interface flags: No such device
eth2: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up eth2.
ath0: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.ath0.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 [url]http://www.isc.org/sw/dhcp/[/url]

SIOCSIFADDR: No such device
ath0: ERROR while getting interface flags: No such device
ath0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up ath0.
wlan0: ERROR while getting interface flags: No such device
There is already a pid file /var/run/dhclient.wlan0.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 [url]http://www.isc.org/sw/dhcp/[/url]

SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up wlan0.
                                     [ OK ]

[RenegadeAbe]

Re: Ethernet Connection doesn't work if cable is connected AFTER boot

try:

sudo ifdown eth0
then
sudo ifup eth0

[Cristiano]

Re: Ethernet Connection doesn't work if cable is connected AFTER boot

Hi,

Maybe this applicantion help you: http://0pointer.de/lennart/projects/ifplugd/

[insmod]

Re: Ethernet Connection doesn't work if cable is connected AFTER boot

ifdown eth0

then

ifup eth0

you must use sudo so:

sudo ifdown eth0

sudo ifup eth0

----- eth0 is the ethernet card listed in if config

[congyiwu]

Re: Ethernet Connection doesn't work if cable is connected AFTER boot

if you do ifconfig eth0 down/up, afterwards, you might (or might not) have to kill and rerun dhclient. That's more or less what I had to do in archlinux, but then again archlinux uses dhcpcd instead of dhclient.

Maybe going to knetworkmanager, configure manually, and disabling/enabling eth0 in that dialog could help...?