[SOLVED] wlan interface deauthenticated and soft blocked sporadically

Rogach · 2022-12-07 15:26:38

After yesterday's update my system started sporadically losing network connection. WLAN interface (wlo1) switches to "down" state, rfkill lists wlan as blocked. Here's the log with relevant entries:

Dec 07 13:20:48 hostname kernel: wlo1: deauthenticating from 86:83:c2:3b:24:f1 by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 07 13:20:48 hostname wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 13:20:48 hostname wpa_supplicant[18023]: BSSID 86:83:c2:3b:24:f1 ignore list count incremented to 2, ignoring for 10 seconds
Dec 07 13:20:48 hostname avahi-daemon[747]: Interface wlo1.IPv4 no longer relevant for mDNS.
Dec 07 13:20:48 hostname avahi-daemon[747]: Leaving mDNS multicast group on interface wlo1.IPv4 with address 10.5.196.220.
Dec 07 13:20:48 hostname avahi-daemon[747]: Withdrawing address record for 10.5.196.220 on wlo1.
Dec 07 13:20:48 hostname wpa_supplicant[18023]: rfkill: WLAN soft blocked
Dec 07 13:20:48 hostname wpa_supplicant[18023]: rfkill: WLAN soft blocked
Dec 07 13:20:48 hostname NetworkManager[762]: <info>  [1670408448.8689] manager: rfkill: Wi-Fi now disabled by radio killswitch

Kernel version: 6.0.11-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 02 Dec 2022 17:25:31 +0000 x86_64 GNU/Linux

I use NetworkManager for connection management.

System goes back to normal if I execute these commands:

$ rfkill unblock all
$ ip link set dev wlo1 up

But this is only temporary, after a while (15-120 minutes) the issue comes back.

How can I debug this further? What could be causing these "deauthenticating" events?

Last edited by Rogach (2022-12-14 06:48:03)

Slithery · 2022-12-07 15:38:19

'hostname' isn't a valid hostname - try setting it to something else...
https://wiki.archlinux.org/title/Networ … e_hostname

Rogach · 2022-12-07 16:11:42

I know, the real hostname is different. I just redacted it out as I thought it to be irrelevant

Slithery · 2022-12-07 17:14:52

Rogach wrote:

I know, the real hostname is different. I just redacted it out as I thought it to be irrelevant

As you can see from my previous reply redacting things that you think are irrelevant doesn't help anyone, it just leads to confusion.

Rogach wrote:

Here's the log with relevant entries:

Why do you think that those are the only relevant entries? Please post a full, unredacted log.
https://bbs.archlinux.org/viewtopic.php?id=57855

Rogach · 2022-12-07 17:30:18

Here's the full log: http://0x0.st/odTt.txt

seth · 2022-12-07 20:16:37

Dec 07 10:03:53 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 10:07:38 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 10:09:47 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 12:02:07 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 12:16:50 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 12:33:08 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 13:11:25 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 13:20:48 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 13:58:53 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 14:06:21 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 18:03:23 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 18:27:05 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 18:29:38 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 19:11:52 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 19:53:07 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 19:54:27 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 19:55:15 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 19:55:57 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 19:57:01 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3a:24:f1 reason=3 locally_generated=1
Dec 07 19:58:28 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 19:58:51 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 19:59:44 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1
Dec 07 20:03:43 one-two-three wpa_supplicant[18023]: wlo1: CTRL-EVENT-DISCONNECTED bssid=86:83:c2:3b:24:f1 reason=3 locally_generated=1

Probably because of

Dec 07 18:18:29 one-two-three NetworkManager[3040830]: <warn>  [1670426309.9440] ipv6ll[70b9481ff4b581c9,ifindex=2]: changed: no IPv6 link local address to retry after Duplicate Address Detection failures (back off)
Dec 07 18:18:39 one-two-three NetworkManager[3040830]: <warn>  [1670426319.9495] platform-linux: do-add-ip6-address[2: fe80::b4bb:9eee:1f0c:51b9]: failure 95 (Operation not supported)
Dec 07 18:18:41 one-two-three NetworkManager[3040830]: <warn>  [1670426321.9512] platform-linux: do-add-ip6-address[2: fe80::5a26:aece:24b3:a136]: failure 95 (Operation not supported)
Dec 07 18:18:43 one-two-three NetworkManager[3040830]: <warn>  [1670426323.9515] platform-linux: do-add-ip6-address[2: fe80::312a:a56f:9883:820c]: failure 95 (Operation not supported)
Dec 07 18:18:45 one-two-three NetworkManager[3040830]: <warn>  [1670426325.9547] platform-linux: do-add-ip6-address[2: fe80::d4cf:5b4b:381c:f473]: failure 95 (Operation not supported)
Dec 07 18:18:47 one-two-three NetworkManager[3040830]: <warn>  [1670426327.9576] platform-linux: do-add-ip6-address[2: fe80::a4e7:bb29:bb91:b296]: failure 95 (Operation not supported)
Dec 07 18:18:49 one-two-three NetworkManager[3040830]: <warn>  [1670426329.9598] platform-linux: do-add-ip6-address[2: fe80::bd0:e44:c01b:1c72]: failure 95 (Operation not supported)

=> https://unix.stackexchange.com/question … orkmanager (but your device is wlo1)
You can also disable IPv6 enirely, https://wiki.archlinux.org/title/IPv6#Disable_IPv6
If that's not it, please post an updated journal.

Rogach · 2022-12-08 05:41:48

I already had IPv6 disabled via ipv6.disable=1 kernel parameter. But these errors were worrying me as well. I disabled ipv6 in NetworkManager as well (via "nmcli device modify wlo1 ipv6.method disabled").

"do-add-ip6-address" went away for now, will wait to see if network disconnects will still be happening.

Rogach · 2022-12-14 06:47:34

Disabling ipv6 in NetworkManager didn't help much, the errors still kept happening. But after several days they went away, and I can't reproduce them anymore. Will mark the thread as "solved" for now.

Rogach · 2023-02-24 17:36:28

I've finally found what was causing the issue, posting here just to add some closure to the thread.

The problem was due to my keypad - I have a keypad connected to my laptop (I use it for additional hotkeys). One of the keys on the keypad I remapped to keycode 247, which happens to be KEY_RFKILL. Thus when I pressed that key wifi module got immediately disabled, and network died. Remapping the key to a different keycode fixed the issue.

Arch Linux

#1 2022-12-07 15:26:38

[SOLVED] wlan interface deauthenticated and soft blocked sporadically

#2 2022-12-07 15:38:19

Re: [SOLVED] wlan interface deauthenticated and soft blocked sporadically

#3 2022-12-07 16:11:42

Re: [SOLVED] wlan interface deauthenticated and soft blocked sporadically

#4 2022-12-07 17:14:52

Re: [SOLVED] wlan interface deauthenticated and soft blocked sporadically

#5 2022-12-07 17:30:18

Re: [SOLVED] wlan interface deauthenticated and soft blocked sporadically

#6 2022-12-07 20:16:37

Re: [SOLVED] wlan interface deauthenticated and soft blocked sporadically

#7 2022-12-08 05:41:48

Re: [SOLVED] wlan interface deauthenticated and soft blocked sporadically

#8 2022-12-14 06:47:34

Re: [SOLVED] wlan interface deauthenticated and soft blocked sporadically

#9 2023-02-24 17:36:28

Re: [SOLVED] wlan interface deauthenticated and soft blocked sporadically

Board footer