[SOLVED] Wired network doesn't reconnect after suspend
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi all, I use pm-suspend to put my work laptop to sleep at the end of the day. When it resumes, I have to manually tell the wired network to reconnect.
It connects as expected while booting, and wicd automatically reconnects to known wireless networks when resuming. I've told wicd to "Always switch to wired connection when available" and "Automatically reconnect on connection loss", but still it does not.
Manually telling wicd to connect to the wired network connects as expected.
Do you have the link down after resume? (= buggy driver?)
Do you use dhcp and your dhcp client terminated running after suspend? (= buggy dhcpcd setup?)
The link appears to still be up after resuming, although admittedly I'm not 100% sure how to check. ifconfig recognizes eth0, however it shows an inet6 IP address only.
However, after resume it appears that dhcpcd is not running anymore. After reconnecting via wicd it has been started again. Any ideas as to why it might not start after resume?
Thanks!
---------- Post added 09-06-13 at 09:50 ----------
...
However, after resume it appears that dhcpcd is not running anymore. After reconnecting via wicd it has been started again. Any ideas as to why it might not start after resume?
...
I have the same problem with dhcpcd. When my link goes down briefly, dhcpcd terminates. The author of dhcpcd says I must have explicitly told dhcpcd to exit on link down. Because the word "told" is non-technical, I can't figure out what he means.
So now I'm running dhcpcd with the "-K" option. Not an elegant solution but it works.
I have the same problem with dhcpcd. When my link goes down briefly, dhcpcd terminates. The author of dhcpcd says I must have explicitly told dhcpcd to exit on link down. Because the word "told" is non-technical, I can't figure out what he means.
So now I'm running dhcpcd with the "-K" option. Not an elegant solution but it works.
Thanks for the tip. Where would be the appropriate place to do that? I'm assuming I should edit one of the files in /etc/rc.d. Which one? It appears rc.inet1, rc.6 and rc.0 all start dhcpcd. Is it possible to do this as an option in one of the conf files, or do I actually need to edit a script?
Because you are using wicd, the rc.inet1 stuff has no effect. Probably you can try the "/etc/dhcpcd.conf" file. Please "man dhcpcd.conf" and search for "nolink" (without quotes).
If you choose to use rc.inet1 instead of wicd, then with the patch here you can add options to dhcpcd.
Because you are using wicd, the rc.inet1 stuff has no effect. Probably you can try the "/etc/dhcpcd.conf" file. Please "man dhcpcd.conf" and search for "nolink" (without quotes).
If you choose to use rc.inet1 instead of wicd, then with the patch here you can add options to dhcpcd.
Thanks for the tip. I've added "nolink" to dhcpcd.conf and it doesn't seem to have helped
Also, if the issue is with dhcpcd, wouldn't it affect all networking? Why does it reconnect to wireless networks, but not wired?
Sorry, I've been away from wicd for quite some time. Looks like the wicd deamon killed dhcpcd.
Did you set "Always switch to wired connection when available" in wicd Preference?
Yes, but upon rechecking my settings I noticed the "Wired Autoconnect Settings" section. "Use default profile on wired autoconnect" was selected. I switched it to "Use last used profile on wired autoconnect", and it appears to work now!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
