Xiaomi Router Mini 2.4Ghz Wifi randomly cannot connect

Installing and Using OpenWrt
1

Hello everyone,

I have a Xiaomi Router Mini working as a separate network. Recently I changed the original firmware to openwrt-23.05. Which work ok except the Wifi 2.4GHz interface.

At random times clients cannot connect to the interface and the log floods with these error messages

on Nov 13 12:50:38 2023 daemon.info hostapd: phy1-ap0: STA 6a:f7:18:08:5a:49 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mon Nov 13 13:12:12 2023 daemon.notice hostapd: phy1-ap0: STA d2:6b:26:f0:72:6a IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 13:12:17 2023 daemon.notice hostapd: phy1-ap0: STA d2:6b:26:f0:72:6a IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 13:22:24 2023 daemon.notice hostapd: phy1-ap0: STA d2:6b:26:f0:72:6a IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 13:22:28 2023 daemon.notice hostapd: phy1-ap0: STA d2:6b:26:f0:72:6a IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 13:28:54 2023 daemon.notice hostapd: phy1-ap0: STA d2:6b:26:f0:72:6a IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 13:28:58 2023 daemon.notice hostapd: phy1-ap0: STA d2:6b:26:f0:72:6a IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:12:10 2023 daemon.info hostapd: phy1-ap0: STA d2:6b:26:f0:72:6a IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mon Nov 13 14:33:08 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:33:09 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:33:10 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:33:11 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:33:12 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:33:13 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:33:14 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:33:15 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:33:16 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:33:17 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:33:18 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:33:19 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:35:24 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:35:25 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:35:26 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:35:27 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:35:28 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:35:29 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:35:30 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:35:31 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:35:41 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:35:42 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:35:43 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:35:44 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:35:46 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:35:47 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:35:48 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:35:49 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:36:45 2023 daemon.info hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: disconnected due to excessive missing ACKs
Mon Nov 13 14:36:52 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:36:53 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:36:53 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:36:55 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:37:15 2023 daemon.info hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mon Nov 13 14:37:56 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:37:57 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:37:59 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:38:00 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:39:34 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:39:35 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:39:36 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:39:37 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:39:38 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:39:39 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:39:40 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:39:41 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:39:54 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:39:55 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:39:56 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:39:57 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:40:10 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:40:10 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:40:11 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:40:13 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:40:14 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:40:15 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:40:16 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:40:17 2023 daemon.info hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: disconnected due to excessive missing ACKs
Mon Nov 13 14:40:17 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:40:30 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:40:31 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:40:32 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:40:33 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:40:47 2023 daemon.info hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mon Nov 13 14:41:11 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:41:13 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:41:13 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:41:15 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:41:17 2023 daemon.notice hostapd: phy1-ap0: STA d2:6b:26:f0:72:6a IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:41:21 2023 daemon.notice hostapd: phy1-ap0: STA d2:6b:26:f0:72:6a IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:41:21 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:41:22 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:41:23 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:41:24 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:41:31 2023 daemon.notice hostapd: phy1-ap0: STA d2:6b:26:f0:72:6a IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:41:40 2023 daemon.notice hostapd: phy1-ap0: STA d2:6b:26:f0:72:6a IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:42:00 2023 daemon.notice hostapd: phy1-ap0: STA d2:6b:26:f0:72:6a IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:42:04 2023 daemon.notice hostapd: phy1-ap0: STA d2:6b:26:f0:72:6a IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:42:25 2023 daemon.info hostapd: phy0-ap0: STA 46:f9:b3:cc:f6:61 IEEE 802.11: associated (aid 5)
Mon Nov 13 14:42:25 2023 daemon.notice hostapd: phy0-ap0: AP-STA-CONNECTED 46:f9:b3:cc:f6:61 auth_alg=sae
Mon Nov 13 14:42:25 2023 daemon.info hostapd: phy0-ap0: STA 46:f9:b3:cc:f6:61 WPA: pairwise key handshake completed (RSN)
Mon Nov 13 14:42:25 2023 daemon.notice hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED 46:f9:b3:cc:f6:61
Mon Nov 13 14:42:25 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:42:26 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:42:27 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:42:28 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 46:f9:b3:cc:f6:61
Mon Nov 13 14:42:28 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.31.243 46:f9:b3:cc:f6:61
Mon Nov 13 14:42:28 2023 daemon.info dnsmasq-dhcp[1]: DHCPDISCOVER(br-lan) 46:f9:b3:cc:f6:61
Mon Nov 13 14:42:28 2023 daemon.info dnsmasq-dhcp[1]: DHCPOFFER(br-lan) 192.168.31.243 46:f9:b3:cc:f6:61
Mon Nov 13 14:42:28 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.31.243 46:f9:b3:cc:f6:61
Mon Nov 13 14:42:28 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.31.243 46:f9:b3:cc:f6:61 Xiaomi-11T
Mon Nov 13 14:42:28 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:42:57 2023 daemon.err uhttpd[1472]: [info] luci: accepted login on / for root from 192.168.31.149
Mon Nov 13 14:43:30 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:43:31 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:43:32 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:43:33 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:44:34 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:44:35 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:44:36 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:44:37 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:45:39 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:45:39 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:45:40 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response
Mon Nov 13 14:45:42 2023 daemon.notice hostapd: phy1-ap0: STA f4:b7:e2:a5:e3:b1 IEEE 802.11: did not acknowledge authentication response

If I restart the Wifi interface (or the router), everything goes back to normal until the next time it's going to happen.

I searched google and forums but I've seems this problem reported for other models and each time a different solution is suggested. I tried most of them (like set manually the transmit power to max) but without luck, up until now.

Any ideas? Suggestions?

2

I would like to know as well as I facing exactly the same on Xiaomi Mi Router 4A Gigabit Edition. I noticed this happening when I upgraded from 22.03.5 to 23.05.2. Then I saw full log of what you posted and lots of my devices had problems with connecting.

I tried to uncheck "Disassociate On Low Acknowledgement" but it did not really help.

I went back to 22.03.6 and everything works fine again.

1 Like
3

Same router here, same version of openwrt (Currently running: 23.05.2 - r23630-842932a63d) same issue.

Will try 22.03.6, thanks for the info.

4

You folks have any Bluetooth devices close to the router?

5

No Bluetooth devices (router is outside the house) and not even another router nearby. Closest neighbor router is probably 400m afar.

6

option dtim_period '3'
option wpa_group_rekey '86400'
option disassoc_low_ack '0'

These might help.

2 Likes
7

Still happening on 22.03.6. Once this happens, all the 2.4 devices stay disconnected, and only 5G keep connected.

Tue Feb 13 17:41:36 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:41:38 2024 daemon.notice hostapd: wlan0: STA a0:92:08:37:2b:ce IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:41:39 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:41:41 2024 daemon.notice hostapd: wlan0: STA a0:92:08:37:2b:ce IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:41:44 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:41:45 2024 daemon.notice hostapd: wlan0: STA a0:92:08:37:2b:ce IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:41:47 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:41:48 2024 daemon.notice hostapd: wlan0: STA a0:92:08:37:2b:ce IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:41:50 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:41:53 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:41:56 2024 daemon.notice hostapd: wlan0: STA 08:05:81:e3:69:1b IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:41:56 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:41:56 2024 daemon.notice hostapd: wlan0: STA 08:05:81:e3:69:1b IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:41:58 2024 daemon.notice hostapd: wlan0: STA a0:92:08:37:2b:ce IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:41:58 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:01 2024 daemon.notice hostapd: wlan0: STA a0:92:08:37:2b:ce IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:01 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:04 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:04 2024 daemon.notice hostapd: wlan0: STA a0:92:08:37:2b:ce IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:07 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:08 2024 daemon.notice hostapd: wlan0: STA a0:92:08:37:2b:ce IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:10 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:11 2024 daemon.notice hostapd: wlan0: STA a0:92:08:37:2b:ce IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:13 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:16 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:19 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:20 2024 daemon.notice hostapd: wlan0: STA 08:05:81:e3:69:1b IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:20 2024 daemon.notice hostapd: wlan0: STA 08:05:81:e3:69:1b IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:21 2024 daemon.notice hostapd: wlan0: STA a0:92:08:37:2b:ce IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:22 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:25 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:28 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:31 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:32 2024 daemon.notice hostapd: wlan0: STA a0:92:08:37:2b:ce IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:34 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:35 2024 daemon.notice hostapd: wlan0: STA a0:92:08:37:2b:ce IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:37 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:39 2024 daemon.notice hostapd: wlan0: STA a0:92:08:37:2b:ce IEEE 802.11: did not acknowledge authentication response
Tue Feb 13 17:42:40 2024 daemon.notice hostapd: wlan0: STA d8:f1:5b:04:0f:be IEEE 802.11: did not acknowledge authentication response
8

I'm trying this starting now.

9

So far this solved the issue. Still on 22.03.6, I guess I'll keep this version for a while. Thank you!

10

Thanks! That solved the problem of my wife's laptop not being able to connect.

When trying to find out what this actually does, in the wiki, I found that wpa_group_rekey is only for WPA Enterprise, which I'm not using. (option encryption 'psk2'). So the option dtim_period does the trick on it's own?

11

Many (Apple) devices are picky about DTIM interval, 3 is the recommended one for them.

Time interval for rekeying GTK (broadcast/multicast encryption keys) in
seconds. (dot11RSNAConfigGroupRekeyTime)
This defaults to 86400 seconds (once per day) when using CCMP/GCMP as the
group cipher and 600 seconds (once per 10 minutes) when using TKIP as the
group cipher. #wpa_group_rekey=86400

https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf

I've got no idea why OpenWrt sets 600 as default for both of them.

1 Like