LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-24-2018, 08:16 AM   #1
navigium
Member
 
Registered: Aug 2014
Location: Switzerland
Distribution: Slackware, FreeBSD
Posts: 113

Rep: Reputation: 56
dhcpd exits on suspend (using rc.inet1 on current)


When I suspend my laptop I see the following messages in /var/log/messages:

Code:
Jul 24 15:07:11 darkstar dhcpcd[4042]: wlan0: carrier lost
Jul 24 15:07:11 darkstar dhcpcd[4042]: wlan0: deleting address fe80::xxxx:xxxx:xxxx:xxxx (replaced for this post)
Jul 24 15:07:11 darkstar dhcpcd[4042]: wlan0: deleting route to 192.168.43.0/24
Jul 24 15:07:11 darkstar dhcpcd[4042]: wlan0: deleting default route via 192.168.43.1
Jul 24 15:07:11 darkstar dhcpcd[4042]: wlan0: removing interface
Jul 24 15:07:11 darkstar dhcpcd[4042]: dhcpcd exited
It seems that dhcpcd decides to exit when it loses the carrier.

On resume the wifi connection comes back up, iwconfig says I'm connected but wlan0 isn't assigned an address because dhcpcd isn't running anymore.

Manually doing a
Code:
dhcpcd wlan0
reconnects.

I noticed the -L option in /etc/rc.d/rc.inet1. Could this affect the behaviour?

Thank you

-b
 
Old 07-24-2018, 01:49 PM   #2
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 955

Rep: Reputation: 494Reputation: 494Reputation: 494Reputation: 494Reputation: 494
Given that your DHCP server/router has a long lease time (days maybe) so that it won't re-allocate the give IP again while your system is suspended and that you only connect to that particular server/router, you could try to add the -p switch to the dhcpcd in /etc/rc.d/rc.inet1 for your particular problem:
Code:
/sbin/dhcpcd -L -p -t
 
Old 07-24-2018, 03:30 PM   #3
navigium
Member
 
Registered: Aug 2014
Location: Switzerland
Distribution: Slackware, FreeBSD
Posts: 113

Original Poster
Rep: Reputation: 56
Quote:
Originally Posted by abga View Post
Given that your DHCP server/router has a long lease time (days maybe) so that it won't re-allocate the give IP again while your system is suspended and that you only connect to that particular server/router, you could try to add the -p switch to the dhcpcd in /etc/rc.d/rc.inet1 for your particular problem:
Code:
/sbin/dhcpcd -L -p -t
Thank you for your reply. However, this can't be the problem for two reasons
  • The problem occurs only on my Slackware Current laptop, but on every single wifi network with every router. On the same networks resuming and reconnecting my Slackware 14.2 laptop works flawless
  • This still doesn't explain why dhcpcd would quit. It's supposed to stick around and wait for the lease to expire. After resuming the dhcpcd process is gone.

I tried anyway and as expected the -p flag for dhcpcd didn't change anything.

Last edited by navigium; 07-24-2018 at 05:28 PM. Reason: typo
 
Old 07-24-2018, 04:32 PM   #4
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 955

Rep: Reputation: 494Reputation: 494Reputation: 494Reputation: 494Reputation: 494
Sorry to hear it didn't work, I just presented a workaround for your particular issue, not a general one.
The -p flag, according to the man page, is actually instructing dhcpcd to not remove the interface configuration when it exits, that's what you presented in the log from your first post, not sure what your expectations were:
https://www.daemon-systems.org/man/dhcpcd.8.html

There might be issues with the latest network management interface/application you're using, if any.

Last edited by abga; 07-24-2018 at 04:35 PM. Reason: typo
 
Old 07-24-2018, 05:25 PM   #5
navigium
Member
 
Registered: Aug 2014
Location: Switzerland
Distribution: Slackware, FreeBSD
Posts: 113

Original Poster
Rep: Reputation: 56
Quote:
Originally Posted by abga View Post
Sorry to hear it didn't work, I just presented a workaround for your particular issue, not a general one.
The -p flag, according to the man page, is actually instructing dhcpcd to not remove the interface configuration when it exits, that's what you presented in the log from your first post, not sure what your expectations were:
https://www.daemon-systems.org/man/dhcpcd.8.html
I read up the manual on the flag before I entered it. However, the network settings are gone after a resume anyway, as far as I can tell from the 'ifconfig' output which doesn't list an IP address.

Quote:
There might be issues with the latest network management interface/application you're using, if any.
I'm not using networkmanager or wicd if that's what you mean. It's plain old rc.inet1 starting wpa_supplicant and dhcpcd.

Last edited by navigium; 07-24-2018 at 05:26 PM. Reason: Removed useless quote tag.
 
Old 07-24-2018, 05:58 PM   #6
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 955

Rep: Reputation: 494Reputation: 494Reputation: 494Reputation: 494Reputation: 494
There were some changes in the latest dhcpcd version that might be related:
https://roy.marples.name/archives/dh...s/0002131.html
https://roy.marples.name/git/dhcpcd....7b95111f3ea5e6
ftp://ftp.osuosl.org/pub/slackware/s.../ChangeLog.txt
Thu Jun 21 22:58:42 UTC 2018
n/dhcpcd-7.0.6-x86_64-1.txz: Upgraded.
Couldn't find anything else interesting in the dhcpcd recent ticket list:
https://roy.marples.name/archives/dhcpcd-discuss/

Found an older discussions about dhcpcd quitting after loosing the carrier (interface down), but there it is exiting after timing out , unlike in your report, immediately after carrier loss:
https://www.linuxquestions.org/quest...em-4175531474/

The only difference I've spotted between the 14.2 stable release and -current in /etc/dhcpcd.conf is:
Code:
# Generate SLAAC address using the Hardware Address of the interface
#slaac hwaddr
# OR generate Stable Private IPv6 Addresses based from the DUID
slaac private
Try commenting it out.
https://www.daemon-systems.org/man/dhcpcd.conf.5.html
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] slackware current, typo in new rc.inet1, also is gtk3 now required for firefox? pataphysician Slackware 23 05-24-2017 01:48 AM
Modifications to rc.inet1, rc.inet1.conf and rc.wireless hba Slackware 1 12-07-2014 03:57 AM
[SOLVED] gcc exits with "libXrender" error when building wmii for Slackware64-current markush Slackware 4 05-06-2012 04:49 AM
hostapd with dhcpd on slackware current rt2561 trumpet_tom Slackware 1 07-31-2010 08:06 AM
iwl3945 drivers: dhcpd works but not from rc.inet1! dugan Slackware 7 06-02-2008 07:15 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 02:00 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration