[SOLVED] WiFi loss upon resume?

gegechris99 · 09-14-2021, 03:08 PM

Quote:

Originally Posted by marav

works after suspend/resume ?

it works for me ...
dhcpcd is running

Code:

dhcpcd   28476  0.0  0.0   3084  1376 ?        S    18:02   0:00 dhcpcd: [master] [ip4] [ip6]
root     28477  0.0  0.0   3224  1400 ?        S    18:02   0:00  \_ dhcpcd: [privileged actioneer]
dhcpcd    4192  0.0  0.0   3224   128 ?        S    21:35   0:00  |   \_ dhcpcd: [BPF ARP] wlan0 192.168.111.15
dhcpcd   28478  0.0  0.0   3004   204 ?        S    18:02   0:00  \_ dhcpcd: [network proxy]
dhcpcd   28479  0.0  0.0   3000    60 ?        S    18:02   0:00  \_ dhcpcd: [control proxy]

Sorry, it doesn't work for me.

EDIT: I'm using a wired connection not wifi.

Before suspend:

Code:

$ps aux | grep dhcpcd
dhcpcd    5608  0.0  0.0   3012  2404 ?        S    21:49   0:00 dhcpcd: eth0 [ip4]
root      5609  0.0  0.0   3016  2048 ?        S    21:49   0:00 dhcpcd: [privileged actioneer] eth0 [ip4]
dhcpcd    5610  0.0  0.0   3000   312 ?        S    21:49   0:00 dhcpcd: [control proxy] eth0 [ip4]
dhcpcd    5624  0.0  0.0   3016   320 ?        S    21:49   0:00 dhcpcd: [network proxy] 192.168.0.1

After suspend:

Code:

$ps aux | grep dhcpcd
dhcpcd    5608  0.0  0.0   3168  2404 ?        S    21:49   0:00 dhcpcd: eth0 [ip4]
root      5609  0.0  0.0   3016  2052 ?        S    21:49   0:00 dhcpcd: [privileged actioneer] eth0 [ip4]
dhcpcd    5610  0.0  0.0   3000   312 ?        S    21:49   0:00 dhcpcd: [control proxy] eth0 [ip4]
dhcpcd    5805  0.0  0.0   3016   320 ?        S    21:59   0:00 dhcpcd: [BPF ARP] eth0 192.168.0.1
dhcpcd    5806  0.0  0.0   3016   320 ?        S    21:59   0:00 dhcpcd: [BPF BOOTP] eth0

My configuration:

Code:

$grep wheel /etc/group
wheel:x:10:root

$cat /etc/NetworkManager/conf.d/00-dhcp-client.conf 
[main]
# Choose a DHCP client below. Upstream recommends internal, but results may vary.
# dhcpcd is the DHCP client usually used by Slackware. The --noconfigure
# option must be used or the network will not return after suspend/resume:
dhcp=dhcpcd 
# dhclient is the ISC reference DHCP client, part of the dhcp package:
#dhcp=dhclient
# This is a simple DHCP client that is built into NetworkManager:
#dhcp=internal

$grep wheel /etc/dhcpcd.conf 
controlgroup wheel

marav · 09-14-2021, 03:14 PM

Quote:

Originally Posted by LuckyCyborg

Your unprivileged user is part of "wheel" group? That's not that usual on Slackware.

nope

Code:

blackstar :: ~ » grep wheel /etc/group
wheel:x:10:root

marav · 09-14-2021, 03:16 PM

Quote:

Originally Posted by gegechris99

Sorry, it doesn't work for me.

Before suspend:

Code:

$ps aux | grep dhcpcd
dhcpcd    5608  0.0  0.0   3012  2404 ?        S    21:49   0:00 dhcpcd: eth0 [ip4]
root      5609  0.0  0.0   3016  2048 ?        S    21:49   0:00 dhcpcd: [privileged actioneer] eth0 [ip4]
dhcpcd    5610  0.0  0.0   3000   312 ?        S    21:49   0:00 dhcpcd: [control proxy] eth0 [ip4]
dhcpcd    5624  0.0  0.0   3016   320 ?        S    21:49   0:00 dhcpcd: [network proxy] 192.168.0.1

I've just checked
It doesn't work for me too, if ipv6 is disabled

When enabled, it works

Code:

dhcpcd   28476  0.0  0.0   3084  1296 ?        S    18:02   0:00 dhcpcd: [master] [ip4] [ip6]
root     28477  0.0  0.0   3224  1404 ?        S    18:02   0:00  \_ dhcpcd: [privileged actioneer]
dhcpcd   19443  0.0  0.0   3224   132 ?        S    22:15   0:00  |   \_ dhcpcd: [BPF ARP] wlan0 192.168.111.15

That's a lot of "if" to get anywhere...
we always come back to "internal" in the end

EDIT :
it works when ipv6 is set to :
auto
auto (address only)
local link

It doesn't work when set to:
ignore

IMPORTANT NOTE :
dhcvp v6 must be disabled on the server (or router/gateway, anything that provide ipv6 address). if not, it doesn't work

allend · 09-15-2021, 09:36 AM

I am wondering whether there is a problem with NetworkManager shutting down dhcpcd when connections are closed.

I am writing from my netbook that I normally run with 'dhcp=dhclient' set in /etc/NetworkManager/conf.d/00-dhcp-client.conf, as it plays well with my USB modem. Prior to performing upgrades, I often drop to run level 3, log in as root, use 'nmcli radio wifi on' to activate my wireless interface and use 'nmtui' to establish an internet connection. After upgrades, I reverse that process, before rebooting if required.

Looking at this thread, I checked the output of 'ps ax | grep dhc' after establishing a connection and again after dropping the connection. As expected, dhclient processes were running after establishing a connection and were absent when the connection was closed.

Changing to 'dhcp=dhcpcd' in /etc/NetworkManager/conf.d/00-dhcp-client.conf, I note that dhcpcd processes were running after establishing a connection but, _unexpectedly_, were present when the connection was closed.

With 'dhcp=internal' in /etc/NetworkManager/conf.d/00-dhcp-client.conf, there is no output from 'ps ax | grep dhc'.

BenCollver · 09-15-2021, 10:11 AM

WIFI was working for me on resume until this week when i updated -current. My last update was early in August. Reverting to the old kernel didn't fix it. I am using iwlwifi. I recall installing updates to kernel-firmware, dnsmasq, dhcpcd, and NetworkManager. I haven't been able to get back online unless i reboot. Otherwise it connects to wifi but fails to set up a route. Haven't had the time to troubleshoot further yet.

pghvlaans · 09-15-2021, 11:44 AM

I'm not certain this applies for your situation, but people have had the most luck using "dhcp=internal" or "dhcp=dhclient" in "/etc/NetworkManager/conf.d/00-dhcp-client.conf" recently. It's probably worth a try.

marav · 09-15-2021, 12:25 PM

I think that at this level of the thread, it is no longer useful to vote for a solution
dhcp=internal is definitely the right option

LuckyCyborg · 09-15-2021, 12:36 PM

Quote:

Originally Posted by marav

I think that at this level of the thread, it is no longer useful to vote for a solution
dhcp=internal is definitely the right option

Well, I do not think that's the right option, because I have 3 (three) USB dongles model Asus USB-AC51 with driver native on kernel (mt7610u) which are unable to connect at all to router with this option.

https://www.asus.com/Networking-IoT-...eries/USBAC51/

However, I agree that's the best solution - let's say... the lesser evil.

marav · 09-15-2021, 05:42 PM

If someone is interested

I cloned & compiled git repo of dhcpcd
https://github.com/NetworkConfiguration/dhcpcd.git

Since I'm pretty sure this is the issue :
https://roy.marples.name/git/dhcpcd/...6c8fddae300503

Code:

blackstar :: ~ » dhcpcd --version
dhcpcd 9.99.0
Copyright (c) 2006-2021 Roy Marples
Compiled in features: INET ARP ARPing IPv4LL INET6 DHCPv6 AUTH PRIVSEP

I'll wait and see how it goes over time, but for now it's fine with the slackware dhcpcd.conf untouched

marav · 09-16-2021, 02:55 AM

dhcpcd slackbuild with PRIVSEP=no doesn't work

Code:

root:~/ # dhcpcd --version
dhcpcd 9.4.0
Copyright (c) 2006-2020 Roy Marples
Compiled in features: INET ARP ARPing IPv4LL INET6 DHCPv6 AUTH

Code:

root:~/ # /etc/rc.d/rc.networkmanager restart
Stopping NetworkManager: stopped
Starting NetworkManager daemon:  /usr/sbin/NetworkManager

Code:

root:~/ # cat /etc/resolv.conf 
# Generated by NetworkManager
search blackstar.local
nameserver fd0f:ee:b0::1

No nameserver v4

But, with the git version (just with ./configure):

Code:

root:~/ # dhcpcd --version
dhcpcd 9.99.0
Copyright (c) 2006-2021 Roy Marples
Compiled in features: INET ARP ARPing IPv4LL INET6 DHCPv6 AUTH PRIVSEP

Code:

root:~/ # cat /etc/resolv.conf
# Generated by NetworkManager
search blackstar.local
nameserver 80.67.169.12
nameserver 80.67.169.40
nameserver fd0f:ee:b0::1

Issue #44
https://github.com/NetworkConfigurat...cpcd/issues/44

Code:

while debugging some weird issues with IPv6 name reolution with my home router

corrected by (as I said in my previous post):
https://roy.marples.name/git/dhcpcd/...6c8fddae300503

PJBrs · 09-16-2021, 09:35 AM

I compiled dhcpcd from git as well, using cflags and build options from the original slackbuild, but without patches. I can confirm that I now have an IPv4 address after resume when I use NetwerkManager with dhcpcd. Previously, I only got an IPv6 address, and couldn't reach sites that only used IPv4. Problem solved, except, I also end up with a couple of zombies. I suspended three times:

Code:

# ps aux | grep dhc
dhcpcd    7323  0.0  0.0      0     0 ?        Z    16:26   0:00 [dhcpcd] <defunct>
dhcpcd    7486  0.0  0.0      0     0 ?        Z    16:26   0:00 [dhcpcd] <defunct>
dhcpcd    7995  0.0  0.0      0     0 ?        Z    16:27   0:00 [dhcpcd] <defunct>
dhcpcd    8863  0.0  0.0   3016  2504 ?        S    16:29   0:00 dhcpcd: wlan0 [ip4]
root      8864  0.0  0.0   3020  2128 ?        S    16:29   0:00 dhcpcd: [privileged proxy] wlan0 [ip4]
dhcpcd    8865  0.0  0.0   3008   304 ?        S    16:29   0:00 dhcpcd: [control proxy] wlan0 [ip4]
dhcpcd    8872  0.0  0.0   3020   316 ?        S    16:29   0:00 dhcpcd: [BPF ARP] wlan0 192.168.0.23
dhcpcd    8891  0.0  0.0   3020   316 ?        S    16:29   0:00 dhcpcd: [BOOTP proxy] 192.168.0.23
root      8952  0.0  0.0   4008  2200 pts/3    S+   16:29   0:00 grep dhc

Compiled dhcpcd as follows:

Code:

git clone https://github.com/NetworkConfiguration/dhcpcd.git
cd dhcpcd/
CFLAGS="-O2 -fPIC" LIBDIRSUFFIX="64" PRIVSEP_OPTIONS="--enable-privsep --privsepuser=dhcpcd" ./configure --prefix=/usr --libdir=/usr/lib${LIBDIRSUFFIX} --sbindir=/sbin --sysconfdir=/etc --dbdir=/var/lib/dhcpcd --libexecdir=/lib/dhcpcd --mandir=/usr/man --rundir=/run $PRIVSEP_OPTIONS
make
mkdir /tmp/dhcpcd
make install DESTDIR=/tmp/dhcpcd HOOKSCRIPTS="50-ntp.conf 50-yp.conf"
cd /tmp/dhcpcd/
/sbin/makepkg -l y -c n /tmp/dhcpcd-9.99-x86_64-1pj.txz

marav · 09-16-2021, 09:41 AM

Quote:

Originally Posted by PJBrs

I compiled dhcpcd from git as well, using cflags and build options from the original slackbuild, but without patches. I can confirm that I now have an IPv4 address after resume when I use NetwerkManager with dhcpcd. Previously, I only got an IPv6 address, and couldn't reach sites that only used IPv4. Problem solved, except, I also end up with a couple of zombies. I suspended three times:

Code:

# ps aux | grep dhc
dhcpcd    7323  0.0  0.0      0     0 ?        Z    16:26   0:00 [dhcpcd] <defunct>
dhcpcd    7486  0.0  0.0      0     0 ?        Z    16:26   0:00 [dhcpcd] <defunct>
dhcpcd    7995  0.0  0.0      0     0 ?        Z    16:27   0:00 [dhcpcd] <defunct>
dhcpcd    8863  0.0  0.0   3016  2504 ?        S    16:29   0:00 dhcpcd: wlan0 [ip4]
root      8864  0.0  0.0   3020  2128 ?        S    16:29   0:00 dhcpcd: [privileged proxy] wlan0 [ip4]
dhcpcd    8865  0.0  0.0   3008   304 ?        S    16:29   0:00 dhcpcd: [control proxy] wlan0 [ip4]
dhcpcd    8872  0.0  0.0   3020   316 ?        S    16:29   0:00 dhcpcd: [BPF ARP] wlan0 192.168.0.23
dhcpcd    8891  0.0  0.0   3020   316 ?        S    16:29   0:00 dhcpcd: [BOOTP proxy] 192.168.0.23
root      8952  0.0  0.0   4008  2200 pts/3    S+   16:29   0:00 grep dhc

Compiled dhcpcd as follows:

Code:

git clone https://github.com/NetworkConfiguration/dhcpcd.git
cd dhcpcd/
CFLAGS="-O2 -fPIC" LIBDIRSUFFIX="64" PRIVSEP_OPTIONS="--enable-privsep --privsepuser=dhcpcd" ./configure --prefix=/usr --libdir=/usr/lib${LIBDIRSUFFIX} --sbindir=/sbin --sysconfdir=/etc --dbdir=/var/lib/dhcpcd --libexecdir=/lib/dhcpcd --mandir=/usr/man --rundir=/run $PRIVSEP_OPTIONS
make
mkdir /tmp/dhcpcd
make install DESTDIR=/tmp/dhcpcd HOOKSCRIPTS="50-ntp.conf 50-yp.conf"
cd /tmp/dhcpcd/
/sbin/makepkg -l y -c n /tmp/dhcpcd-9.99-x86_64-1pj.txz

I also notice the zombies after the suspension/resume

EDIT : same behaviour after logout/login

marav · 09-16-2021, 09:51 AM

The zombie process seems to be the parent one

before suspend

Code:

dhcpcd    4956  0.0  0.0   3008  2496 ?        S    16:39   0:00  \_ dhcpcd: wlan0 [ip4]
root      4957  0.0  0.0   3012  1996 ?        S    16:39   0:00      \_ dhcpcd: [privileged proxy] wlan0 [ip4]
dhcpcd    4972  0.0  0.0   3012   300 ?        S    16:39   0:00      |   \_ dhcpcd: [BPF ARP] wlan0 192.168.111.15
dhcpcd    4979  0.0  0.0   3012   304 ?        S    16:39   0:00      |   \_ dhcpcd: [BOOTP proxy] 192.168.111.15
dhcpcd    4958  0.0  0.0   3004   288 ?        S    16:39   0:00      \_ dhcpcd: [control proxy] wlan0 [ip4]

after resume

Code:

dhcpcd    4956  0.0  0.0      0     0 ?        Z    16:39   0:00  \_ [dhcpcd] <defunct>
dhcpcd    7936  0.0  0.0   3008  2496 ?        S    16:49   0:00  \_ dhcpcd: wlan0 [ip4]
root      7937  0.0  0.0   3012  1988 ?        S    16:49   0:00      \_ dhcpcd: [privileged proxy] wlan0 [ip4]
dhcpcd    7945  0.0  0.0   3012   296 ?        S    16:49   0:00      |   \_ dhcpcd: [BPF ARP] wlan0 192.168.111.15
dhcpcd    7951  0.0  0.0   3012   296 ?        S    16:49   0:00      |   \_ dhcpcd: [BOOTP proxy] 192.168.111.15
dhcpcd    7938  0.0  0.0   3004   284 ?        S    16:49   0:00      \_ dhcpcd: [control proxy] wlan0 [ip4]

marav · 09-16-2021, 10:01 AM

The strace log from the dhcpcd parent process during a suspend/resume

marav · 09-16-2021, 04:50 PM

For your information :

I reported the bug (dhcpcd zombies) upstream to Roy Marples - who is clearly a nice guy!
And he made a patch in his NetworkManager tree
https://gitlab.freedesktop.org/rsmar...cd189cb1580bde

Code:

dhcpcd: stop dhcpcd using nm_dhcp_client_stop_pid rather than killing
NetworkManager can stop/start a DHCP client faster than dhcpcd can
gracefully exit.
As such, refactor nm_dhcp_client_stop_pid so that a specific signal
can be sent which allows dhcpcd to gracefully stop on SIGTERM and
release on SIGALRM.

that I just tested and it works great

Code:

blackstar :: SRC/nm/NetworkManager-9cc2591fe871b29ce9a743dfb2cd189cb1580bde » NetworkManager -V
1.33.2

Code:

blackstar :: SRC/nm/NetworkManager-9cc2591fe871b29ce9a743dfb2cd189cb1580bde » dhcpcd --version
dhcpcd 9.99.0
Copyright (c) 2006-2021 Roy Marples
Compiled in features: INET ARP ARPing IPv4LL INET6 DHCPv6 AUTH PRIVSEP

Before suspend

Code:

blackstar :: SRC/nm/NetworkManager-9cc2591fe871b29ce9a743dfb2cd189cb1580bde » ps faux | grep "[d]hcp"
dhcpcd   25557  0.0  0.0   3016  2560 ?        S    23:42   0:00  \_ dhcpcd: wlan0 [ip4]
root     25558  0.0  0.0   3020  1964 ?        S    23:42   0:00      \_ dhcpcd: [privileged proxy] wlan0 [ip4]
dhcpcd   25574  0.0  0.0   3020   304 ?        S    23:42   0:00      |   \_ dhcpcd: [BPF ARP] wlan0 192.168.111.15
dhcpcd   25580  0.0  0.0   3020   308 ?        S    23:42   0:00      |   \_ dhcpcd: [BOOTP proxy] 192.168.111.15
dhcpcd   25559  0.0  0.0   3008   296 ?        S    23:42   0:00      \_ dhcpcd: [control proxy] wlan0 [ip4]

After resume

Code:

blackstar :: SRC/nm/NetworkManager-9cc2591fe871b29ce9a743dfb2cd189cb1580bde » ps faux | grep "[d]hcp"
dhcpcd   25901  0.0  0.0   3020  2528 ?        S    23:43   0:00  \_ dhcpcd: wlan0 [ip4]
root     25902  0.0  0.0   3024  2088 ?        S    23:43   0:00      \_ dhcpcd: [privileged proxy] wlan0 [ip4]
dhcpcd   25910  0.0  0.0   3024   308 ?        S    23:43   0:00      |   \_ dhcpcd: [BPF ARP] wlan0 192.168.111.15
dhcpcd   25916  0.0  0.0   3024   312 ?        S    23:43   0:00      |   \_ dhcpcd: [BOOTP proxy] 192.168.111.15
dhcpcd   25903  0.0  0.0   3008   296 ?        S    23:43   0:00      \_ dhcpcd: [control proxy] wlan0 [ip4]

github link :
https://github.com/NetworkConfigurat...cpcd/issues/57

So we have to wait a few versions for dhcpcd/NetworkManager to work together as expected. (as soon as its patch is merged in the NM tree)