You are not logged in.

Pages: 1

#1 2024-06-14 00:50:34

guilehm
Member
Registered: 2023-02-01
Posts: 12

[SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

Hi everyone,

I'm having trouble connecting to Wi-Fi on my Arch Linux setup.

When I try to connect to my Wi-Fi network using nmcli, I receive the error "Connection activation failed: the wifi network could not be found".
Same error happens if I try to use nmtui.
Also tried connecting with wpa_supplicant:

sudo wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf

The same Wi-Fi works perfectly fine on Windows in a dual-boot setup (fast startup was already disabled), so I'm confident it's not a hardware issue.

What I tried
- Ensured the Wi-Fi interface is up and managed by NetworkManager:

nmcli radio wifi on
nmcli device set wlan0 managed yes

- Checked RFKill status and nothing is blocked
- Updated the system packages:

sudo pacman -Syu
sudo pacman -S networkmanager wpa_supplicant wireless_tools

- The result of: nmcli device status

wlan0            wifi      disconnected            --
p2p-dev-wlan0    wifi-p2p  disconnected            --

So I start suspecting of this p2p-dev-wlan0, because when I try to connect, I see both logs at the same time:

Jun 13 21:41:51 gui NetworkManager[41264]: <info>  [1718325711.2941] device (wlan0): supplicant interface state: disconnected -> inactive
Jun 13 21:41:51 gui NetworkManager[41264]: <info>  [1718325711.2941] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> inactive
Jun 13 21:41:51 gui NetworkManager[41264]: <info>  [1718325711.3114] device (wlan0): supplicant interface state: inactive -> authenticating
Jun 13 21:41:51 gui NetworkManager[41264]: <info>  [1718325711.3114] device (p2p-dev-wlan0): supplicant management interface state: inactive -> authenticating
Jun 13 21:42:16 gui NetworkManager[41264]: <warn>  [1718325736.9064] device (wlan0): Activation: (wifi) association took too long, failing activation
Jun 13 21:42:16 gui NetworkManager[41264]: <info>  [1718325736.9064] device (wlan0): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jun 13 21:42:16 gui NetworkManager[41264]: <info>  [1718325736.9675] device (wlan0): set-hw-addr: set MAC address to 8A:40:81:F3:9E:83 (scanning)
Jun 13 21:42:16 gui NetworkManager[41264]: <warn>  [1718325736.9917] device (wlan0): Activation: failed for connection 'pwned'
Jun 13 21:42:16 gui NetworkManager[41264]: <info>  [1718325736.9918] device (wlan0): supplicant interface state: disconnected -> interface_disabled

And NetworkManager is creating it:

Jun 13 21:40:50 gui NetworkManager[41264]: <info>  [1718325650.5105] device (docker0): Activation: successful, device activated.
Jun 13 21:40:50 gui NetworkManager[41264]: <info>  [1718325650.5326] dhcp4 (eno1): state changed new lease, address=192.168.15.153, acd pending
Jun 13 21:40:50 gui NetworkManager[41264]: <info>  [1718325650.5328] device (wlan0): supplicant interface state: internal-starting -> disconnected
Jun 13 21:40:50 gui NetworkManager[41264]: <info>  [1718325650.5328] Wi-Fi P2P device controlled by interface wlan0 created

I tried disabling it in /etc/wpa_supplicant/wpa_supplicant.conf

p2p_disabled=1

Also on NetworkManager.conf

[device]
wifi.scan-rand-mac-address=no

[wifi]
p2p_device=no

Restarted both services, wpa_supplicant and NetworkManager, but nothing changed. Both services are active.

nmcli list the wifi list perfectly:

nmcli device wifi list
IN-USE  BSSID              SSID                   MODE   CHAN  RATE        SIGNAL  BARS  SECURITY
        86:0B:BB:77:08:3F  hacked                 Infra  149   540 Mbit/s  82      ▂▄▆█  WPA2
        84:0B:BB:77:08:3F  pwned                  Infra  149   540 Mbit/s  80      ▂▄▆_  WPA2

I'm completely out of ideas on what to do next or what could be causing this issue.
I was using it normally yesterday, and today this problem started.

Any assistance or suggestions on what I might be missing or additional steps to try would be greatly appreciated.

Thanks

Last edited by guilehm (2024-06-18 18:30:15)

Offline

#2 2024-06-14 12:59:36

AaAaAAaaAAaARCH
Member
Registered: 2024-02-29
Posts: 42

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

Do you have some kind of firewall running that could be blocking dhcp?

What is the output of the following commands?

ip a
sudo iptables -nvL
sudo ip6tables -nvL
sudo nft list ruleset

although it looks like it fails well before dhcp is even started. Are there any driver errors in dmesg?

Last edited by AaAaAAaaAAaARCH (2024-06-14 13:39:41)

Offline

#3 2024-06-14 14:27:36

guilehm
Member
Registered: 2023-02-01
Posts: 12

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

AaAaAAaaAAaARCH wrote:

Do you have some kind of firewall running that could be blocking dhcp?

What is the output of the following commands?

ip a
sudo iptables -nvL
sudo ip6tables -nvL
sudo nft list ruleset

although it looks like it fails well before dhcp is even started. Are there any driver errors in dmesg?

Thanks for your answer.
No firewalls.

sudo dmesg | grep -i error
[    0.439763] RAS: Correctable Errors collector initialized.
[    7.449745] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
ip a
sudo iptables -nvL
sudo ip6tables -nvL
sudo nft list ruleset
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether c8:7f:54:04:bf:47 brd ff:ff:ff:ff:ff:ff
    altname enp10s0
    inet 192.168.15.153/24 brd 192.168.15.255 scope global dynamic noprefixroute eno1
       valid_lft 14361sec preferred_lft 14361sec
    inet6 2804:7f0:b500:1dfa:820:8fcf:c7b6:40a5/64 scope global dynamic noprefixroute
       valid_lft 43195sec preferred_lft 43195sec
    inet6 fe80::959a:5345:791d:cce1/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether ae:ae:c4:fe:33:19 brd ff:ff:ff:ff:ff:ff permaddr 10:6f:d9:db:eb:3b
4: br-532f00479926: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:09:5e:5b:2d brd ff:ff:ff:ff:ff:ff
    inet 172.27.0.1/16 brd 172.27.255.255 scope global br-532f00479926
       valid_lft forever preferred_lft forever
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:b1:9c:a0:ea brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
6: br-ea17f7412758: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:da:8a:a4:8e brd ff:ff:ff:ff:ff:ff
    inet 192.168.49.1/24 brd 192.168.49.255 scope global br-ea17f7412758
       valid_lft forever preferred_lft forever
    inet6 fe80::42:daff:fe8a:a48e/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
7: br-f2d76f96f92c: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:7f:69:22:82 brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global br-f2d76f96f92c
       valid_lft forever preferred_lft forever
8: br-f6ceae761663: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:60:eb:80:29 brd ff:ff:ff:ff:ff:ff
    inet 172.20.0.1/16 brd 172.20.255.255 scope global br-f6ceae761663
       valid_lft forever preferred_lft forever
10: veth76e89c5@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-ea17f7412758 state UP group default
    link/ether 3e:ec:86:ea:df:0b brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::3cec:86ff:feea:df0b/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
11: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 500
    link/none
    inet 192.168.252.2/27 scope global tun0
       valid_lft forever preferred_lft forever
    inet6 fe80::bdaf:d489:75bc:87a6/64 scope link stable-privacy proto kernel_ll
       valid_lft forever preferred_lft forever
[sudo] password for gui:
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain FORWARD (policy DROP 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination
   50  9547 DOCKER-USER  0    --  *      *       0.0.0.0/0            0.0.0.0/0
   50  9547 DOCKER-ISOLATION-STAGE-1  0    --  *      *       0.0.0.0/0            0.0.0.0/0
    0     0 ACCEPT     0    --  *      docker0  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
    0     0 DOCKER     0    --  *      docker0  0.0.0.0/0            0.0.0.0/0
    0     0 ACCEPT     0    --  docker0 !docker0  0.0.0.0/0            0.0.0.0/0
    0     0 ACCEPT     0    --  docker0 docker0  0.0.0.0/0            0.0.0.0/0
    0     0 ACCEPT     0    --  *      br-f6ceae761663  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
    0     0 DOCKER     0    --  *      br-f6ceae761663  0.0.0.0/0            0.0.0.0/0
    0     0 ACCEPT     0    --  br-f6ceae761663 !br-f6ceae761663  0.0.0.0/0            0.0.0.0/0
    0     0 ACCEPT     0    --  br-f6ceae761663 br-f6ceae761663  0.0.0.0/0            0.0.0.0/0
    0     0 ACCEPT     0    --  *      br-f2d76f96f92c  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
    0     0 DOCKER     0    --  *      br-f2d76f96f92c  0.0.0.0/0            0.0.0.0/0
    0     0 ACCEPT     0    --  br-f2d76f96f92c !br-f2d76f96f92c  0.0.0.0/0            0.0.0.0/0
    0     0 ACCEPT     0    --  br-f2d76f96f92c br-f2d76f96f92c  0.0.0.0/0            0.0.0.0/0
   24  7291 ACCEPT     0    --  *      br-ea17f7412758  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
    0     0 DOCKER     0    --  *      br-ea17f7412758  0.0.0.0/0            0.0.0.0/0
   26  2256 ACCEPT     0    --  br-ea17f7412758 !br-ea17f7412758  0.0.0.0/0            0.0.0.0/0
    0     0 ACCEPT     0    --  br-ea17f7412758 br-ea17f7412758  0.0.0.0/0            0.0.0.0/0
    0     0 ACCEPT     0    --  *      br-532f00479926  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
    0     0 DOCKER     0    --  *      br-532f00479926  0.0.0.0/0            0.0.0.0/0
    0     0 ACCEPT     0    --  br-532f00479926 !br-532f00479926  0.0.0.0/0            0.0.0.0/0
    0     0 ACCEPT     0    --  br-532f00479926 br-532f00479926  0.0.0.0/0            0.0.0.0/0

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain DOCKER (5 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 ACCEPT     6    --  !br-ea17f7412758 br-ea17f7412758  0.0.0.0/0            192.168.49.2         tcp dpt:32443
    0     0 ACCEPT     6    --  !br-ea17f7412758 br-ea17f7412758  0.0.0.0/0            192.168.49.2         tcp dpt:8443
    0     0 ACCEPT     6    --  !br-ea17f7412758 br-ea17f7412758  0.0.0.0/0            192.168.49.2         tcp dpt:5000
    0     0 ACCEPT     6    --  !br-ea17f7412758 br-ea17f7412758  0.0.0.0/0            192.168.49.2         tcp dpt:2376
    0     0 ACCEPT     6    --  !br-ea17f7412758 br-ea17f7412758  0.0.0.0/0            192.168.49.2         tcp dpt:22

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 DOCKER-ISOLATION-STAGE-2  0    --  docker0 !docker0  0.0.0.0/0            0.0.0.0/0
    0     0 DOCKER-ISOLATION-STAGE-2  0    --  br-f6ceae761663 !br-f6ceae761663  0.0.0.0/0            0.0.0.0/0
    0     0 DOCKER-ISOLATION-STAGE-2  0    --  br-f2d76f96f92c !br-f2d76f96f92c  0.0.0.0/0            0.0.0.0/0
   26  2256 DOCKER-ISOLATION-STAGE-2  0    --  br-ea17f7412758 !br-ea17f7412758  0.0.0.0/0            0.0.0.0/0
    0     0 DOCKER-ISOLATION-STAGE-2  0    --  br-532f00479926 !br-532f00479926  0.0.0.0/0            0.0.0.0/0
   50  9547 RETURN     0    --  *      *       0.0.0.0/0            0.0.0.0/0

Chain DOCKER-ISOLATION-STAGE-2 (5 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 DROP       0    --  *      docker0  0.0.0.0/0            0.0.0.0/0
    0     0 DROP       0    --  *      br-f6ceae761663  0.0.0.0/0            0.0.0.0/0
    0     0 DROP       0    --  *      br-f2d76f96f92c  0.0.0.0/0            0.0.0.0/0
    0     0 DROP       0    --  *      br-ea17f7412758  0.0.0.0/0            0.0.0.0/0
    0     0 DROP       0    --  *      br-532f00479926  0.0.0.0/0            0.0.0.0/0
   26  2256 RETURN     0    --  *      *       0.0.0.0/0            0.0.0.0/0

Chain DOCKER-USER (1 references)
 pkts bytes target     prot opt in     out     source               destination
   50  9547 RETURN     0    --  *      *       0.0.0.0/0            0.0.0.0/0
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination
# Warning: table ip nat is managed by iptables-nft, do not touch!
table ip nat {
	chain DOCKER {
		iifname "docker0" counter packets 0 bytes 0 return
		iifname "br-f6ceae761663" counter packets 0 bytes 0 return
		iifname "br-f2d76f96f92c" counter packets 0 bytes 0 return
		iifname "br-ea17f7412758" counter packets 0 bytes 0 return
		iifname "br-532f00479926" counter packets 0 bytes 0 return
		ip daddr 127.0.0.1 iifname != "br-ea17f7412758" tcp dport 32768 counter packets 0 bytes 0 xt target "DNAT"
		ip daddr 127.0.0.1 iifname != "br-ea17f7412758" tcp dport 32769 counter packets 0 bytes 0 xt target "DNAT"
		ip daddr 127.0.0.1 iifname != "br-ea17f7412758" tcp dport 32770 counter packets 0 bytes 0 xt target "DNAT"
		ip daddr 127.0.0.1 iifname != "br-ea17f7412758" tcp dport 32771 counter packets 0 bytes 0 xt target "DNAT"
		ip daddr 127.0.0.1 iifname != "br-ea17f7412758" tcp dport 32772 counter packets 0 bytes 0 xt target "DNAT"
	}

	chain POSTROUTING {
		type nat hook postrouting priority srcnat; policy accept;
		ip saddr 172.17.0.0/16 oifname != "docker0" counter packets 0 bytes 0 xt target "MASQUERADE"
		ip saddr 172.20.0.0/16 oifname != "br-f6ceae761663" counter packets 0 bytes 0 xt target "MASQUERADE"
		ip saddr 172.18.0.0/16 oifname != "br-f2d76f96f92c" counter packets 0 bytes 0 xt target "MASQUERADE"
		ip saddr 192.168.49.0/24 oifname != "br-ea17f7412758" counter packets 7 bytes 640 xt target "MASQUERADE"
		ip saddr 172.27.0.0/16 oifname != "br-532f00479926" counter packets 0 bytes 0 xt target "MASQUERADE"
		ip saddr 192.168.49.2 ip daddr 192.168.49.2 tcp dport 32443 counter packets 0 bytes 0 xt target "MASQUERADE"
		ip saddr 192.168.49.2 ip daddr 192.168.49.2 tcp dport 8443 counter packets 0 bytes 0 xt target "MASQUERADE"
		ip saddr 192.168.49.2 ip daddr 192.168.49.2 tcp dport 5000 counter packets 0 bytes 0 xt target "MASQUERADE"
		ip saddr 192.168.49.2 ip daddr 192.168.49.2 tcp dport 2376 counter packets 0 bytes 0 xt target "MASQUERADE"
		ip saddr 192.168.49.2 ip daddr 192.168.49.2 tcp dport 22 counter packets 0 bytes 0 xt target "MASQUERADE"
	}

	chain PREROUTING {
		type nat hook prerouting priority dstnat; policy accept;
		xt match "addrtype" counter packets 0 bytes 0 jump DOCKER
	}

	chain OUTPUT {
		type nat hook output priority dstnat; policy accept;
		ip daddr != 127.0.0.0/8 xt match "addrtype" counter packets 0 bytes 0 jump DOCKER
	}
}
# Warning: table ip filter is managed by iptables-nft, do not touch!
table ip filter {
	chain DOCKER {
		ip daddr 192.168.49.2 iifname != "br-ea17f7412758" oifname "br-ea17f7412758" tcp dport 32443 counter packets 0 bytes 0 accept
		ip daddr 192.168.49.2 iifname != "br-ea17f7412758" oifname "br-ea17f7412758" tcp dport 8443 counter packets 0 bytes 0 accept
		ip daddr 192.168.49.2 iifname != "br-ea17f7412758" oifname "br-ea17f7412758" tcp dport 5000 counter packets 0 bytes 0 accept
		ip daddr 192.168.49.2 iifname != "br-ea17f7412758" oifname "br-ea17f7412758" tcp dport 2376 counter packets 0 bytes 0 accept
		ip daddr 192.168.49.2 iifname != "br-ea17f7412758" oifname "br-ea17f7412758" tcp dport 22 counter packets 0 bytes 0 accept
	}

	chain DOCKER-ISOLATION-STAGE-1 {
		iifname "docker0" oifname != "docker0" counter packets 0 bytes 0 jump DOCKER-ISOLATION-STAGE-2
		iifname "br-f6ceae761663" oifname != "br-f6ceae761663" counter packets 0 bytes 0 jump DOCKER-ISOLATION-STAGE-2
		iifname "br-f2d76f96f92c" oifname != "br-f2d76f96f92c" counter packets 0 bytes 0 jump DOCKER-ISOLATION-STAGE-2
		iifname "br-ea17f7412758" oifname != "br-ea17f7412758" counter packets 26 bytes 2256 jump DOCKER-ISOLATION-STAGE-2
		iifname "br-532f00479926" oifname != "br-532f00479926" counter packets 0 bytes 0 jump DOCKER-ISOLATION-STAGE-2
		counter packets 50 bytes 9547 return
	}

	chain DOCKER-ISOLATION-STAGE-2 {
		oifname "docker0" counter packets 0 bytes 0 drop
		oifname "br-f6ceae761663" counter packets 0 bytes 0 drop
		oifname "br-f2d76f96f92c" counter packets 0 bytes 0 drop
		oifname "br-ea17f7412758" counter packets 0 bytes 0 drop
		oifname "br-532f00479926" counter packets 0 bytes 0 drop
		counter packets 26 bytes 2256 return
	}

	chain FORWARD {
		type filter hook forward priority filter; policy drop;
		counter packets 50 bytes 9547 jump DOCKER-USER
		counter packets 50 bytes 9547 jump DOCKER-ISOLATION-STAGE-1
		oifname "docker0" xt match "conntrack" counter packets 0 bytes 0 accept
		oifname "docker0" counter packets 0 bytes 0 jump DOCKER
		iifname "docker0" oifname != "docker0" counter packets 0 bytes 0 accept
		iifname "docker0" oifname "docker0" counter packets 0 bytes 0 accept
		oifname "br-f6ceae761663" xt match "conntrack" counter packets 0 bytes 0 accept
		oifname "br-f6ceae761663" counter packets 0 bytes 0 jump DOCKER
		iifname "br-f6ceae761663" oifname != "br-f6ceae761663" counter packets 0 bytes 0 accept
		iifname "br-f6ceae761663" oifname "br-f6ceae761663" counter packets 0 bytes 0 accept
		oifname "br-f2d76f96f92c" xt match "conntrack" counter packets 0 bytes 0 accept
		oifname "br-f2d76f96f92c" counter packets 0 bytes 0 jump DOCKER
		iifname "br-f2d76f96f92c" oifname != "br-f2d76f96f92c" counter packets 0 bytes 0 accept
		iifname "br-f2d76f96f92c" oifname "br-f2d76f96f92c" counter packets 0 bytes 0 accept
		oifname "br-ea17f7412758" xt match "conntrack" counter packets 24 bytes 7291 accept
		oifname "br-ea17f7412758" counter packets 0 bytes 0 jump DOCKER
		iifname "br-ea17f7412758" oifname != "br-ea17f7412758" counter packets 26 bytes 2256 accept
		iifname "br-ea17f7412758" oifname "br-ea17f7412758" counter packets 0 bytes 0 accept
		oifname "br-532f00479926" xt match "conntrack" counter packets 0 bytes 0 accept
		oifname "br-532f00479926" counter packets 0 bytes 0 jump DOCKER
		iifname "br-532f00479926" oifname != "br-532f00479926" counter packets 0 bytes 0 accept
		iifname "br-532f00479926" oifname "br-532f00479926" counter packets 0 bytes 0 accept
	}

	chain DOCKER-USER {
		counter packets 50 bytes 9547 return
	}
}

Offline

#4 2024-06-15 14:00:43

guilehm
Member
Registered: 2023-02-01
Posts: 12

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

The connection works fine when I use my mobile's 5G hotspot, but fails with my home Wi-Fi network.

I tried few more things:

- Disabled MAC Address Randomization:

sudo vim /etc/NetworkManager/conf.d/wifi_rand_mac.conf

[device]
wifi.scan-rand-mac-address=no

- Restored my router to default settings

- Set Wi-Fi to 2.4GHz Instead of Auto

- Tried different Wi-Fi channels: 1, 6, 11

- Updated the BIOS of my motherboard (since i'm using its wi-fi)

- Updated the Wi-Fi drivers and Firmware:

sudo pacman -Syu
sudo pacman -S linux-firmware

And the problem persists...

Motherboard: UF GAMING X670E-PLUS WIFI
Wi-Fi Driver in Use: mt7921e

Last edited by guilehm (2024-06-15 16:52:17)

Offline

#5 2024-06-15 21:20:41

AaAaAAaaAAaARCH
Member
Registered: 2024-02-29
Posts: 42

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

You can try:
- manual scan using iwlist
- disabling power saving for the wireless card
- enable debug output of wpa_supplicant

It is hard to help you with the very limited logs you have posted.

Offline

#6 2024-06-15 21:48:16

seth
Member
Registered: 2012-09-03
Posts: 64,179

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

NM enables wpa_supplicant debugging anyway, please post your complete system journal for the boot: 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

not some random filter.
When you attempted the manual connection w/ wpa_supplicant, did you stop NM beforehand?

Both services are active.

NM invokes wpa_supplicant itself, you're not supposed to have that enabled.
Please post the output of

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

I was using it normally yesterday, and today this problem started.

So what changed between yesterday and today?

The connection works fine when I use my mobile's 5G hotspot, but fails with my home Wi-Fi network.

- Set Wi-Fi to 2.4GHz Instead of Auto

Wouldn't it make more sense to lock 5GHz?
There's gonna be more noise on 2.4GHz (incl. bluetooth, DECT and a broken microwave) but the channel selection would rather have helped you out with that.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2024-06-16 17:35:22

guilehm
Member
Registered: 2023-02-01
Posts: 12

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

AaAaAAaaAAaARCH wrote:

You can try:
- manual scan using iwlist
- disabling power saving for the wireless card
- enable debug output of wpa_supplicant

It is hard to help you with the very limited logs you have posted.

Thanks for your help

- I disabled the power saving and got the same result

- Debug logs using wpa_supplicant

- Complete system journal logs

- Logs using NetworkManager with iwd backend (I just installed it):


seth wrote:

Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
awsvpnclient.service                     | multi-user.target.wants
bluetooth.service                        | bluetooth.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service    | system
dbus-org.freedesktop.timesync1.service   | system
display-manager.service                  | system
docker.service                           | multi-user.target.wants
fstrim.timer                             | timers.target.wants
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
iwd.service                              | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
nvidia-suspend.service                   | systemd-suspend.service.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-resolved.service                 | sysinit.target.wants
systemd-timesyncd.service                | sysinit.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants
seth wrote:

When you attempted the manual connection w/ wpa_supplicant, did you stop NM beforehand?

Yes, I stopped the NM service before trying

seth wrote:

Wouldn't it make more sense to lock 5GHz?

I locked 5GHz and no success

seth wrote:

So what changed between yesterday and today?

I worked the entire day, but I don't remember exactly what I did on the system, possibly upgraded it using: sudo pacman -Syu

Last edited by guilehm (2024-06-16 18:08:40)

Offline

#8 2024-06-16 19:39:25

AaAaAAaaAAaARCH
Member
Registered: 2024-02-29
Posts: 42

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

nl80211: Authenticate (ifindex=3)
  * bssid=84:0b:bb:77:08:3f
  * freq=5745
  * SSID=ZeroDay
  * IEs - hexdump(len=0): [NULL]
  * Auth Type 0
nl80211: Authentication request send successfully
RTM_NEWLINK: ifi_index=3 ifname=wlan0 wext ifi_family=0 ifi_flags=0x1003 ([UP])
nl80211: Drv Event 19 (NL80211_CMD_NEW_STATION) received for wlan0
nl80211: New station 84:0b:bb:77:08:3f
nl80211: Drv Event 20 (NL80211_CMD_DEL_STATION) received for wlan0
nl80211: Delete station 84:0b:bb:77:08:3f
nl80211: Drv Event 37 (NL80211_CMD_AUTHENTICATE) received for wlan0
nl80211: MLME event 37; timeout with 84:0b:bb:77:08:3f
wlan0: Event AUTH_TIMED_OUT (13) received
wlan0: SME: Authentication timed out

It looks like you can scan and find the AP, but you fail to send any data to it or fail to receive the response. Or the AP completely ignores your request (check AP logs for that).

- I disabled the power saving and got the same result

Like this? https://github.com/lwfinger/rtw88/issue … 1023821042

possibly upgraded it using: sudo pacman -Syu

look for that in /var/log/pacman.log, maybe check if the driver was updated as part of a kernel upgrade. Try the LTS kernel.

Do you reboot into linux? try turning of the computer entirely, and do a cold boot into linux.

When you tested windows, did you do it at the same location/distance of the AP?

Last edited by AaAaAAaaAAaARCH (2024-06-16 19:47:46)

Offline

#9 2024-06-16 21:47:31

seth
Member
Registered: 2012-09-03
Posts: 64,179

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

You've NM and iwd enabled, disable iwd. If you want to use it as NM backend follow https://wiki.archlinux.org/title/Networ … Fi_backend
If the issue remains, post an updated journal covering the failure - right now they're tripping over each other for absolutely sure.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#10 2024-06-17 20:46:38

guilehm
Member
Registered: 2023-02-01
Posts: 12

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

It looks like you can scan and find the AP, but you fail to send any data to it or fail to receive the response. Or the AP completely ignores your request (check AP logs for that).

Correct, I can see the wifi list using: nmcli device wifi list

I also can connect to my mobile's 5G hotspot using wpa_supplicant and iwd

Unfortunatelly my router is not generating any logs, a hard reset wasn't enough

look for that in /var/log/pacman.log, maybe check if the driver was updated as part of a kernel upgrade.

no changes for the driver

cat /var/log/pacman.log |grep mt7921e

Do you reboot into linux? try turning of the computer entirely, and do a cold boot into linux.

I rarely use Windows, so I didn't setup grub
I run it from the BIOS when I want
But I tried everything, also disconnecting it from the power and tried again

It's a desktop computer, so I'm trying to connect from the same distance, and the router is right next to the computer

Like this? https://github.com/lwfinger/rtw88/issue … 1023821042

Exactly, just like that

You've NM and iwd enabled, disable iwd. If you want to use it as NM backend follow https://wiki.archlinux.org/title/Networ … Fi_backend
If the issue remains, post an updated journal covering the failure - right now they're tripping over each other for absolutely sure.

I didn't have iwd, I installed it just for testing following the same example as you sent

All logs:
this log here without iwd
this log here with iwd
this log using wpa_supplicant
full output of journal with all logs

Offline

#11 2024-06-17 20:59:10

seth
Member
Registered: 2012-09-03
Posts: 64,179

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

First and last log seem the same, inbetween a filter for NM and the output of wpa_supplicant in isolation.
Regardless of why you did this, you cannot run iwd and wpa_supplicant in parallel and expect any sane behavior and enabling the iwd service is explicitly NOT how to use it as backend for NM.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#12 2024-06-17 21:38:29

guilehm
Member
Registered: 2023-02-01
Posts: 12

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

seth wrote:

First and last log seem the same, inbetween a filter for NM and the output of wpa_supplicant in isolation.
Regardless of why you did this, you cannot run iwd and wpa_supplicant in parallel and expect any sane behavior and enabling the iwd service is explicitly NOT how to use it as backend for NM.

I tried them individually, stopped wpa_supplicant using: `sudo systemctl disable / stop wpa_supplicant` (rebooted the pc) to try using iwd with this config:

[device]
wifi.backend=iwd

I did the same with NetworkManager, disabled it, and then tried to use only wpa_supplicant directly running: sudo wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf

I'm not sure what else to try at this point
My next step is to borrow a router and see if changing it resolves the issue

Since I'm able to connect via my personal hotspot, it seems likely that the problem could be with my current router (what is weird is that my TV, mobile, Mac and Windows can connect)

Last edited by guilehm (2024-06-17 21:39:37)

Offline

#13 2024-06-17 21:53:38

seth
Member
Registered: 2012-09-03
Posts: 64,179

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

Please post a journal covering the failure where iwd and wpa_supplicant are not tripping over each other.
In case it's not clear - here's a random minute from the one that said "this log here without iwd":

Jun 16 17:16:48 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16
Jun 16 17:16:48 gui iwd[806]: event: state, old: disconnected, new: autoconnect_quick
Jun 16 17:16:48 gui wpa_supplicant[12155]: wlan0: WPS-PBC-ACTIVE
Jun 16 17:16:48 gui iwd[806]: Could not register frame watch type 00d0: -114
Jun 16 17:16:48 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Jun 16 17:16:48 gui wpa_supplicant[12155]: wlan0: WPS-CANCEL
Jun 16 17:16:48 gui NetworkManager[12134]: <info>  [1718569008.6569] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 SAE'
Jun 16 17:16:48 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Jun 16 17:16:49 gui iwd[806]: event: connect-info, ssid: AccessDenied, bss: 84:0b:bb:77:08:38, signal: -53, load: 127/255
Jun 16 17:16:49 gui iwd[806]: event: state, old: autoconnect_quick, new: connecting (auto)
Jun 16 17:16:49 gui iwd[806]: CMD_SET_CQM failed: Operation not supported
Jun 16 17:16:49 gui iwd[806]: event: connect-timeout, reason: 2
Jun 16 17:16:49 gui iwd[806]: event: connect-failed, status: 1
Jun 16 17:16:49 gui iwd[806]: event: state, old: connecting (auto), new: disconnected
Jun 16 17:16:49 gui iwd[806]: event: state, old: disconnected, new: autoconnect_full
Jun 16 17:16:51 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Jun 16 17:16:52 gui iwd[806]: event: connect-info, ssid: ZeroDay, bss: 84:0b:bb:77:08:3f, signal: -55, load: 17/255
Jun 16 17:16:52 gui iwd[806]: event: state, old: autoconnect_full, new: connecting (auto)
Jun 16 17:16:52 gui iwd[806]: CMD_SET_CQM failed: Operation not supported
Jun 16 17:16:52 gui wpa_supplicant[12155]: wlan0: SME: Trying to authenticate with 84:0b:bb:77:08:38 (SSID='AccessDenied' freq=2462 MHz)
Jun 16 17:16:52 gui iwd[806]: event: connect-timeout, reason: 2
Jun 16 17:16:52 gui iwd[806]: event: connect-failed, status: 1
Jun 16 17:16:52 gui iwd[806]: event: state, old: connecting (auto), new: disconnected
Jun 16 17:16:52 gui iwd[806]: event: state, old: disconnected, new: autoconnect_full
Jun 16 17:16:54 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Jun 16 17:16:58 gui wpa_supplicant[12155]: wlan0: SME: Trying to authenticate with 84:0b:bb:77:08:38 (SSID='AccessDenied' freq=2462 MHz)
Jun 16 17:16:59 gui iwd[806]: Unexpected connection related event -- is another supplicant running?
Jun 16 17:17:02 gui wpa_supplicant[12155]: wlan0: SME: Trying to authenticate with 84:0b:bb:77:08:38 (SSID='AccessDenied' freq=2462 MHz)
Jun 16 17:17:02 gui iwd[806]: Unexpected connection related event -- is another supplicant running?
Jun 16 17:17:02 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=1 ssid="AccessDenied" auth_failures=1 duration=10 reason=CONN_FAILED
Jun 16 17:17:12 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-SSID-REENABLED id=1 ssid="AccessDenied"
Jun 16 17:17:12 gui wpa_supplicant[12155]: wlan0: SME: Trying to authenticate with 84:0b:bb:77:08:38 (SSID='AccessDenied' freq=2462 MHz)
Jun 16 17:17:12 gui iwd[806]: Unexpected connection related event -- is another supplicant running?
Jun 16 17:17:12 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=1 ssid="AccessDenied" auth_failures=2 duration=20 reason=CONN_FAILED
Jun 16 17:17:14 gui iwd[806]: event: state, old: disconnected, new: autoconnect_quick
Jun 16 17:17:14 gui iwd[806]: Could not register frame watch type 00d0: -114
Jun 16 17:17:14 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16
Jun 16 17:17:14 gui iwd[806]: event: state, old: autoconnect_quick, new: autoconnect_full
Jun 16 17:17:14 gui iwd[806]: event: state, old: disconnected, new: autoconnect_quick
Jun 16 17:17:14 gui NetworkManager[12134]: <info>  [1718569034.7565] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 SAE'
Jun 16 17:17:14 gui iwd[806]: Could not register frame watch type 00d0: -114
Jun 16 17:17:14 gui wpa_supplicant[12155]: wlan0: SME: Trying to authenticate with 84:0b:bb:77:08:3f (SSID='ZeroDay' freq=5745 MHz)
Jun 16 17:17:14 gui wpa_supplicant[12155]: wlan0: SME: Authentication request to the driver failed
Jun 16 17:17:14 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=1 ssid="ZeroDay" auth_failures=1 duration=10 reason=CONN_FAILED
Jun 16 17:17:15 gui iwd[806]: event: state, old: autoconnect_quick, new: autoconnect_full
Jun 16 17:17:24 gui NetworkManager[12134]: <warn>  [1718569044.5453] device (wlan0): Deactivation failed: GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected
Jun 16 17:17:24 gui iwd[806]: event: state, old: disconnected, new: autoconnect_quick
Jun 16 17:17:24 gui iwd[806]: Could not register frame watch type 00d0: -114
Jun 16 17:17:24 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16
Jun 16 17:17:25 gui iwd[806]: event: state, old: autoconnect_quick, new: autoconnect_full
Jun 16 17:17:25 gui iwd[806]: event: state, old: disconnected, new: autoconnect_quick
Jun 16 17:17:25 gui wpa_supplicant[12155]: wlan0: WPS-PBC-ACTIVE
Jun 16 17:17:25 gui iwd[806]: Could not register frame watch type 00d0: -114
Jun 16 17:17:25 gui NetworkManager[12134]: <info>  [1718569045.3032] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 SAE'
Jun 16 17:17:25 gui wpa_supplicant[12155]: wlan0: WPS-CANCEL
Jun 16 17:17:25 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Jun 16 17:17:25 gui iwd[806]: event: state, old: autoconnect_quick, new: autoconnect_full
Jun 16 17:17:25 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Jun 16 17:17:26 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Jun 16 17:17:28 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 16 17:17:29 gui iwd[806]: event: state, old: disconnected, new: autoconnect_quick
Jun 16 17:17:29 gui iwd[806]: Could not register frame watch type 00d0: -114
Jun 16 17:17:29 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16
Jun 16 17:17:29 gui iwd[806]: event: state, old: autoconnect_quick, new: autoconnect_full
Jun 16 17:17:30 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16
Jun 16 17:17:34 gui iwd[806]: event: state, old: disconnected, new: autoconnect_quick
Jun 16 17:17:34 gui iwd[806]: Could not register frame watch type 00d0: -114
Jun 16 17:17:34 gui iwd[806]: event: state, old: autoconnect_quick, new: autoconnect_full
Jun 16 17:17:38 gui NetworkManager[12134]: <info>  [1718569058.4457] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 SAE'
Jun 16 17:17:38 gui wpa_supplicant[12155]: wlan0: SME: Trying to authenticate with 84:0b:bb:77:08:3f (SSID='ZeroDay' freq=5745 MHz)
Jun 16 17:17:38 gui iwd[806]: Unexpected connection related event -- is another supplicant running?
Jun 16 17:17:38 gui wpa_supplicant[12155]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="ZeroDay" auth_failures=1 duration=10 reason=CONN_FAILED

nb. also the "Unexpected connection related event -- is another supplicant running" messages.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#14 2024-06-17 22:19:51

guilehm
Member
Registered: 2023-02-01
Posts: 12

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

Sure, here are the logs showing the attempt to connect to ZeroDay (my home Wi-Fi which fails) and the successful connection to my personal hotspot "Guilherme"

Offline

#15 2024-06-17 22:48:30

AaAaAAaaAAaARCH
Member
Registered: 2024-02-29
Posts: 42

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

The driver is part of the kernel, e.g. the "linux" package.

cat /var/log/pacman.log | grep " linux"

If you know what was updated arround the time it stopped working, you can search the kernel diffs for changes to your drivers inbetween those versions.

Offline

#16 2024-06-17 23:06:29

guilehm
Member
Registered: 2023-02-01
Posts: 12

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

AaAaAAaaAAaARCH wrote:

The driver is part of the kernel, e.g. the "linux" package.

cat /var/log/pacman.log | grep " linux"

If you know what was updated arround the time it stopped working, you can search the kernel diffs for changes to your drivers inbetween those versions.

There were no changes around June 11 or 12
It changed June 13, which is when I started trying to resolve it

cat /var/log/pacman.log | grep " linux"
...
[2024-05-24T21:45:08-0300] [ALPM] upgraded linux-api-headers (6.4-1 -> 6.8-1)
[2024-05-24T21:45:24-0300] [ALPM] upgraded linux (6.7.2.arch1-2 -> 6.9.1.arch1-2)
[2024-05-24T21:45:24-0300] [ALPM] upgraded linux-firmware-whence (20240115.9b6d0b08-2 -> 20240510.b9d2bf23-1)
[2024-05-24T21:45:25-0300] [ALPM] upgraded linux-firmware (20240115.9b6d0b08-2 -> 20240510.b9d2bf23-1)
[2024-05-24T21:45:26-0300] [ALPM] upgraded linux-headers (6.7.2.arch1-2 -> 6.9.1.arch1-2)
[2024-05-28T10:17:11-0300] [ALPM] upgraded linux (6.9.1.arch1-2 -> 6.9.2.arch1-1)
[2024-05-28T10:17:12-0300] [ALPM] upgraded linux-headers (6.9.1.arch1-2 -> 6.9.2.arch1-1)
[2024-06-13T10:48:23-0300] [ALPM] upgraded linux (6.9.2.arch1-1 -> 6.9.4.arch1-1)
[2024-06-13T10:48:23-0300] [ALPM] upgraded linux-firmware-whence (20240510.b9d2bf23-1 -> 20240610.9c10a208-1)
[2024-06-13T10:48:24-0300] [ALPM] upgraded linux-firmware (20240510.b9d2bf23-1 -> 20240610.9c10a208-1)
[2024-06-13T10:48:25-0300] [ALPM] upgraded linux-headers (6.9.2.arch1-1 -> 6.9.4.arch1-1)

Offline

#17 2024-06-18 07:00:20

seth
Member
Registered: 2012-09-03
Posts: 64,179

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

Connecting to guilherme isn't a smooth sail either:

Jun 17 22:20:36 gui wpa_supplicant[991]: wlan0: Authentication with 46:0e:ab:79:a3:b1 timed out.
Jun 17 22:20:36 gui wpa_supplicant[991]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Guilherme" auth_failures=1 duration=10 reason=CONN_FAILED

Your home AP might just have a little less patience.

What sticks out in the journal is that docker is throwing a complete tantrum over DNS failures, the bridge flickers

Jun 17 22:19:41 gui kernel: vethf241cf78: entered allmulticast mode
Jun 17 22:19:41 gui kernel: vethf241cf78: entered promiscuous mode
Jun 17 22:19:41 gui kernel: bridge: port 12(vethf241cf78) entered blocking state
Jun 17 22:19:41 gui kernel: bridge: port 12(vethf241cf78) entered forwarding state
Jun 17 22:19:41 gui kernel: bridge: port 13(veth6fae1aae) entered blocking state
Jun 17 22:19:41 gui kernel: bridge: port 13(veth6fae1aae) entered disabled state

probably leading to

Jun 17 22:19:43 gui kernel: iptables[14195]: segfault at 80 ip 0000792441da4964 sp 00007fff97e78898 error 4 in libnftnl.so.11.2.0[792441d9f000+19000] likely on CPU 10 (core 12, socket 0)
Jun 17 22:19:43 gui kernel: Code: 83 c4 08 5b 5d 41 5c 41 5d c3 0f 1f 40 00 48 83 c4 08 31 c0 5b 5d 41 5c 41 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa <48> 8b 87 80 00 00 00 48 83 ef 80 48 39 f8 74 1b 85 f6 75 0c eb 18
Jun 17 22:19:43 gui systemd[1]: Created slice Slice /system/systemd-coredump.
Jun 17 22:19:43 gui systemd[1]: Started Process Core Dump (PID 14197/UID 0).
Jun 17 22:19:44 gui systemd-coredump[14210]: Process 14195 (iptables) of user 0 dumped core.
                                             
                                             Stack trace of thread 10873:
                                             #0  0x0000792441da4964 n/a (/usr/lib/x86_64-linux-gnu/libnftnl.so.11.2.0 + 0xe964)
                                             ELF object binary architecture: AMD x86-64

iptables crashing in libnft (multiple times)

=> Is there ayn change in behavior of you calm the waters and disable dockerd/containerd?
(I assume the bridges only come from there, too?)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#18 2024-06-18 12:36:35

guilehm
Member
Registered: 2023-02-01
Posts: 12

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

seth wrote:

=> Is there ayn change in behavior of you calm the waters and disable dockerd/containerd?
(I assume the bridges only come from there, too?)

I removed all docker networks

docker network rm 532f00479926 6e54b48d7771 f6ceae761663 f2d76f96f92c 98cab5b9f993 64a6f79abb80

Stopped and disabled the service

sudo systemctl stop docker
sudo systemctl disable docker

sudo systemctl stop docker.socket
sudo systemctl disable docker.socket

Rebooted

when I list the networks:

ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether c8:7f:54:04:bf:47 brd ff:ff:ff:ff:ff:ff
    altname enp10s0
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DORMANT group default qlen 1000
    link/ether 42:2a:3f:a6:c8:72 brd ff:ff:ff:ff:ff:ff permaddr 10:6f:d9:db:eb:3b

No more docker networks, so I tried again got the same result, but now my personal hotspot is unpatient too

logs here

Offline

#19 2024-06-18 16:14:01

seth
Member
Registered: 2012-09-03
Posts: 64,179

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

but now my personal hotspot is unpatient too

The journal has only connection attempts to SSID='ZeroDay' freq=5180 MHz

Your OP had 

wifi.scan-rand-mac-address=no

which otherwise would have been a strong contender for the cause … and probably still is because

Jun 18 12:30:27 gui NetworkManager[803]: <info>  [1718724627.4646] device (wlan0): set-hw-addr: set MAC address to C6:9D:26:A4:AD:0E (scanning)
Jun 18 12:31:42 gui NetworkManager[803]: <info>  [1718724702.1056] device (wlan0): set-hw-addr: set MAC address to 86:A7:F8:B8:CF:29 (scanning)
Jun 18 12:31:48 gui NetworkManager[803]: <info>  [1718724708.1748] device (wlan0): set-hw-addr: set MAC address to 96:A7:DD:88:4F:C6 (scanning)
Jun 18 12:32:16 gui NetworkManager[803]: <info>  [1718724736.1117] device (wlan0): set-hw-addr: set MAC address to FA:1B:D9:A0:A9:EB (scanning)
Jun 18 12:32:44 gui NetworkManager[803]: <info>  [1718724764.1082] device (wlan0): set-hw-addr: set MAC address to D2:5E:73:17:E5:6D (scanning)

https://wiki.archlinux.org/title/Networ … domization

In doubt stop and disable NM, reboot the computer and your AP (router) and try to connect w/ wifi-menu from the netctl package.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#20 2024-06-18 18:00:23

guilehm
Member
Registered: 2023-02-01
Posts: 12

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

seth wrote:

In doubt stop and disable NM, reboot the computer and your AP (router) and try to connect w/ wifi-menu from the netctl package.

Thank you seth and AaAaAAaaAAaARCH very much for your help!

I followed your advice to disable NetworkManager and use wifi-menu to connect to my WiFi, and it worked perfectly

logs here using wifi-menu

Are there any concerns or potential issues with not using NetworkManager that I should be aware of?

What do you think about all that?

Offline

#21 2024-06-18 18:10:10

seth
Member
Registered: 2012-09-03
Posts: 64,179

Re: [SOLVED] Wi-Fi Connection Issues - NetworkManager, WPA Supplicant

NM probably has the best integration with the bigger desktop environments like gnome or KDE but has no substantial functional advantages over other ways to configure your network.

However, I'm now almost convinced that you somehow failed to deactivate the MAC randomization and that's what's causing your AP to sulk (because that's not uncommon)
=> Make sure to get the randomization effectively disabled and see whether you can continue to use NM this way if you see any benefit in it.

Edit: Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Last edited by seth (2024-06-18 18:10:37)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB