Thanks everyone for the suggestions.
Just to clarify about "a lot of devices leaving/joining the network": I have up to 30 wireless devices at one time, but they come and go, so there are about 50-60 DHCP clients after a day (mix of iOS/Android/Windows). My existing settings are fine for a few devices, but the issues pop out when having many devices, so any suggestion please take that into account. Please also mention the number of wireless devices in your tests if possible.
I'll erase nvram and reconfigure everything from scratch, and refrain from trying funny things this time, hopefully the issue is due to the remnants of my bad settings. _________________ ▫ RSS feed for DD-WRT releases (2024): https://rsseverything.com/feed/7d36ab68-7733-46c3-bd8a-9c54c5cef08c.xml
▫ easyddup - A simple upgrade/downgrade utilityby yoyoma2--- as featured in 📌 Reference Links, stickies retired back to forum (Moderator's Pick 🌟)
[*]iPhone 13 frequently disconnects from WiFi "EEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)" <--- I disable "Disassoc Low Ack" and 802.11r (FT) and no more issue.
But the "Disassoc Low Ack" message is a different one ...
IEEE 802.11: disconnected due to excessive missing ACKs
[*]iPhone 13 frequently disconnects from WiFi "EEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)" <--- I disable "Disassoc Low Ack" and 802.11r (FT) and no more issue.
But the "Disassoc Low Ack" message is a different one ...
IEEE 802.11: disconnected due to excessive missing ACKs
Update:
one Dell laptop bc:17:b8:xx:xx:ff (Intel Wi-Fi 6 AX201) still encounters random WiFi disconnections.
I suspect there's a correlation between these few log lines:
Code:
kern.warn kernel: [191453.250791] ath10k_warn: 238 callbacks suppressed
kern.warn kernel: [191453.250800] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 165 tid 0
...
daemon.info hostapd: wlan0: STA bc:17:b8:xx:xx:ff MLME: auth request, signal -66 (Accepted)
Well, if the problems always occur when clients move out of range.
Then you can play with these two settings "disassoc_low_ack" and "Minimum Signal for connection".
So that it disconnects the clients in time before they somehow negatively influence the network performance.
otherwise try another older build.
The Atheros drivers and firmware are constantly being developed and bugs creep in from time to time.
Well, if the problems always occur when clients move out of range.
Then you can play with these two settings "disassoc_low_ack" and "Minimum Signal for connection".
So that it disconnects the clients in time before they somehow negatively influence the network performance.
otherwise try another older build.
The Atheros drivers and firmware are constantly being developed and bugs creep in from time to time.
The Zoom meeting is still on-going, so I can't apply any setting or reboot the router.
My concerns:
- Will it make any difference if the router actively drops the WiFi connection instead of waiting for the wireless client to move out of range?
- Why am I the only one having this problem? (maybe the OP "e-" also has the same problem) What's the procedure to trigger this problem?
I can revert to as many older builds as I want when there's no one using the WiFi, but without understanding the trigger conditions, how to know if the issue is gone or not?
EDIT: "Minimum signal for connection" only may not be enough, there are also "Poll Time for signal lookup" "Amount of allowed low signals".