systemd-networkd not detecting wireless connection via wpa_supplicant

mraf61-i6556 · 2022-09-23 17:11:25

I don't know what's exactly happened, all I know that I was trying to install Gimp plugin resynthesizer from aur repository and break my system GUI (I think GTK mostly), so I did full system upgrade (*Arch Linux*) and the DE come back to work again ...

After restart, I immediately notice that Internet connection were lost I checked `wpa_supplicant` service
`wpa_supplicant@wlo1.service` and it was running correctly, but my network connection didn't have IP address when i run `ip a` ,,,

The weird thing that when I use `wifigui` ( wifiman Wi-Fi GUI script) and connect to the network using preset profile, the connection were success, with no issue at all..
the problem with `wifigui` is that I can't make it works automatically at boot,
BTW wpa_supplicant service works well it connect to Wifi network after each boot, but networked can't communicate with it network

After my last boot, I tried to solve the issue by assigning an IP address to the wifi network

sudo ip a add 192.168.1.50/24 dev wlo1
sudo ip route   add 192.168.1.0/24 dev wlo1

But no hope, I still go `connect: Network is unreachable` when I tried to ping an IP address .

Here is complete log of my trial and error trying to fix this issue

   ========== ip a  
: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 99:49:96:91:99:91 brd ff:ff:ff:ff:ff:ff
altname wlp1s0
inet 192.168.1.50/24 scope global wlo1
valid_lft forever preferred_lft forever
inet6 fe80::224e:8381:8381:8381/64 scope link 
valid_lft forever preferred_lft forever
=============    ip -s link show  wlo1
2: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether 99:49:96:91:99:91 brd ff:ff:ff:ff:ff:ff
RX:  bytes packets errors dropped  missed   mcast           
320       2      0       0       0       0 
TX:  bytes packets errors dropped carrier collsns           
7320      49      0       0       0       0 
altname wlp1s0
=============    networkctl status  wlo1
● 2: wlo1                                                                       
Link File: /usr/lib/systemd/network/99-default.link
Network File: n/a
Type: wlan
Kind: n/a
State: routable (unmanaged)
Online state: unknown
Alternative Names: wlp1s0
Path: pci-0000:01:00.0
Driver: rtw_8822ce
Vendor: Realtek Semiconductor Co., Ltd.
Model: RTL8822CE 802.11ac PCIe Wireless Network Adapter
Hardware Address: 99:49:96:91:99:91 (AzureWave Technology Inc.)
MTU: 1500 (min: 256, max: 2304)
QDisc: noqueue
IPv6 Address Generation Mode: eui64
WiFi access point: (null) (20:00:05:00:02:00)
Number of Queues (Tx/Rx): 1/1
Address: 192.168.1.50
fe80::224e:f6ff:fe51:b3b1
Activation Policy: up
Required For Online: yes

Sep 23 18:28:16 archlinux systemd-networkd[251]: wlo1: Link UP
Sep 23 18:28:21 archlinux systemd-networkd[251]: wlo1: Gained carrier
Sep 23 18:28:23 archlinux systemd-networkd[251]: wlo1: Gained IPv6LL
=============  sudo  networkctl  -s
IDX LINK TYPE     OPERATIONAL SETUP    
1 lo   loopback carrier     unmanaged
2 wlo1 wlan     routable    unmanaged
2 links listed. 
=============    sudo  systemctl status  wpa_supplicant@wlo1.service
● wpa_supplicant@wlo1.service - WPA supplicant daemon (interface-specific version)
Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant@.service; enabled; preset: disabled)
Active: active (running) since Fri 2022-09-23 18:28:15 EET; 11min ago
Main PID: 366 (wpa_supplicant)
Tasks: 1 (limit: 3912)
Memory: 2.4M
CPU: 751ms
CGroup: /system.slice/system-wpa_supplicant.slice/wpa_supplicant@wlo1.service
└─366 /usr/bin/wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant-wlo1.conf -iwlo1
Sep 23 18:28:15 archlinux systemd[1]: Started WPA supplicant daemon (interface-specific version).
Sep 23 18:28:15 archlinux wpa_supplicant[366]: Successfully initialized wpa_supplicant
Sep 23 18:28:20 archlinux wpa_supplicant[366]: wlo1: SME: Trying to authenticate with 20:00:05:00:02:00 (SSID='LTT4G-ADL0' freq=2427 MHz)
Sep 23 18:28:21 archlinux wpa_supplicant[366]: wlo1: Trying to associate with 20:00:05:00:02:00 (SSID='ADL0' freq=2427 MHz)
Sep 23 18:28:21 archlinux wpa_supplicant[366]: wlo1: Associated with 20:00:05:00:02:00
Sep 23 18:28:21 archlinux wpa_supplicant[366]: wlo1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sep 23 18:28:21 archlinux wpa_supplicant[366]: wlo1: WPA: Key negotiation completed with 20:00:05:00:02:00 [PTK=CCMP GTK=CCMP]
Sep 23 18:28:21 archlinux wpa_supplicant[366]: wlo1: CTRL-EVENT-CONNECTED - Connection to 20:00:05:00:02:00 completed [id=0 id_str=]

=============ping 8.8.8.8
ping: connect: Network is unreachable

and this after make the connection with `wifigui`

      		============= ip a
	2: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
		 link/ether 25:99:99:91:93:91 brd ff:ff:ff:ff:ff:ff
		 altname wlp1s0
		 inet 192.168.1.50/24 scope global wlo1
		    valid_lft forever preferred_lft forever
		 inet 192.168.1.101/24 brd 192.168.1.255 scope global secondary dynamic noprefixroute wlo1
		    valid_lft 85526sec preferred_lft 74726sec
		 inet6 fe80::16a2:ec12:611e:1215/64 scope link 
		    valid_lft forever preferred_lft forever

Last edited by mraf61-i6556 (2022-09-24 12:36:30)

seth · 2022-09-23 21:22:23

: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 99:49:96:91:99:91 brd ff:ff:ff:ff:ff:ff
altname wlp1s0
inet 192.168.1.50/24 scope global wlo1
valid_lft forever preferred_lft forever
inet6 fe80::224e:8381:8381:8381/64 scope link
valid_lft forever preferred_lft forever

At this point you've a carrier and a lease, I'd look into "ip r" and "resolvectl"

2 wlo1 wlan routable unmanaged

doesn't look good (? i don't use networkd, but "unmanaged" sounds wrong)

I'll guess that this is a race condition across the NIC rename, https://wiki.archlinux.org/title/Networ … face_names - the NIC should then be reliably wlan0

mraf61-i6556 · 2022-09-24 00:06:35

seth wrote:

At this point you've a carrier and a lease, I'd look into "ip r" and "resolvectl"
2 wlo1 wlan routable unmanaged
doesn't look good (? i don't use networkd, but "unmanaged" sounds wrong)
I'll guess that this is a race condition across the NIC rename, https://wiki.archlinux.org/title/Networ … face_names - the NIC should then be reliably wlan0

"ip r" output nothing and I don't think issue is with "resolvectl" , since I don't have network connection at all.
Here is the rest of the logs, after a couple changes I did that did not solve the issue .

 =============ip r # nothing result 
$ sudo  networkctl  -s
IDX LINK TYPE     OPERATIONAL SETUP    
1 lo   loopback carrier     unmanaged
2 wlo1 wlan     degraded    unmanaged
2 links listed.
=============  ip  a
2: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 15:63:65:04:91:82 brd ff:ff:ff:ff:ff:ff
    altname wlp1s0
    inet6 fe80::224e:f6ff:fe51:b3b1/64 scope link 
       valid_lft forever preferred_lft forever
=============  networkctl status wlo1
● 2: wlo1                                                                       
Link File: /usr/lib/systemd/network/99-default.link
Network File: n/a
Type: wlan
Kind: n/a
State: degraded (unmanaged)
Online state: unknown
Alternative Names: wlp1s0
Path: pci-0000:01:00.0
Driver: rtw_8822ce
Vendor: Realtek Semiconductor Co., Ltd.
Model: RTL8822CE 802.11ac PCIe Wireless Network Adapter
Hardware Address: 15:63:65:04:91:82 (AzureWave Technology Inc.)
MTU: 1500 (min: 256, max: 2304)
QDisc: noqueue
IPv6 Address Generation Mode: eui64
WiFi access point: (null) (15:63:65:04:91:28)
Number of Queues (Tx/Rx): 1/1
Address: fe80::224e:f6ff:fe51:b3b1
Activation Policy: up
Required For Online: yes
Sep 24 00:26:26 archlinux systemd-networkd[250]: wlo1: Link UP
Sep 24 00:26:31 archlinux systemd-networkd[250]: wlo1: Gained carrier
Sep 24 00:26:32 archlinux systemd-networkd[250]: wlo1: Gained IPv6LL
=============  sudo systemctl status  systemd-networkd.service
● systemd-networkd.service - Network Configuration
     Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; preset: enabled)
     Active: active (running) since Sat 2022-09-24 00:26:24 EET; 14min ago
TriggeredBy: ● systemd-networkd.socket
       Docs: man:systemd-networkd.service(8)
   Main PID: 250 (systemd-network)
     Status: "Processing requests..."
      Tasks: 1 (limit: 3912)
     Memory: 3.2M
        CPU: 39ms
     CGroup: /system.slice/systemd-networkd.service
             └─250 /usr/lib/systemd/systemd-networkd
Sep 24 00:26:24 archlinux systemd[1]: Starting Network Configuration...
Sep 24 00:26:24 archlinux systemd-networkd[250]: lo: Link UP
Sep 24 00:26:24 archlinux systemd-networkd[250]: lo: Gained carrier
Sep 24 00:26:24 archlinux systemd-networkd[250]: Enumeration completed
Sep 24 00:26:24 archlinux systemd[1]: Started Network Configuration.
Sep 24 00:26:25 archlinux systemd-networkd[250]: wlan0: Interface name change detected, renamed to wlo1.
Sep 24 00:26:26 archlinux systemd-networkd[250]: wlo1: Link UP
Sep 24 00:26:31 archlinux systemd-networkd[250]: wlo1: Gained carrier
Sep 24 00:26:32 archlinux systemd-networkd[250]: wlo1: Gained IPv6LL

Last edited by mraf61-i6556 (2022-09-24 12:43:50)

seth · 2022-09-24 06:21:01

Please use code tags, not quote tags.
Then follow https://wiki.archlinux.org/title/Networ … face_names and if that still doesn't help, post a complete system journal

sudo journalctl -b > /tmp/journal.txt # upload that file

Random outputs of random commands you took at random times after random actions are meaningless.

apaz · 2022-09-24 07:44:54

I had had problems because it proposed to use "wlan0" but then wanted "wlp5s0". Try to check if your problem is similar. If it is this you have to repeat the whole installation by imposing the real name of your wireless device (wlp1s0).

seth · 2022-09-24 08:03:33

Yes, that's why I keep suggesting to https://wiki.archlinux.org/title/Networ … face_names in order to prevent the race where the left hand of systemd loses track of what the right hand of systemd is doing there.

you have to repeat the whole installation

AB·SO·LU·TE·LY NOT! You just need to fix the network configuration, ie. disable the renaming nonsense and alter the wpa_supplicant@ service to use wlan0

mraf61-i6556 · 2022-09-24 13:24:28

I did all seth suggested, the wireless network now have named wlan0 , but the issue still existing...
Anyway I figure out it's DHCP (IP assigning ) issue, I don't know why systemd-networkd did not issue DHCP correctly my system have `dhcpcd` ,,
wpa_supplicant works well and connect to the network correctly

Since when I use these commands the wifi network connect works

sudo ip a add 192.168.1.50/24 dev  wlan0
sudo ip route add default via 192.168.1.1 dev wlan0

Here is contents of my `/etc/systemd/network/25-wireless.network` file

[Match]
Name=wlan0
SSID=LTT4G-ADL0

[Network]
DHCP=yes
IPv6AcceptRA=no

here is contents of `sudo journalctl -b > /tmp/journal.txt` command

https://res.cloudinary.com/dyxy0zski/ra … bc2kqz.txt

Last edited by mraf61-i6556 (2022-09-24 13:31:07)

seth · 2022-09-24 13:37:52

networkd doesn't use dhcpcd.

Let's see whethre there is a dhcp server (and where)

sudo nmap --script broadcast-dhcp-discover

mraf61-i6556 · 2022-09-24 16:21:35

seth wrote:

networkd doesn't use dhcpcd.
Let's see whethre there is a dhcp server (and where)
Sorry the previous out were after I setup IP manually this is real output just after I log in
   sudo nmap --script broadcast-dhcp-discover 
Starting Nmap 7.92 ( https://nmap.org ) at 2022-09-24 18:53 EET
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 10.36 seconds
[s]sudo nmap --script broadcast-dhcp-discover

   sudo nmap --script broadcast-dhcp-discover
Starting Nmap 7.92 ( https://nmap.org ) at 2022-09-24 18:19 EET
Pre-scan script results:
| broadcast-dhcp-discover: 
|   Response 1 of 1: 
|     Interface: wlan0
|     IP Offered: 192.168.1.104
|     DHCP Message Type: DHCPOFFER
|     Server Identifier: 192.168.1.1
|     IP Address Lease Time: 1d00h00m00s
|     Renewal Time Value: 12h00m00s
|     Rebinding Time Value: 21h00m00s
|     Subnet Mask: 255.255.255.0
|     Router: 192.168.1.1
|_    Domain Name Server: 192.168.1.1
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 10.49 seconds[/s]

Last edited by mraf61-i6556 (2022-09-24 16:58:54)

seth · 2022-09-24 16:42:04

So there's a dhcp server…

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

mraf61-i6556 · 2022-09-24 16:43:28

 find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
cpupower.service                         | multi-user.target.wants
cronie.service                           | multi-user.target.wants
cups.path                                | multi-user.target.wants
cups.service                             | multi-user.target.wants
cups.service                             | printer.target.wants
cups.socket                              | sockets.target.wants
dbus-fi.w1.wpa_supplicant1.service       | system
dbus-org.freedesktop.network1.service    | system
dbus-org.freedesktop.resolve1.service    | system
disable-c6.service                       | basic.target.wants
disable-c6.service                       | hibernate.target.wants
disable-c6.service                       | suspend.target.wants
display-manager.service                  | system
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
libvirtd-ro.socket                       | sockets.target.wants
libvirtd.service                         | multi-user.target.wants
libvirtd.socket                          | sockets.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-networkd.service                 | multi-user.target.wants
systemd-networkd.socket                  | sockets.target.wants
systemd-networkd-wait-online.service     | network-online.target.wants
systemd-resolved.service                 | multi-user.target.wants
virtlockd.socket                         | sockets.target.wants
virtlogd.socket                          | sockets.target.wants
wpa_supplicant.service                   | multi-user.target.wants
wpa_supplicant@wlan0.service             | multi-user.target.wants
xdg-user-dirs-update.service             | default.target.wants

seth · 2022-09-24 16:51:48

wpa_supplicant.service                   | multi-user.target.wants
wpa_supplicant@wlan0.service             | multi-user.target.wants

You've competing wpa_supplicant services, get rid of the specific one.

mraf61-i6556 · 2022-09-24 17:01:28

seth wrote:

wpa_supplicant.service                   | multi-user.target.wants
wpa_supplicant@wlan0.service             | multi-user.target.wants
You've competing wpa_supplicant services, get rid of the specific one.

I disable

 sudo systemctl disable  wpa_supplicant.service

Anyway I update my previous reply about dhcp server

   sudo nmap --script broadcast-dhcp-discover 
Starting Nmap 7.92 ( https://nmap.org ) at 2022-09-24 18:53 EET
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 10.36 seconds

=Edit=
still even after reboot same issue I'm only able to Set IP address to the network manually , BTW the wlan0 are up by `systemd-networkd` at boot, but it fails assigning IPv4 for it.

Last edited by mraf61-i6556 (2022-09-24 18:08:54)

seth · 2022-09-24 20:43:03

Anyway I update my previous reply about dhcp server

Did you at this point have a carrier ("<BROADCAST,MULTICAST,UP,LOWER_UP>")?

but it fails assigning IPv4 for it.

If there's no dhcp server on the network, nor a static IP config, you're not getting an IP from anywhere.

Do you control LTT4G-ADL0 ?
Is there a parallel windows installation?

Can you reliably get a lease when using networkmanager *instead* of systemd-networkd? ie. stop/disable services and sockets for the latter as well as wpa_supplicant and then start NM (it'll run wpa_supplicant itself); networkd and NM must NOT run in parallel.

mraf61-i6556 · 2022-09-26 00:18:11

seth wrote:

Did you at this point have a carrier ("<BROADCAST,MULTICAST,UP,LOWER_UP>")?

I'm having it all the time after boot, the issue only related to not having IP on the network ..
BTW my current ( wpa_supplicant & networkd) setup was working for me very well for months, the issue happened after I did full system update ( the last time were over month )

If there's no dhcp server on the network, nor a static IP config, you're not getting an IP from anywhere.

networkd should give the network either static or dhcp IP from my configuration file (I tried both config static && DHCP)

cat /etc/systemd/network/25-wireless.network
[Match]
Name=wlan0
SSID=LTT4G-ADL0
[Network]
DHCP=yes
IPv6AcceptRA=no

Do you control LTT4G-ADL0 ?
Is there a parallel windows installation?

Yes that's my 4G wifi modem,,,,No there is no Windows installed on my Laptop (the wifi chip name are in above logs)

Can you reliably get a lease when using networkmanager *instead* of systemd-networkd?
ie. stop/disable services and sockets for the latter as well as wpa_supplicant and then start NM (it'll run wpa_supplicant itself); networkd and NM must NOT run in parallel.

I don't have networkmanager installed on my system, I use both systemd-networkd and wpa_supplicant service to get the connection done automaticity after boot,,
I tried both start/stop enable/disable either of systemd-networkd wpa_supplicant and nothing changed same IP issue .

BTW, for now I'm adding IP manually after each boot. since now, this is the only way I know to temporarily solve this issue .

Last edited by mraf61-i6556 (2022-09-26 00:21:11)

seth · 2022-09-26 06:36:41

networkd should give the network either static or dhcp IP

There's no static IP configuration in that .network file.

Yes that's my 4G wifi modem

Please make sure it runs a dhcp server, in doubt reboot it.

I don't have networkmanager installed on my system

Yeah… the plan was to change it and figure whether this is a problem networkd and/or your networkd configuration.
Though for the moment, as long as nmap doesn't find a dhcp server you need to either fix the dhcp server (reboot your modem) or use a static IP configuration.

I tried both start/stop enable/disable either of systemd-networkd wpa_supplicant

What do you think stopping any of the required services would achieve. Stop flailing, you're creating a moving target that will make it much harder to get to the bottom of this.

mraf61-i6556 · 2022-09-26 12:51:20

seth wrote:

There's no static IP configuration in that .network file.

I already did try that, and I always get `connect: Network is unreachable` when ping to any IP (it is similar to this config file .
Like systemd-networkd completely ignoring /etc/systemd/network/25-wireless.network file

Please make sure it runs a dhcp server, in doubt reboot it.

I connect to same modem using my android phone and it get dynamic IP with no issue,
and here is screenshot of modem DHCP settings

Yeah… the plan was to change it and figure whether this is a problem networkd and/or your networkd configuration..

I didn't install networkmanager because I was afraid it could conflict with systemd-networkd , I may try it later on.

Last edited by mraf61-i6556 (2022-09-26 14:09:32)

seth · 2022-09-26 13:15:45

I connect to same modem using my android phone and

… that's completely irrelevant. If there's a stale lease and the router/dhcp server ignores your system. (Though a scan should™ still find it)

Make sure to NOT have a static IP configured, reboot, then run

ip a
sudo nmap --script broadcast-dhcp-discover

to make sure that you've a carrier on the wifi nic and then scan for dhcp servers.

t is similar

https://bbs.archlinux.org/viewtopic.php?id=57855
Post the actual file and the output of

ip a; ip r; ping -c1 _gateway

for this setup.

I didn't install networkmanager because I was afraid

Simply enable NM and disable the networkd and wpa_supplicant services.

Please replace the image w/ a link. The board has a 250x250 limit rule.

Arch Linux

#1 2022-09-23 17:11:25

systemd-networkd not detecting wireless connection via wpa_supplicant

#2 2022-09-23 21:22:23

Re: systemd-networkd not detecting wireless connection via wpa_supplicant

#3 2022-09-24 00:06:35

Re: systemd-networkd not detecting wireless connection via wpa_supplicant

#4 2022-09-24 06:21:01

Re: systemd-networkd not detecting wireless connection via wpa_supplicant

#5 2022-09-24 07:44:54

Re: systemd-networkd not detecting wireless connection via wpa_supplicant

#6 2022-09-24 08:03:33

Re: systemd-networkd not detecting wireless connection via wpa_supplicant

#7 2022-09-24 13:24:28

Re: systemd-networkd not detecting wireless connection via wpa_supplicant

#8 2022-09-24 13:37:52

Re: systemd-networkd not detecting wireless connection via wpa_supplicant

#9 2022-09-24 16:21:35

Re: systemd-networkd not detecting wireless connection via wpa_supplicant

#10 2022-09-24 16:42:04

Re: systemd-networkd not detecting wireless connection via wpa_supplicant

#11 2022-09-24 16:43:28

Re: systemd-networkd not detecting wireless connection via wpa_supplicant

#12 2022-09-24 16:51:48

Re: systemd-networkd not detecting wireless connection via wpa_supplicant

#13 2022-09-24 17:01:28

Re: systemd-networkd not detecting wireless connection via wpa_supplicant

#14 2022-09-24 20:43:03

Re: systemd-networkd not detecting wireless connection via wpa_supplicant

#15 2022-09-26 00:18:11

Re: systemd-networkd not detecting wireless connection via wpa_supplicant

#16 2022-09-26 06:36:41

Re: systemd-networkd not detecting wireless connection via wpa_supplicant

#17 2022-09-26 12:51:20

Re: systemd-networkd not detecting wireless connection via wpa_supplicant

#18 2022-09-26 13:15:45

Re: systemd-networkd not detecting wireless connection via wpa_supplicant

Board footer