Re: Repeated Deauthentication event, reason: 4

James Prestwood <[email protected]> Fri, 3 Jan 2025 15:25:47 -0800
Newsgroups	dev.linux.lists.iwd
Message-ID	<[email protected]>
Hi,

On 1/3/25 2:16 PM, Owen Garland wrote:
> Hej all,
>
> I couldn't find an issue tracker so I am trying here. Essentially my
> problem is I get deauthenticated from AP's at seemingly random
> intervals, with `reason: 4`.
>
> iwd --version: 3.3
> OS: Arch-Linux 6.11.9-arch1-1
> Device: Dell XPS 9370
> Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
>          Subsystem: Intel Corporation Device 8050
>          Kernel driver in use: iwlwifi
>          Kernel modules: iwlwifi
> iwconfig:
>    wlan0     IEEE 802.11  ESSID:"Tronx_Upper"
>             Mode:Managed  Frequency:2.422 GHz  Access Point: 22:D2:CC:07:9C:B5
>             Bit Rate=65 Mb/s   Tx-Power=22 dBm
>             Retry short limit:7   RTS thr:off   Fragment thr:off
>             Power Management:off
>             Link Quality=31/70  Signal level=-79 dBm
>             Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>             Tx excessive retries:209  Invalid misc:664   Missed beacon:0
>
> The logs from `journactl -u iwd` show this:
>
> Jan 03 21:52:09 titanium systemd[1]: Starting Wireless service...
> Jan 03 21:52:09 titanium iwd[318201]: Wireless daemon version 3.3
> Jan 03 21:52:09 titanium iwd[318201]: Loaded configuration from
> /etc/iwd/main.conf
> Jan 03 21:52:09 titanium systemd[1]: Started Wireless service.
> Jan 03 21:52:09 titanium iwd[318201]: Wiphy: 0, Name: phy0
> Jan 03 21:52:09 titanium iwd[318201]:         Permanent Address:
> 64:5d:86:ed:80:5a
> Jan 03 21:52:09 titanium iwd[318201]:         2.4GHz Band:
> Jan 03 21:52:09 titanium iwd[318201]:                 Bitrates (non-HT):
> Jan 03 21:52:09 titanium iwd[318201]:                          1.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                          2.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                          5.5 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                         11.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                          6.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                          9.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                         12.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                         18.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                         24.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                         36.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                         48.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                         54.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                 HT Capabilities:
> Jan 03 21:52:09 titanium iwd[318201]:                         HT40
> Jan 03 21:52:09 titanium iwd[318201]:                         Short GI for 20Mhz
> Jan 03 21:52:09 titanium iwd[318201]:                         Short GI for 40Mhz
> Jan 03 21:52:09 titanium iwd[318201]:                 HT RX MCS indexes:
> Jan 03 21:52:09 titanium iwd[318201]:                         0-15
> Jan 03 21:52:09 titanium iwd[318201]:         5GHz Band:
> Jan 03 21:52:09 titanium iwd[318201]:                 Bitrates (non-HT):
> Jan 03 21:52:09 titanium iwd[318201]:                          6.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                          9.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                         12.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                         18.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                         24.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                         36.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                         48.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                         54.0 Mbps
> Jan 03 21:52:09 titanium iwd[318201]:                 HT Capabilities:
> Jan 03 21:52:09 titanium iwd[318201]:                         HT40
> Jan 03 21:52:09 titanium iwd[318201]:                         Short GI for 20Mhz
> Jan 03 21:52:09 titanium iwd[318201]:                         Short GI for 40Mhz
> Jan 03 21:52:09 titanium iwd[318201]:                 HT RX MCS indexes:
> Jan 03 21:52:09 titanium iwd[318201]:                         0-15
> Jan 03 21:52:09 titanium iwd[318201]:                 VHT Capabilities:
> Jan 03 21:52:09 titanium iwd[318201]:                         Short GI for 80Mhz
> Jan 03 21:52:09 titanium iwd[318201]:                         Max RX
> MCS: 0-9 for NSS: 2
> Jan 03 21:52:09 titanium iwd[318201]:                         Max TX
> MCS: 0-9 for NSS: 2
> Jan 03 21:52:09 titanium iwd[318201]:         Ciphers: BIP-CMAC-128
> CCMP-128 TKIP
> Jan 03 21:52:09 titanium iwd[318201]:         Supported iftypes:
> ad-hoc station ap p2p-client p2p-go p2p-device
> Jan 03 21:52:09 titanium iwd[318201]: event: state, old: disconnected,
> new: autoconnect_quick
> Jan 03 21:52:09 titanium iwd[318201]: udev interface=wlan0 ifindex=6
> Jan 03 21:52:10 titanium iwd[318201]: event: connect-info, ssid:
> Tronx_Upper, bss: 22:d2:cc:07:9c:b5, signal: -79, load: 0/255
> Jan 03 21:52:10 titanium iwd[318201]: event: state, old:
> autoconnect_quick, new: connecting (auto)
> Jan 03 21:52:10 titanium iwd[318201]: event: state, old: connecting
> (auto), new: connecting (netconfig)
> Jan 03 21:52:10 titanium iwd[318201]: event: state, old: connecting
> (netconfig), new: connected
> Jan 03 21:52:15 titanium iwd[318201]: event: roam-scan,
> <truncated>
> Jan 03 22:41:53 titanium iwd[318201]: Received Deauthentication event,
> reason: 4, from_ap: false
> Jan 03 22:41:53 titanium iwd[318201]: event: disconnect-info, reason: 4
> Jan 03 22:41:53 titanium iwd[318201]: event: state, old: connected,
> new: disconnected
> Jan 03 22:41:53 titanium iwd[318201]: event: state, old: disconnected,
> new: autoconnect_quick
> Jan 03 22:41:54 titanium iwd[318201]: event: state, old:
> autoconnect_quick, new: autoconnect_full
> Jan 03 22:42:13 titanium iwd[318201]: event: connect-info, ssid:
> Tronx_Upper, bss: 22:d2:cc:07:9c:b5, signal: -79, load: 0/255
> Jan 03 22:42:13 titanium iwd[318201]: event: state, old:
> autoconnect_full, new: connecting (auto)
> Jan 03 22:42:17 titanium iwd[318201]: event: state, old: connecting
> (auto), new: connecting (netconfig)
> Jan 03 22:42:18 titanium iwd[318201]: event: state, old: connecting
> (netconfig), new: connected
>
> This then appears to happen several times, and at seemingly random
> intervals. It can be fine for several hours, then there is one
> disconnect, or there may be a few disconnects in a short time. As an
> example the 28th had this:
>
>   Dec 28 15:40:49 titanium iwd[869]: Received Deauthentication event,
> reason: 4, from_ap: false
>   Dec 28 15:41:12 titanium iwd[869]: Received Deauthentication event,
> reason: 4, from_ap: false
>   Dec 28 16:02:27 titanium iwd[869]: Received Deauthentication event,
> reason: 4, from_ap: false
>   Dec 28 16:13:12 titanium iwd[869]: Received Deauthentication event,
> reason: 4, from_ap: false
>   Dec 28 16:13:27 titanium iwd[869]: Received Deauthentication event,
> reason: 4, from_ap: false
>   Dec 28 16:34:55 titanium iwd[869]: Received Deauthentication event,
> reason: 4, from_ap: false
>   Dec 28 17:02:41 titanium iwd[869]: Received Deauthentication event,
> reason: 4, from_ap: false
>   Dec 28 17:11:34 titanium iwd[869]: Received Deauthentication event,
> reason: 4, from_ap: false
>   Dec 28 17:16:38 titanium iwd[869]: Received Deauthentication event,
> reason: 4, from_ap: false
>   Dec 28 17:20:27 titanium iwd[869]: Received Deauthentication event,
> reason: 4, from_ap: false
>   Dec 28 17:25:01 titanium iwd[869]: Received Deauthentication event,
> reason: 4, from_ap: false
>   Dec 28 18:52:40 titanium iwd[869]: Received Deauthentication event,
> reason: 4, from_ap: false
>   Dec 28 20:21:20 titanium iwd[869]: Received Deauthentication event,
> reason: 4, from_ap: false
>   Dec 28 20:21:28 titanium iwd[869]: Received Deauthentication event,
> reason: 4, from_ap: false
>   Dec 28 20:21:46 titanium iwd[869]: Received Deauthentication event,
> reason: 4, from_ap: false
>   Dec 28 21:07:33 titanium iwd[869]: Received Deauthentication event,
> reason: 4, from_ap: false

Were there any additional kernel/IWD logs at those time? Its probably 
best to enable IWD debugging with the "-d" flag.

This reason code is "Disassociated due to inactivity" and a local 
disconnect, which we see in our deployments as well. Is your device 
operating in low RSSI conditions? I see when you connected the RSSI was 
-79 which is at or at least very quickly approaching unusable connection 
quality. I suspect this i

>
> My investigations haven't led to much, not having a publicly viewable
> issue tracker is certainly not helping. I have found a few other
> threads where people have had this issue, however none of the proposed
> remedies have made an impact. The one thing I did try was disabling
> powersaving by adding this to my config:
>
> ~ λ cat /etc/modprobe.d/iwlwifi.conf
> options iwlmvm power_scheme=1
> options iwlwifi power_save=0
>
>   Any suggestions on where to take this, and let me know if I can
> provide you with any further information.
>
> Thanks for making open source software <3
>