Was just looking through the system log on my ZenWifi AX tonight, and noticed that it had only been up for 1 day, 10 hours, when it should have been up longer. Looked at what was in the log for that time, and saw this:
I'm not up enough on what's in mesh router system logs to see if this contains a clue as to what happened...This is relatively new firmware, looks like I installed it about Feb. 3, so I'm wondering if I should revert it to the previous firmware? I didn't notice the crash, so the router must have recovered fairly quickly from whatever caused it to crash.
Not sure if this: "90:CD:B6:98:E2:A3 not mesh client, can't update it's ip" has any significance relative to the mesh router crashing or not. It doesn't sound great, since all my clients are mesh clients *smile*. But it is the first significant thing in the crashlog, so it might.
Anyways, any help here about what might be going on? Very happy with the performance of the mesh, but this has me wondering.
It did just occur to me that I didn't reset the routers to factory defaults and reconfigure when I did the last upgrade of firmware which included the upgrade to AiMesh 2.0, maybe I should try that and see if that helps the stability. Just not sure what I'm seeing here.
Code:
Feb 9 14:58:28 roamast: Roam a client [78:7B:8A:3B:C2:53], status [0]
Feb 9 14:58:28 wlceventd: wlceventd_proc_event(507): eth5: Disassoc 78:7B:8A:3B:C2:53, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 9 14:58:28 wlceventd: wlceventd_proc_event(507): eth5: Disassoc 78:7B:8A:3B:C2:53, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 9 15:17:28 wlceventd: wlceventd_proc_event(526): eth5: Auth A8:81:7E:A2:DE:45, status: Successful (0), rssi:0
Feb 9 15:17:28 wlceventd: wlceventd_proc_event(536): eth5: ReAssoc A8:81:7E:A2:DE:45, status: Successful (0), rssi:0
May 4 22:05:13 crashlog: LOG
May 4 22:05:13 crashlog: <4>
May 4 22:05:13 crashlog: <4>90:CD:B6:98:E2:A3 not mesh client, can't update it's ip
May 4 22:05:13 crashlog: <4>
May 4 22:05:13 crashlog: <7>[tdts_shell_ioctl_stat:256] Recv ioctl req with op 2
May 4 22:05:13 crashlog: <6>CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
May 4 22:05:13 crashlog: <6>CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
May 4 22:05:13 crashlog: <7>[tdts_shell_ioctl_stat:256] Recv ioctl req with op 2
May 4 22:05:13 crashlog: <7>[tdts_shell_ioctl_stat:256] Recv ioctl req with op 2
May 4 22:05:13 crashlog: <7>[tdts_shell_ioctl_stat:256] Recv ioctl req with op 2
May 4 22:05:13 crashlog: <4>84:AB:1A:89:E0:98 not mesh client, can't update it's ip
May 4 22:05:13 crashlog: <4>
May 4 22:05:13 crashlog: <4>90:CD:B6:98:E2:A3 not mesh client, can't update it's ip
May 4 22:05:13 kernel: klogd started: BusyBox v1.24.1 (2021-01-18 14:05:07 CST)
I'm not up enough on what's in mesh router system logs to see if this contains a clue as to what happened...This is relatively new firmware, looks like I installed it about Feb. 3, so I'm wondering if I should revert it to the previous firmware? I didn't notice the crash, so the router must have recovered fairly quickly from whatever caused it to crash.
Not sure if this: "90:CD:B6:98:E2:A3 not mesh client, can't update it's ip" has any significance relative to the mesh router crashing or not. It doesn't sound great, since all my clients are mesh clients *smile*. But it is the first significant thing in the crashlog, so it might.
Anyways, any help here about what might be going on? Very happy with the performance of the mesh, but this has me wondering.
It did just occur to me that I didn't reset the routers to factory defaults and reconfigure when I did the last upgrade of firmware which included the upgrade to AiMesh 2.0, maybe I should try that and see if that helps the stability. Just not sure what I'm seeing here.
Last edited: