Client-mode: CTRL-EVENT-BEACON-LOSS

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:

      Mode: Client  Channel: 3 (2.422 GHz)
      Tx-Power: 20 dBm  Link Quality: 57/70
      Signal: -53 dBm  Noise: unknown
      Bit Rate: 43.3 MBit/s
      Encryption: WPA2 PSK (CCMP)
      Type: nl80211  HW Mode(s): 802.11bgn
      Hardware: [MediaTek MT7620]

(logs on the access point, also running openwrt, show nothing out of the ordinary).

burst of these can last anywhere from a couple of seconds to 5 minutes.

any help would be much appreciated.

> Thu Apr  9 20:47:40 2020 daemon.notice wpa_supplicant[22034]: wlan1: CTRL-EVENT-BEACON-LOSS
> Thu Apr  9 20:47:45 2020 daemon.notice wpa_supplicant[22034]: wlan1: CTRL-EVENT-BEACON-LOSS
> Thu Apr  9 20:47:49 2020 daemon.notice wpa_supplicant[22034]: wlan1: CTRL-EVENT-BEACON-LOSS
> Thu Apr  9 20:47:53 2020 daemon.notice wpa_supplicant[22034]: wlan1: CTRL-EVENT-BEACON-LOSS
> Thu Apr  9 20:47:56 2020 daemon.notice wpa_supplicant[22034]: wlan1: CTRL-EVENT-BEACON-LOSS
> Thu Apr  9 20:47:58 2020 daemon.notice wpa_supplicant[22034]: wlan1: CTRL-EVENT-BEACON-LOSS
> Thu Apr  9 20:47:59 2020 daemon.notice wpa_supplicant[22034]: wlan1: CTRL-EVENT-BEACON-LOSS
> Thu Apr  9 20:48:01 2020 daemon.notice wpa_supplicant[22034]: wlan1: CTRL-EVENT-BEACON-LOSS
> Thu Apr  9 20:48:02 2020 daemon.notice wpa_supplicant[22034]: wlan1: CTRL-EVENT-BEACON-LOSS
> Thu Apr  9 20:48:03 2020 daemon.notice wpa_supplicant[22034]: wlan1: CTRL-EVENT-BEACON-LOSS
> Thu Apr  9 20:48:05 2020 daemon.notice wpa_supplicant[22034]: wlan1: CTRL-EVENT-BEACON-LOSS
> Thu Apr  9 20:48:08 2020 daemon.notice wpa_supplicant[22034]: wlan1: CTRL-EVENT-BEACON-LOSS
> Thu Apr  9 20:48:09 2020 daemon.notice wpa_supplicant[22034]: wlan1: CTRL-EVENT-BEACON-LOSS
> Thu Apr  9 20:48:10 2020 daemon.notice wpa_supplicant[22034]: wlan1: CTRL-EVENT-BEACON-LOSS
> Thu Apr  9 20:48:16 2020 daemon.notice wpa_supplicant[22034]: wlan1: CTRL-EVENT-BEACON-LOSS
> Thu Apr  9 20:48:18 2020 daemon.notice wpa_supplicant[22034]: wlan1: CTRL-EVENT-BEACON-LOSS

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

Please also post together the logs that come immediately before CTRL-EVENT-BEACON-LOSS

Hello guys,

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.

I've added the following in the scheduled task:

0 */1 * * * ping -c 1 dns.google

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.

Found this bug which seems related:

It may be a powersaving issue that causes missed beacons.