Unknown device always connecting to 2.4G wifi

Hello Everyone :smile:
I have a Tp-Link Archer C20 V5 running the latest OpenWrt 21.02.1, r16325-88151b8303 .
I opened the luci admin page for configuring something, when I noticed that an unknown device with no hostname (the hostname area showed a ? mark) was connected to my 2.4G wlan. I disconnected it, but it reconnected almost immidiately, no matter how many times I change my wifi password, router password the unknown device always connects to the 2.4G wlan, EVEN hard resetting my router and changing my wifi name and password at the same time didn't help. No matter what I do, this device ALWAYS connects to my wifi. What should I do ? I live alone and have one phone where I use wifi and one computer where I use the lan cable. I use https for accessing luci. I am well familiar with linux/terminal/using openwrt ONLY with CLI.
Any help will be appreciate ! Please aks for more information if needed. Sorry if I posted in the wrong place, I am quite new to this forum :slightly_smiling_face:

Is your phone an Android? If so check if it is using a random MAC address. I've been fooled by this a couple of times.

Please show where you see this device.

My phone running Android 10. I just checked and it is using device mac instead of randomized mac. And also, in the connected stations tab, I can see my android phone with its model number in the host name. Thats where I also see the unknown device. And also one thing to note here is that the signal strength of the unknown device shows around -84dBm, while my android device has a signal strengt of around -50dBm.

Here you go :


The bottom device is my android phone named redlinux.lan
The device I am talking about is the one above it.

This is so weird... there's no way someone could just access your wifi network. This maybe not be related but did this issue occurred in the past versions of openwrt as well?

This is the first version of openwrt I have ever used. I installed openwrt on my router in november when 21.02.01 was already available for my device. I have applied a temporary fix though, I just blocked the mac address of the device from my network.

are you sure the device connects, and not only tries to connect ?
it connecting, even after the password's changed, would indicate it ...

try Hide ESSID, see what happens then ...

So even if the device is trying to connect to my wifi it will show up in the associated stations tab ?
EDIT : the device still shows up even after I hid the essid and rebooted the device.

hiding ESSID doesn't really guarantee anything, it's down to the client
what it tries to connect to.

Post the MAC, if it isn't yours there's no worry :wink:

The thing is, I even changed the ssid name after hiding it, and changed the password after that and the device still shows up !!
Oviously my phone does not connect now since i changed the password. Can it be a bug in the current version of openwrt that I'm using ? Also the mac of that unknown device is: 70:89:76:FB:0A:E6

I found the system log filled with this :

Wed Feb  2 13:30:04 2022 daemon.info hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed Feb  2 13:30:06 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:30:10 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:30:14 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:30:17 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:30:21 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:30:24 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:30:28 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:30:31 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:30:35 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:30:39 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:30:42 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:30:46 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:30:49 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:30:53 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:30:57 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:31:00 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:31:04 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:31:07 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:31:11 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:31:15 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:31:18 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:31:22 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:31:25 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:31:29 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:31:32 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:31:36 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:31:40 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:31:43 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:31:47 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:31:50 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:31:54 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:31:58 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:32:01 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:32:05 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:32:08 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:32:12 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:32:15 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:32:19 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:32:23 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:32:26 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:32:30 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:32:33 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:32:37 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:32:41 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:32:44 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:32:48 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:32:51 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:32:55 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:32:58 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:33:02 2022 daemon.info hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: disconnected due to excessive missing ACKs
Wed Feb  2 13:33:02 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:33:06 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:33:09 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:33:13 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:33:16 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:33:20 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:33:24 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:33:27 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:33:31 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:33:32 2022 daemon.info hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed Feb  2 13:33:34 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:33:38 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:33:41 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:33:45 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:33:49 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:33:52 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:33:56 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:33:59 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:34:03 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:34:07 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:34:10 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:34:14 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:34:17 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:34:21 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:34:25 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:34:28 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:34:32 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:34:35 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:34:39 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:34:42 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:34:46 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:34:50 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:34:53 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:34:57 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:35:00 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:35:04 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:35:08 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:35:11 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:35:15 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:35:18 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:35:22 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:35:25 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:35:29 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:35:33 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:35:36 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:35:40 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:35:43 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:35:47 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:35:51 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:35:54 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:35:58 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:36:01 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:36:05 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:36:08 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:36:12 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:36:16 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:36:19 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:36:23 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:36:26 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:36:30 2022 daemon.info hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: disconnected due to excessive missing ACKs
Wed Feb  2 13:36:30 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:36:34 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:36:37 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:36:41 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:36:44 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:36:48 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:36:51 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:36:55 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:36:59 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:37:00 2022 daemon.info hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed Feb  2 13:37:02 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:37:06 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:37:09 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:37:13 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:37:17 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:37:20 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:37:24 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:37:27 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:37:31 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:37:35 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:37:38 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:37:42 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:37:45 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:37:49 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:37:52 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:37:56 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:38:00 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:38:03 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:38:07 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:38:10 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:38:14 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:38:18 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:38:21 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:38:25 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:38:28 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:38:32 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:38:35 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:38:39 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:38:43 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:38:46 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:38:50 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:38:53 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:38:57 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:39:01 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:39:04 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:39:08 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:39:11 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:39:15 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:39:18 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:39:22 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:39:26 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:39:29 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:39:33 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:39:36 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:39:40 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:39:44 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:39:47 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response
Wed Feb  2 13:39:51 2022 daemon.notice hostapd: wlan0: STA 70:89:76:fb:0a:e6 IEEE 802.11: did not acknowledge authentication response

Doing a OUI lookup on the Wireshark site shows the MAC is registered to:

#### Results
70:89:76 Tuya Smart Inc.

Does that name rings any bell?

EDIT: Maybe is a smart appliance trying to connect to any available network, but how is it attempting to connect on a hidden and different ESSID?

1 Like

Nope. What even is that ? Some sort of smart home device, I have none in my house.

well, i don't think it connects.

Tuya works with IoT devices https://www.tuya.com/

Well after searching around with what I found in the logs, I think it is called a bad actor mac address ? Meaning that a Random device like an alarm clock or security camera, due to bad software or hardware defects, is CONSTANTLY trying to connect to EVERY wifi that is available in range. In that case, I will just block that mac address in my wireless settings.

1 Like

This post got me curious... Indeed here's an exact example of this situation that I found on Reddit... A Tuya alarm clock, which hasn't been setup on the owner's network causing this behaviour.

2 Likes

Yep, that was one of the results I got back from searching.