[XT8] [CFG80211-ERROR] Error reoccurs near 9pm - Possible cause?

stebrick

Occasional Visitor
Currently running 386.5_2-gnuton0 on Zenwifi XT8. No other stuff have been installed yet (amtm etc).

This error could happen randomly but I notice a pattern that it so far happened a lot near 9pm of my local time (not exactly, sometimes little earlier), causing a brief network disconnection for like 2-3 mins. The blue led of the node in my room was flashing blue when this happened and soon it turned back to white and normal again.

From the logs below it seems quite a lot happened within that 2 mins duration, but I've no idea what happened at all. It would be great if someone could explain what was happening, and how to solve this problem. Detailed logs file is also attached.


Code:
May 30 21:00:30 kernel: CFG80211-ERROR) wl_event_handler : No wdev corresponding to bssidx: 0x0 found! Ignoring event.
May 30 21:00:30 wlceventd: wlceventd_proc_event(486): wds2.0.1: Disassoc 04:42:1A:14:6E:B8, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 30 21:00:30 wlceventd: wlceventd_proc_event(486): eth6: Disassoc 04:42:1A:14:6E:B8, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 30 21:00:30 kernel: br0: port 8(wds2.0.1) entered disabled state
May 30 21:00:30 hostapd: eth6: STA 04:42:1a:14:6e:b8 IEEE 802.11: disassociated
May 30 21:00:30 kernel: br3: port 8(wds2.0.1.502) entered disabled state
May 30 21:00:30 kernel: br3: topology change detected, propagating
May 30 21:00:30 kernel: br2: port 8(wds2.0.1.501) entered disabled state
May 30 21:00:30 kernel: device wds2.0.1 left promiscuous mode
May 30 21:00:30 kernel: br0: port 8(wds2.0.1) entered disabled state
May 30 21:00:30 kernel: device wds2.0.1.501 left promiscuous mode
May 30 21:00:30 kernel: br2: port 8(wds2.0.1.501) entered disabled state
May 30 21:00:30 kernel: device wds2.0.1.502 left promiscuous mode
May 30 21:00:30 kernel: br3: port 8(wds2.0.1.502) entered disabled state
May 30 21:00:32 kernel: br2: port 9(wds0.0.1.501) received tcn bpdu
May 30 21:00:32 kernel: br2: topology change detected, propagating
May 30 21:00:32 wlceventd: wlceventd_proc_event(486): wds0.0.1: Disassoc 04:42:1A:14:6E:B1, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 30 21:00:32 wlceventd: wlceventd_proc_event(486): eth4: Disassoc 04:42:1A:14:6E:B1, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
May 30 21:00:32 kernel: CFG80211-ERROR) wl_notify_connect_status : Invalid ndev status 4
May 30 21:00:32 kernel: wl0: set timeout 5 secs to wait dev reg finish
May 30 21:00:32 hostapd: eth4: STA 04:42:1a:14:6e:b1 IEEE 802.11: disassociated
May 30 21:00:32 kernel: Flushing net_device wds0.0.1.
May 30 21:00:32 kernel: br0: port 9(wds0.0.1) entered disabled state
May 30 21:00:32 kernel: br3: port 9(wds0.0.1.502) entered disabled state
May 30 21:00:32 kernel: br3: topology change detected, propagating
May 30 21:00:32 kernel: br2: port 9(wds0.0.1.501) entered disabled state
May 30 21:00:32 kernel: device wds0.0.1 left promiscuous mode
May 30 21:00:32 kernel: br0: port 9(wds0.0.1) entered disabled state
May 30 21:00:32 kernel: device wds0.0.1.501 left promiscuous mode
May 30 21:00:32 kernel: br2: port 9(wds0.0.1.501) entered disabled state
May 30 21:00:32 kernel: device wds0.0.1.502 left promiscuous mode
May 30 21:00:32 kernel: br3: port 9(wds0.0.1.502) entered disabled state
May 30 21:00:35 wlceventd: wlceventd_proc_event(515): eth6: ReAssoc 92:DD:FA:5E:67:1A, status: Successful (0)
May 30 21:00:35 hostapd: eth6: STA 92:dd:fa:5e:67:1a IEEE 802.11: associated
 

Attachments

  • router_error_no_redact.txt
    15.5 KB · Views: 23
Last edited:

ColinTaylor

Part of the Furniture
Please don't redact the MAC addresses, it makes trying to debug the problem much more difficult.

My first guess is that this could be an issue with the node rather than the router. How is the node connected to the router, by Ethernet?
 

stebrick

Occasional Visitor
Please don't redact the MAC addresses, it makes trying to debug the problem much more difficult.

My first guess is that this could be an issue with the node rather than the router. How is the node connected to the router, by Ethernet?

Sorry, didn't know it would be a problem redacting those addresses. I edited accordingly so that they're not redacted anymore. Attached file also re-uploaded. No, the node is connected via wireless backhaul.
 

ColinTaylor

Part of the Furniture
Thanks for the update. Can you post the syslog from the node please.
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top