Devices kicked from wifi

Hello,
I have a question, I suddenly have the issue that some devices got kicked from one of the accesspoints I have no way to access the netwerk again untill the accesspoint is reset.
I run openwer 23.05 RC1, but I have had this issue before so I don't think it's because of the RC1. it's one of the reasons I installed RC1, to hope the issue was resolved.

from my log I get this

Wed Jun 21 21:02:41 2023 daemon.info hostapd: phy0-ap0: STA ca:e9:2b:3a:ed:14 IEEE 802.11: associated (aid 1)
Wed Jun 21 21:02:41 2023 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED ca:e9:2b:3a:ed:14
Wed Jun 21 21:02:42 2023 daemon.info hostapd: phy0-ap0: STA ca:e9:2b:3a:ed:14 IEEE 802.11: disconnected due to excessive missing ACKs
Wed Jun 21 21:02:42 2023 daemon.info hostapd: phy0-ap0: STA ca:e9:2b:3a:ed:14 IEEE 802.11: disassociated
Wed Jun 21 21:02:43 2023 daemon.info hostapd: phy0-ap0: STA ca:e9:2b:3a:ed:14 IEEE 802.11: authenticated
Wed Jun 21 21:02:43 2023 daemon.info hostapd: phy0-ap0: STA ca:e9:2b:3a:ed:14 IEEE 802.11: associated (aid 1)
Wed Jun 21 21:02:43 2023 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED ca:e9:2b:3a:ed:14 auth_alg=open
Wed Jun 21 21:02:43 2023 daemon.info hostapd: phy0-ap0: STA ca:e9:2b:3a:ed:14 WPA: pairwise key handshake completed (RSN)
Wed Jun 21 21:02:43 2023 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED ca:e9:2b:3a:ed:14
Wed Jun 21 21:05:40 2023 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED cc:d4:2e:e6:fc:24
Wed Jun 21 21:05:40 2023 daemon.notice hostapd: phy0-ap0: STA-OPMODE-N_SS-CHANGED cc:d4:2e:e6:fc:24 1
Wed Jun 21 21:05:40 2023 daemon.info hostapd: phy0-ap0: STA cc:d4:2e:e6:fc:24 IEEE 802.11: authenticated
Wed Jun 21 21:05:40 2023 daemon.notice hostapd: phy0-ap0: STA-OPMODE-N_SS-CHANGED cc:d4:2e:e6:fc:24 2
Wed Jun 21 21:05:40 2023 daemon.info hostapd: phy0-ap0: STA cc:d4:2e:e6:fc:24 IEEE 802.11: associated (aid 2)
Wed Jun 21 21:05:40 2023 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED cc:d4:2e:e6:fc:24 auth_alg=open
Wed Jun 21 21:05:40 2023 daemon.info hostapd: phy0-ap0: STA cc:d4:2e:e6:fc:24 WPA: pairwise key handshake completed (RSN)
Wed Jun 21 21:05:40 2023 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED cc:d4:2e:e6:fc:24
Wed Jun 21 21:07:02 2023 daemon.notice hostapd: Unsupported authentication algorithm (3)
Wed Jun 21 21:08:52 2023 daemon.notice hostapd: Unsupported authentication algorithm (3)
Wed Jun 21 21:08:52 2023 daemon.notice hostapd: Unsupported authentication algorithm (3)
Wed Jun 21 21:08:54 2023 daemon.info hostapd: phy0-ap0: STA ca:e9:2b:3a:ed:14 IEEE 802.11: authenticated
Wed Jun 21 21:08:55 2023 daemon.info hostapd: phy0-ap0: STA ca:e9:2b:3a:ed:14 IEEE 802.11: authenticated
Wed Jun 21 21:08:56 2023 daemon.info hostapd: phy0-ap0: STA ca:e9:2b:3a:ed:14 IEEE 802.11: associated (aid 1)
Wed Jun 21 21:08:56 2023 daemon.info hostapd: phy0-ap0: STA ca:e9:2b:3a:ed:14 WPA: pairwise key handshake completed (RSN)
Wed Jun 21 21:08:56 2023 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED ca:e9:2b:3a:ed:14
Wed Jun 21 21:09:21 2023 daemon.notice hostapd: Unsupported authentication algorithm (3)
Wed Jun 21 21:09:21 2023 daemon.notice hostapd: Unsupported authentication algorithm (3)
Wed Jun 21 21:09:26 2023 daemon.notice hostapd: Unsupported authentication algorithm (3)
Wed Jun 21 21:09:26 2023 daemon.notice hostapd: Unsupported authentication algorithm (3)
Wed Jun 21 21:17:48 2023 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED cc:d4:2e:e6:fc:24
Wed Jun 21 21:17:48 2023 daemon.notice hostapd: phy0-ap0: STA-OPMODE-N_SS-CHANGED cc:d4:2e:e6:fc:24 1
Wed Jun 21 21:17:48 2023 daemon.info hostapd: phy0-ap0: STA cc:d4:2e:e6:fc:24 IEEE 802.11: authenticated
Wed Jun 21 21:17:48 2023 daemon.notice hostapd: phy0-ap0: STA-OPMODE-N_SS-CHANGED cc:d4:2e:e6:fc:24 2
Wed Jun 21 21:17:48 2023 daemon.info hostapd: phy0-ap0: STA cc:d4:2e:e6:fc:24 IEEE 802.11: associated (aid 2)
Wed Jun 21 21:17:48 2023 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED cc:d4:2e:e6:fc:24 auth_alg=open
Wed Jun 21 21:17:48 2023 daemon.info hostapd: phy0-ap0: STA cc:d4:2e:e6:fc:24 WPA: pairwise key handshake completed (RSN)
Wed Jun 21 21:17:48 2023 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED cc:d4:2e:e6:fc:24
Wed Jun 21 21:18:52 2023 daemon.err uhttpd[1528]: [info] luci: accepted login on / for root from 192.168.180.149
Wed Jun 21 21:18:55 2023 daemon.notice hostapd: phy0-ap0: AP-STA-DISCONNECTED ca:e9:2b:3a:ed:14
Wed Jun 21 21:18:55 2023 daemon.info hostapd: phy0-ap0: STA ca:e9:2b:3a:ed:14 IEEE 802.11: disassociated
Wed Jun 21 21:18:56 2023 daemon.info hostapd: phy0-ap0: STA ca:e9:2b:3a:ed:14 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)

ca:e9:2b:3a:ed:14 iphone
cc:d4:2e:e6:fc:24 lgtv

and those were the 2 devices which couldn't connect to the network anymore.

Is there anything usefull in the log which shows why those 2 devices were kicked?

on the uncooperative radio, try one at a time or combinations of the following advanced Wifi interface settings:

  • uncheck „Disassociate On Low Acknowledgement“
  • check „Disable Inactivity Polling“
  • Station inactivity limit: try a higher value
  • DTIM Interval, try: 1 or 3 instead of the default 2
2 Likes

@Pico has good suggestions.

Also...

If it is running on 2.4 then this is somewhat typical. This guide highlights some of the issues.

Long story short is iptv tends to conflict with other devices on 2.4. The guide recommends using 5GHz or a wired connection if possible.

I would add that you may benefit from giving the iptv it's own SSID or even re-purpose an old router for it exclusively.

Band aid solution might be to try using luci-app-watchcat and see if that will reset it when it malfunctions in the meantime.

RouterOS has DTIM fixed at 1. OWRT default is 2 and that worked ok for me (150+aps).
setting it to 3 had some strange behaviour while switching/roaming.

thank you all for the great suggestions.

I'll start with
"uncheck „Disassociate On Low Acknowledgement" for some reason I needed to do that for 2.4 as well,
so it might be needed for 5gz too.
I'm however nog sure it this will affect my roaming, but we will see.

phy0-xxx is my 5ghz network, I extra checked after your comment, so it's already 5Ghz which should be.

I will try then when the other options won't work, it is a good solution, but more like a workaround. I don't like to restart stuff if not needed.

just an update

  • uncheck „Disassociate On Low Acknowledgement“ didn't work

I will try

  • check „Disable Inactivity Polling“

now.

I noticed something else,

Most of the time when the issue occurs, it's the same access point and the tv is using some streaming service.

Could it be that the AP just gets to hot, starts throttling and ditches connections?
Especially during the we weather we have now in the area where I live.

I don't know if it's possible to see the device/cpu temp somewhere.

I did 2 things,
I swapped to accesspoints
and I installed 23.5 RC2.
and now for over a week I haven't had any connection issues.
So either the issue has been fixed or it's hardware.

thank you for helping