Hi,
does anybody know what could be causing these CTRL-EVENT-BEACON-LOSS notices in the log?
device is a Xiaomi mini running OpenWrt 19.07.2, r10947-65030d81f3
configured as a client using the 2.4Ghz radio, the wireless link itself should be fine:
Hi, please help I got the same problem. I bridge the TD-W8970 (OpenWrt 19.07.2 r10947-65030d81f3 ) with my primary router. I don’t have any problem with my wifi , but this annoying message flooding the System Log. Anyone knows how I can disable this message? I changed the log_level to 4 but with no luck.
root@TP-LINK:~# iw dev wlan0 station dump
Station ec:f0:fe:a4:06:a0 (on wlan0)
inactive time: 4 ms
rx bytes: 19474500474
rx packets: 26673482
tx bytes: 26463045857
tx packets: 23389683
tx retries: 5161763
tx failed: 2886
beacon loss: 661
beacon rx: 1523424
rx drop misc: 240733
signal: -48 [-58, -55, -52] dBm
signal avg: -48 [-60, -54, -52] dBm
beacon signal avg: -49 dBm
tx bitrate: 240.0 MBit/s MCS 13 40MHz short GI
rx bitrate: 300.0 MBit/s MCS 15 40MHz short GI
rx duration: 0 us
last ack signal:43 dBm
expected throughput: 44.677Mbps
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
DTIM period: 1
beacon interval:100
short preamble: yes
short slot time:yes
connected time: 176581 seconds
I also am experiencing this with my Xiaomi 4A 100M when I made it as a WDS Bridged Repeater. On related logs on my main router which is also using OpenWRT.
It seems that this happens if there are no activity on it after an hour or so, some kind of power saving/sleep mode on the wifi. So right now, i'm testing if having a sudo keepalive using PING will keep this from happening. I'll probably know in few days if the message still appears.
Let us know if someone find the reason. I've upgraded two WDS connections (4 routers total - 740N, 841N) to 19.07.5 and now I see the message in the log of the client (WDS) router. Previous version 18.06.8 and lower were free of this message.
I'm seeing the same thing on a TP-Link TL-WR1043ND v1 WDS client connecting to a TP-Link Archer C7 v2 AP. They're both on OpenWrt 19.07.3. I use this for the TV box and there are short video pauses caused by this until the connection reestablishes, so it's not just from idle connections.
I see rashes of these. They have been there for a long time, can't remember what version they started with been there since router was installed... with probably Barrier Breaker. I've tried to make them go away with wifi tweaks but if anything I've made it worse. Just reflashed to 21.02.3 and issue is still there.
Router is in a tough spot so reception is not great:
Seems issue can be fixed at kernel level (which would help many drivers beyond ath9k) or on the ath9k driver. I'll try test that, as it is less intrusive: https://lore.kernel.org/stable/8043549.T7Z3S40VBb@natalenko.name/
Funny bunch the kernel maintainers (including Linus Torvalds himself in thread above!).
Have an ASUS RT-AC58U as the AP and a TP-Link Archer C7 v5 as the client - following this guide.
CTRL-EVENT-BEACON-LOSS is flooding the Archer C7 v5, ending up loss of connection with the RT-AC58U and needing a reboot at least once a day. Both are on OpenWrt 22.03.0 r19685, and I have tried reversing their roles too - the client invariably loses connectivity with a deluge of this in the log.
Considering these builds are still on 5.10.138, is there any workaround (like disabling powersave) - or can the relevant patches be cherry-picked from 5.15.x?
Update after a little experimenting - turning off 802.11r and KRACK, and setting beacon interval to 2999 in the AP seems to have gotten rid of this.
But the connection between the AP and Client getting dropped once a day - that still occurs, assuming that is not related to the BEACON_LOSS messages in the log...