Well I got hit by the "no connectivity" issue once again after couple days this time, similar to the @ilshatms.
From dmesg:
[543156.909270] br-lan: port 1(lan1) entered disabled state
[543156.922398] mt7530 mdio-bus:00 lan1: Link is Down
[543179.791306] mt7530 mdio-bus:00 lan1: Link is Up - 100Mbps/Full - flow control off
[543179.798928] br-lan: port 1(lan1) entered blocking state
[543179.804235] br-lan: port 1(lan1) entered forwarding state
[543189.158624] br-lan: port 1(lan1) entered disabled state
[543189.164827] mt7530 mdio-bus:00 lan1: Link is Down
[543191.231516] mt7530 mdio-bus:00 lan1: Link is Up - 100Mbps/Full - flow control rx/tx
[543191.239306] br-lan: port 1(lan1) entered blocking state
[543191.244615] br-lan: port 1(lan1) entered forwarding state
From logread:
Mon Mar 7 05:34:16 2022 daemon.debug hostapd: wlan0: STA 08:c5:e1:61:0d:b0 IEEE 802.11: binding station to interface 'wlan0'
Mon Mar 7 05:34:16 2022 daemon.debug hostapd: wlan0: STA 08:c5:e1:61:0d:b0 IEEE 802.11: authentication OK (FT)
Mon Mar 7 05:34:16 2022 daemon.debug hostapd: wlan0: STA 08:c5:e1:61:0d:b0 MLME: MLME-AUTHENTICATE.indication(08:c5:e1:61:0d:b0, FT)
Mon Mar 7 05:34:16 2022 daemon.debug hostapd: wlan0: STA 08:c5:e1:61:0d:b0 IEEE 802.11: association OK (aid 4)
Mon Mar 7 05:34:16 2022 daemon.info hostapd: wlan0: STA 08:c5:e1:61:0d:b0 IEEE 802.11: associated (aid 4)
Mon Mar 7 05:34:16 2022 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 08:c5:e1:61:0d:b0
Mon Mar 7 05:34:16 2022 daemon.debug hostapd: wlan0: STA 08:c5:e1:61:0d:b0 MLME: MLME-REASSOCIATE.indication(08:c5:e1:61:0d:b0)
Mon Mar 7 05:34:16 2022 daemon.debug hostapd: wlan0: STA 08:c5:e1:61:0d:b0 IEEE 802.11: binding station to interface 'wlan0'
Mon Mar 7 05:34:16 2022 daemon.debug hostapd: wlan0: STA 08:c5:e1:61:0d:b0 WPA: event 6 notification
Mon Mar 7 05:34:16 2022 daemon.notice hostapd: wlan1: Prune association for 08:c5:e1:61:0d:b0
Mon Mar 7 05:34:16 2022 daemon.notice hostapd: wlan1: AP-STA-DISCONNECTED 08:c5:e1:61:0d:b0
Mon Mar 7 05:34:16 2022 daemon.debug hostapd: wlan0: STA 08:c5:e1:61:0d:b0 WPA: FT authentication already completed - do not start 4-way handshake
Mon Mar 7 05:34:18 2022 daemon.debug hostapd: wlan1: STA 08:c5:e1:61:0d:b0 MLME: MLME-DISASSOCIATE.indication(08:c5:e1:61:0d:b0, 1)
Mon Mar 7 05:34:18 2022 daemon.debug hostapd: wlan1: STA 08:c5:e1:61:0d:b0 MLME: MLME-DELETEKEYS.request(08:c5:e1:61:0d:b0)
Mon Mar 7 05:34:46 2022 daemon.info hostapd: wlan1: STA 08:c5:e1:61:0d:b0 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mon Mar 7 05:34:46 2022 daemon.debug hostapd: wlan1: STA 08:c5:e1:61:0d:b0 MLME: MLME-DEAUTHENTICATE.indication(08:c5:e1:61:0d:b0, 2)
Mon Mar 7 05:34:46 2022 daemon.debug hostapd: wlan1: STA 08:c5:e1:61:0d:b0 MLME: MLME-DELETEKEYS.request(08:c5:e1:61:0d:b0)
I checked if the phone was still connected with :
iw dev wlan0 station dump
It was still connected (unfortunately I forgot to copy the output).
I tried to perform the
iw dev wlan0 scan trigger freq 2447 flush
as user @sammo stated in https://forum.openwrt.org/t/archer-c7-2-4-ghz-wireless-dies-in-24-48-hours/44163/150?u=nkef
And I got connectivity back without needing to restart wifi or reboot the router , we may need to apply one of the workaround scripts suggested on that forum posts to apply the scan every time an event 60 occurs.
Maybe it is related to the https://forum.openwrt.org/t/archer-c7-2-4-ghz-wireless-dies-in-24-48-hours/44163/223?u=nkef