Why is this happening and how can I stop this message from flooding my log? My neighbors device is a tablet and this issue keeps popping up even after a restart. I have changed no settings recently and everything has been running fine but this is very annoying.
Wed Dec 24 11:34:41 2025 daemon.notice hostapd: wlan1: STA 94:bd:be:b1:16:41 IEEE 802.11: did not acknowledge authentication response
Wed Dec 24 11:35:01 2025 daemon.notice hostapd: wlan1: STA 94:bd:be:b1:16:41 IEEE 802.11: did not acknowledge authentication response
Wed Dec 24 11:35:21 2025 daemon.notice hostapd: wlan1: STA 94:bd:be:b1:16:41 IEEE 802.11: did not acknowledge authentication response
Wed Dec 24 11:35:41 2025 daemon.info hostapd: wlan1: STA 94:bd:be:b1:16:41 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed Dec 24 11:35:41 2025 daemon.notice hostapd: wlan1: STA 94:bd:be:b1:16:41 IEEE 802.11: did not acknowledge authentication response
Wed Dec 24 11:36:01 2025 daemon.notice hostapd: wlan1: STA 94:bd:be:b1:16:41 IEEE 802.11: did not acknowledge authentication response
Wed Dec 24 11:36:21 2025 daemon.notice hostapd: wlan1: STA 94:bd:be:b1:16:41 IEEE 802.11: did not acknowledge authentication response
Wed Dec 24 11:36:41 2025 daemon.notice hostapd: wlan1: STA 94:bd:be:b1:16:41 IEEE 802.11: did not acknowledge authentication response
Wed Dec 24 11:37:01 2025 daemon.notice hostapd: wlan1: STA 94:bd:be:b1:16:41 IEEE 802.11: did not acknowledge authentication response
Wed Dec 24 11:37:21 2025 daemon.notice hostapd: wlan1: STA 94:bd:be:b1:16:41 IEEE 802.11: did not acknowledge authentication response
Wed Dec 24 11:37:41 2025 daemon.notice hostapd: wlan1: STA 94:bd:be:b1:16:41 IEEE 802.11: did not acknowledge authentication response
Wed Dec 24 11:38:01 2025 daemon.notice hostapd: wlan1: STA 94:bd:be:b1:16:41 IEEE 802.11: did not acknowledge authentication response
Please help.
Edit: Solved. New log message from the Kernel I need assistance with though, more details in the post below.
Find the client with MAC 94:bd:be:b1:16:41. OUI = "Hon Hai Precision Ind. Co.,Ltd." (better known as Foxcon). Maybe weak signal, wrong password, driver problems?
Figured it out. My TV went rogue and decided to for whatever reason cause this. Resetting the network settings on the TV and reconnecting to the proper wifi fixed the issue.
However, on another note I noticed in my Kernel Log that I am getting repeated Syn Flood warnings, this being the exact message repeated.
It should be blocked if unsolicitated traffic, did you do anything particular to the firewall?, its not open due to a misconfiguration?, you can test some port probe test sites.
It can happen its still a incoming traffic due to a other device in your network, which is fine.
Most of the times I see this is with a tunnel connection with a mismatch on mtu maybe a certain device uses it, but it can also be a form of Ddos but a very classic one, I won't worry to much if it is only a single ip and not constantly.
However the device doing this is more of my interest.
I took the france ip through abuseipdb its malicious, so now you need to check if a device actually does a src packet to this ip aswell, if that is the case you may have some botnet connectivity going on.
tcpdump -i br-lan dst 75.163.41.244 likely its just a bot trying a port scan/vulnerability scan which is normal, the wan side is always constantly under attack by malicious bots who seek open ports, getting the message however is tickling me off thinking it might first originated from your lan as source and that would be a bad thing because a line has been created where it no longer is unsolicitated traffic.
The message is not from banip (just to be sure?), then its nothing to worry about if from banip, I was purely speaking about OpenWrt synflooding protection in the firewall.