Reply To: ASUS ZenWiFi AX Whole Home Tri-Band Mesh WiFi 6 System Not sure if this is the right place to ask…. I am thinking of upgrading my Google Mesh wifi to the above. Has anyone used this and does it…

[Jonathan Morris]

I realise it’s been a bit quiet of late, but my wife has been working from home more recently due to us contracting Covid and isolating.

She hasn’t really told me much about any issues she’s had before, but did pipe up that she’s getting kicked off Team calls every day she’s had them since last week (not weekend) – sometimes 2 or 3 times.

Thing is, she has calls throughout the day but she said it always happens around 1600 lor after and now it has happened again, so this leaves me wondering what could be causing an issue at a specific time of day? I’ll need to investigate further, like how long her calls are and how long from starting to dropping etc etc.

Due to the issue of sometimes having the mesh lock on at 2.4GHz, it is set to reboot at 0400 every day. So, this means the issue happens around 12 hours later. Could this be a factor? A fault related to uptime? I might change it so it reboots later, and see if that causes the issues to happen later (bit of a longshot, but sometimes this is the only way to find the smoking gun).

I’m looking through the log and can see reference to a radar detection at 1549 (but nothing else thereafter), so I’m going to keep an eye out on what it does tomorrow. That could also be related, although it happens over 10 minutes before anything else as per the log:

 

Dec 7 15:49:54 amas_adtbw: [ADTBW]Radar detected, wait for radar timeout
Dec 7 16:01:48 wlceventd: wlceventd_proc_event(508): eth5: Disassoc D2:1C:C6:A9:1B:CB, status: 0, reason: Unspecified reason (1), rssi:0
Dec 7 16:01:48 wlceventd: wlceventd_proc_event(508): eth5: Disassoc D2:1C:C6:A9:1B:CB, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 7 16:01:50 wlceventd: wlceventd_proc_event(556): eth5: Assoc D2:1C:C6:A9:1B:CB, status: Successful (0), rssi:-66
Dec 7 16:03:02 wlceventd: wlceventd_proc_event(508): eth5: Disassoc 92:01:0F:02:A4:FB, status: 0, reason: Unspecified reason (1), rssi:0
Dec 7 16:03:02 wlceventd: wlceventd_proc_event(508): eth5: Disassoc 92:01:0F:02:A4:FB, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 7 16:03:04 wlceventd: wlceventd_proc_event(556): eth5: Assoc 92:01:0F:02:A4:FB, status: Successful (0), rssi:-66
Dec 7 16:03:14 wlceventd: wlceventd_proc_event(508): eth5: Disassoc 50:8E:49:46:B0:A4, status: 0, reason: Unspecified reason (1), rssi:0
Dec 7 16:03:14 wlceventd: wlceventd_proc_event(508): eth5: Disassoc 50:8E:49:46:B0:A4, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 7 16:03:16 wlceventd: wlceventd_proc_event(556): eth5: Assoc 50:8E:49:46:B0:A4, status: Successful (0), rssi:-63
Dec 7 16:03:59 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:F4 rcpi 44
Dec 7 16:03:59 roamast: after rssi -88
Dec 7 16:03:59 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:84 rcpi 98
Dec 7 16:03:59 roamast: after rssi -61
Dec 7 16:04:04 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:F4 rcpi 44
Dec 7 16:04:04 roamast: after rssi -88
Dec 7 16:04:04 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:84 rcpi 98
Dec 7 16:04:04 roamast: after rssi -61
Dec 7 16:04:14 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:F4 rcpi 44
Dec 7 16:04:14 roamast: after rssi -88
Dec 7 16:04:14 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:84 rcpi 98
Dec 7 16:04:14 roamast: after rssi -61
Dec 7 16:04:24 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:F4 rcpi 44
Dec 7 16:04:24 roamast: after rssi -88
Dec 7 16:04:24 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:84 rcpi 98
Dec 7 16:04:24 roamast: after rssi -61
Dec 7 16:04:44 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:F4 rcpi 46
Dec 7 16:04:44 roamast: after rssi -87
Dec 7 16:04:44 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:84 rcpi 98
Dec 7 16:04:44 roamast: after rssi -61
Dec 7 16:04:49 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:F4 rcpi 46
Dec 7 16:04:49 roamast: after rssi -87
Dec 7 16:04:49 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:84 rcpi 98
Dec 7 16:04:49 roamast: after rssi -61
Dec 7 16:04:54 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:F4 rcpi 46
Dec 7 16:04:54 roamast: after rssi -87
Dec 7 16:04:54 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:84 rcpi 98
Dec 7 16:04:54 roamast: after rssi -61
Dec 7 16:05:04 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:F4 rcpi 44
Dec 7 16:05:04 roamast: after rssi -88
Dec 7 16:05:04 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:84 rcpi 98
Dec 7 16:05:04 roamast: after rssi -61
Dec 7 16:05:14 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:F4 rcpi 46
Dec 7 16:05:14 roamast: after rssi -87
Dec 7 16:05:14 roamast: sta 50:8E:49:46:B0:A4 ap F0:2F:74:8D:C3:84 rcpi 100
Dec 7 16:05:14 roamast: after rssi -60
Dec 7 16:11:34 wlceventd: wlceventd_proc_event(508): wds2.0.1: Disassoc F0:2F:74:8D:C3:F8, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec 7 16:11:34 kernel: Virtual device br0 asks to queue packet!
Dec 7 16:11:34 kernel: Virtual device br0 asks to queue packet!

Share the knowledge

You need to login in order to vote