LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Network Can't be reloaded after resume from hibernation (https://www.linuxquestions.org/questions/linux-networking-3/network-cant-be-reloaded-after-resume-from-hibernation-938682/)

snowweb 04-07-2012 07:44 PM
Network Can't be reloaded after resume from hibernation
 
After I resume from hibernation, the network is not automatically restored. I can live with that (although it's not what I expect from a polished OS), but no matter what I try from the command line, I can't bring up eth0 until I have physically unplugged the cable from the back of the machine and then plugged it back in again.

After doing that, I can then reload networking and I get an IP address successfully.

This is the output before unplugging the cable:
Code:
peter@peter-accent-ubuntu:~$ sudo /etc/init.d/networking force-reload
 * Reconfiguring network interfaces...                                                  There is already a pid file /var/run/dhclient.eth0.pid with pid 25699
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/00:03:0d:76:a1:8e
Sending on  LPF/eth0/00:03:0d:76:a1:8e
Sending on  Socket/fallback
DHCPRELEASE on eth0 to 192.168.0.1 port 67
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/00:03:0d:76:a1:8e
Sending on  LPF/eth0/00:03:0d:76:a1:8e
Sending on  Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
ssh stop/waiting
ssh start/running, process 25906
I've tried the following;
sudo ifdown eth0; sudo ifup eth0
sudo /etc/init.d/networking force-reload

Beyond that, I would like to be able to programmatically unplug the cable and replug it again. Not sure how to do this? What if I remove the module from the kernel and then reload it? Is that possible? Would that have the same effect as physically unplugging it? Should I even be having to do this? Any advise would be greatly appreciated.

My specs are:
Code:
$ uname -a
Linux peter-accent-ubuntu 2.6.35-32-generic #68-Ubuntu SMP Tue Mar 27 17:01:54 UTC 2012 i686 GNU/Linux
On a Accent 9115 laptop.
Using KDE Desktop (although I think I had the same problem when I was using Gnome.

This has been the problem ever since I installed Ubuntu 10.10 back in 2010.

Relevant lspci output (I think):
Code:
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] 191 Gigabit Ethernet Adapter (rev 02)
Let me know if you need any more info.

Many thanks.

Peter

dklovedoctor 09-16-2012 02:24 PM
Quote:
Originally Posted by snowweb (Post 4647421)
After I resume from hibernation, the network is not automatically restored. I can live with that (although it's not what I expect from a polished OS), but no matter what I try from the command line, I can't bring up eth0 until I have physically unplugged the cable from the back of the machine and then plugged it back in again.

After doing that, I can then reload networking and I get an IP address successfully.

This is the output before unplugging the cable:
Code:
peter@peter-accent-ubuntu:~$ sudo /etc/init.d/networking force-reload
 * Reconfiguring network interfaces...                                                  There is already a pid file /var/run/dhclient.eth0.pid with pid 25699
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/00:03:0d:76:a1:8e
Sending on  LPF/eth0/00:03:0d:76:a1:8e
Sending on  Socket/fallback
DHCPRELEASE on eth0 to 192.168.0.1 port 67
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/00:03:0d:76:a1:8e
Sending on  LPF/eth0/00:03:0d:76:a1:8e
Sending on  Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
ssh stop/waiting
ssh start/running, process 25906
I've tried the following;
sudo ifdown eth0; sudo ifup eth0
sudo /etc/init.d/networking force-reload

Beyond that, I would like to be able to programmatically unplug the cable and replug it again. Not sure how to do this? What if I remove the module from the kernel and then reload it? Is that possible? Would that have the same effect as physically unplugging it? Should I even be having to do this? Any advise would be greatly appreciated.

My specs are:
Code:
$ uname -a
Linux peter-accent-ubuntu 2.6.35-32-generic #68-Ubuntu SMP Tue Mar 27 17:01:54 UTC 2012 i686 GNU/Linux
On a Accent 9115 laptop.
Using KDE Desktop (although I think I had the same problem when I was using Gnome.

This has been the problem ever since I installed Ubuntu 10.10 back in 2010.

Relevant lspci output (I think):
Code:
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] 191 Gigabit Ethernet Adapter (rev 02)
Let me know if you need any more info.

Many thanks.

Peter
This is the solution to your problem!
http://forums.opensuse.org/english/g...e-suspend.html

snowweb 09-16-2012 09:53 PM
[solved]
 
Actually, I upgraded to 12.04 in April 2012 and since then this has not been a problem. It's been working perfectly for me since then.

Thanks.


All times are GMT -5. The time now is 10:50 AM.