[SOLVED] deauthenticating from MAC by local choice (Reason: 3

0x7o · 2023-10-27 12:18:04

Hey, everybody.
I installed Arch Linux a few days ago and started noticing intermittent disconnections from WiFi. As it turns out, every 7 minutes there is a deauthentication, which is accompanied by internet disconnection for a few tens of seconds. I am using NetworkManager.
Laptop: ASUS TUF Gaming F15 FX506LI_FX506LI

 ~  journalctl -b | grep deauth
Oct 27 19:57:45 archlinux kernel: wlan0: deauthenticating from 00:18:e7:f4:9c:3e by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 27 20:04:38 archlinux kernel: wlan0: deauthenticating from 00:18:e7:f4:9c:3e by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 27 20:11:31 archlinux kernel: wlan0: deauthenticating from 00:18:e7:f4:9c:3e by local choice (Reason: 3=DEAUTH_LEAVING)

 ~ journalctl -b | grep wlan0
Oct 27 20:11:31 archlinux kernel: wlan0: deauthenticating from 00:18:e7:f4:9c:3e by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 27 20:11:31 archlinux dhcpcd[505]: wlan0: carrier lost
Oct 27 20:11:31 archlinux NetworkManager[510]: <info>  [1698408691.0985] device (wlan0): set-hw-addr: set MAC address to CA:93:83:DF:99:D1 (scanning)
Oct 27 20:11:31 archlinux dhcpcd[505]: wlan0: deleting address fe80::6076:bf6e:8088:26e1
Oct 27 20:11:31 archlinux dhcpcd[505]: wlan0: deleting route to 192.168.0.0/24
Oct 27 20:11:31 archlinux dhcpcd[505]: wlan0: deleting default route via 192.168.0.1
Oct 27 20:11:31 archlinux dhcpcd[505]: wlan0: old hardware address: 0e:90:a5:29:d5:1e
Oct 27 20:11:31 archlinux dhcpcd[505]: wlan0: new hardware address: ca:93:83:df:99:d1
Oct 27 20:11:31 archlinux NetworkManager[510]: <info>  [1698408691.1326] device (wlan0): supplicant interface state: inactive -> disconnected
Oct 27 20:11:31 archlinux NetworkManager[510]: <info>  [1698408691.1327] device (p2p-dev-wlan0): supplicant management interface state: inactive -> disconnected
Oct 27 20:11:31 archlinux NetworkManager[510]: <info>  [1698408691.1380] device (wlan0): supplicant interface state: disconnected -> inactive
Oct 27 20:11:31 archlinux NetworkManager[510]: <info>  [1698408691.1381] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> inactive
Oct 27 20:11:31 archlinux wpa_supplicant[626]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-16
Oct 27 20:11:34 archlinux kernel: wlan0: authenticate with 00:18:e7:f4:9c:3e
Oct 27 20:11:34 archlinux kernel: wlan0: 80 MHz not supported, disabling VHT
Oct 27 20:11:34 archlinux kernel: wlan0: send auth to 00:18:e7:f4:9c:3e (try 1/3)
Oct 27 20:11:34 archlinux kernel: wlan0: authenticated
Oct 27 20:11:34 archlinux kernel: wlan0: associate with 00:18:e7:f4:9c:3e (try 1/3)
Oct 27 20:11:34 archlinux kernel: wlan0: RX AssocResp from 00:18:e7:f4:9c:3e (capab=0x431 status=0 aid=3)
Oct 27 20:11:34 archlinux kernel: wlan0: associated
Oct 27 20:11:34 archlinux wpa_supplicant[626]: wlan0: No network configuration found for the current AP
Oct 27 20:11:34 archlinux wpa_supplicant[626]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:18:e7:f4:9c:3e reason=3 locally_generated=1
Oct 27 20:11:34 archlinux wpa_supplicant[626]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Oct 27 20:11:34 archlinux wpa_supplicant[626]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Oct 27 20:11:34 archlinux NetworkManager[510]: <info>  [1698408694.1508] device (wlan0): supplicant interface state: inactive -> associated
Oct 27 20:11:34 archlinux NetworkManager[510]: <info>  [1698408694.1509] device (p2p-dev-wlan0): supplicant management interface state: inactive -> associated
Oct 27 20:11:34 archlinux NetworkManager[510]: <info>  [1698408694.1561] device (wlan0): supplicant interface state: associated -> disconnected
Oct 27 20:11:34 archlinux NetworkManager[510]: <info>  [1698408694.1561] device (p2p-dev-wlan0): supplicant management interface state: associated -> disconnected
Oct 27 20:11:34 archlinux dhcpcd[505]: wlan0: carrier acquired
Oct 27 20:11:34 archlinux dhcpcd[505]: wlan0: IAID 83:df:99:d1
Oct 27 20:11:34 archlinux dhcpcd[505]: wlan0: adding address fe80::d6e0:7cca:5d84:26f2
Oct 27 20:11:34 archlinux NetworkManager[510]: <info>  [1698408694.2555] device (wlan0): supplicant interface state: disconnected -> inactive
Oct 27 20:11:34 archlinux NetworkManager[510]: <info>  [1698408694.2555] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> inactive
Oct 27 20:11:34 archlinux dhcpcd[505]: wlan0: rebinding lease of 192.168.0.169
Oct 27 20:11:34 archlinux dhcpcd[505]: wlan0: NAK: from 192.168.0.1
Oct 27 20:11:34 archlinux dhcpcd[505]: wlan0: soliciting a DHCP lease
Oct 27 20:11:35 archlinux dhcpcd[505]: wlan0: soliciting an IPv6 router
Oct 27 20:11:38 archlinux dhcpcd[505]: wlan0: offered 192.168.0.170 from 192.168.0.1
Oct 27 20:11:38 archlinux dhcpcd[505]: wlan0: probing address 192.168.0.170/24
Oct 27 20:11:43 archlinux dhcpcd[505]: wlan0: leased 192.168.0.170 for 86400 seconds
Oct 27 20:11:43 archlinux dhcpcd[505]: wlan0: adding route to 192.168.0.0/24
Oct 27 20:11:43 archlinux dhcpcd[505]: wlan0: adding default route via 192.168.0.1
Oct 27 20:11:48 archlinux dhcpcd[505]: wlan0: no IPv6 Routers available

lspci -k
00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi
	DeviceName: Onboard - Ethernet
	Subsystem: Intel Corporation Wi-Fi 6 AX201 160MHz
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

Last edited by 0x7o (2023-10-29 12:19:46)

seth · 2023-10-27 13:56:08

I am using NetworkManager

No, you're using NM AND dhcpcd - at least.
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

Pick one, disable the other network manger(s)

Edit: assuming you're using dhcpcd as NM backend and there's no additional service, you're leaving by your own volition - NM suggests that "No network configuration found for the current AP" but for a better understanding, please don't filter the journal w/ random grabs (eg. kernel module errors won't show up, nor global NM actions)

Last edited by seth (2023-10-27 14:24:43)

0x7o · 2023-10-27 14:42:31

bluetooth.service                        | bluetooth.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
dhcpcd.service                           | multi-user.target.wants
getty@tty1.service                       | getty.target.wants
iwd.service                              | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.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-timesyncd.service                | sysinit.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

Sorry for the misinformation. All I did was use dhcpcd to connect to the network, and NetworkManager to automatically enable dhcpcd at system startup, as far as I understand.

seth · 2023-10-27 14:56:56

If you want to use NM,m disable dhcpcd and iwd.
If you want to use either as backend for NM, see https://wiki.archlinux.org/title/Networ … HCP_client and https://wiki.archlinux.org/title/Networ … Fi_backend

0x7o · 2023-10-27 14:59:49

What do you recommend in my case? Do you think the problem lies in their conflict?

seth · 2023-10-27 15:03:39

The conflict *will* cause this kind of symptoms, whether it's the only problem is to be seen.

What you want to use to manage your network is down to subjective preferences - I'm personally not a big fan of the nEtWoRk bY MaGiC approach of semi-smart suites, but that's me.
You might be more interested in NMs integration w/ your DE.

0x7o · 2023-10-29 11:06:47

I disabled NetworkManager and left only iwd with dhcpcd and indeed, the error no longer occurred. The connection is very stable. Thank you very much for your help!

seth · 2023-10-29 12:17:26

\o/
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.

Arch Linux

#1 2023-10-27 12:18:04

[SOLVED] deauthenticating from MAC by local choice (Reason: 3

#2 2023-10-27 13:56:08

Re: [SOLVED] deauthenticating from MAC by local choice (Reason: 3

#3 2023-10-27 14:42:31

Re: [SOLVED] deauthenticating from MAC by local choice (Reason: 3

#4 2023-10-27 14:56:56

Re: [SOLVED] deauthenticating from MAC by local choice (Reason: 3

#5 2023-10-27 14:59:49

Re: [SOLVED] deauthenticating from MAC by local choice (Reason: 3

#6 2023-10-27 15:03:39

Re: [SOLVED] deauthenticating from MAC by local choice (Reason: 3

#7 2023-10-29 11:06:47

Re: [SOLVED] deauthenticating from MAC by local choice (Reason: 3

#8 2023-10-29 12:17:26

Re: [SOLVED] deauthenticating from MAC by local choice (Reason: 3

Board footer