RT-AX56 drops daily from GT-AX11000 router (using Ai-Mesh)

[randye007]

Hi All,

I have a very strange issue.
Here is my setup using Ai-Mesh:

• GT-AX11000: Ai-Mesh Router running 3.0.0.4_388_22525
• RT-AX56: Ai-Mesh Node running 3.0.0.4.386_42860
• RT-AX56: Ai-Mesh Node running 3.0.0.4.386_42860

As you can see I have configured 2 ASUS extenders to be Ai-Mesh nodes. Both are using the 5GHz WiFi first in the Backhaul Connection priority.

On a daily basis, one of my Ai-Mesh nodes disconnects from the AiMesh Router for 10-30 mins then reconnects.
Here are the logs from my GT-AX11000 Ai-Mesh Router when the disconnect happens:

Mar  2 00:39:20 kernel: wfd_unregisterdevice Successfully unregistered ifidx 2 wfd_idx 0
Mar  2 00:39:20 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:0
Mar  2 00:39:20 wlceventd: wlceventd_proc_event(511): eth6: Disassoc XX:XX:XX:XX:XX:XX, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar  2 00:39:21 wlceventd: wlceventd_proc_event(559): eth6: Assoc XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-45
Mar  2 00:39:21 kernel: wfd_registerdevice Successfully registered dev wds0.0.2 ifidx 2 wfd_idx 0
Mar  2 00:39:21 kernel: Register interface [wds0.0.2]  MAC: AA:AA:AA:AA:AA:AA
Mar  2 00:41:34 wlceventd: wlceventd_proc_event(530): eth6: Auth BB:BB:BB:BB:BB:BB, status: Successful (0), rssi:0
Mar  2 00:41:34 wlceventd: wlceventd_proc_event(559): eth6: Assoc BB:BB:BB:BB:BB:BB, status: Successful (0), rssi:-66
Mar  2 00:41:39 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind BB:BB:BB:BB:BB:BB, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-70
Mar  2 00:41:40 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind BB:BB:BB:BB:BB:BB, status: 0, reason: Previous authentication no longer valid (2), rssi:-71
Mar  2 00:47:35 wlceventd: wlceventd_proc_event(530): eth6: Auth CC:CC:CC:CC:CC:CC, status: Successful (0), rssi:0
Mar  2 00:47:35 wlceventd: wlceventd_proc_event(559): eth6: Assoc CC:CC:CC:CC:CC:CC, status: Successful (0), rssi:-63
Mar  2 00:48:04 wlceventd: wlceventd_proc_event(530): eth6: Auth DD:DD:DD:DD:DD:DD, status: Successful (0), rssi:0
Mar  2 00:48:04 wlceventd: wlceventd_proc_event(559): eth6: Assoc DD:DD:DD:DD:DD:DD, status: Successful (0), rssi:-67
Mar  2 00:48:23 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind CC:CC:CC:CC:CC:CC, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-61
Mar  2 00:48:23 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind CC:CC:CC:CC:CC:CC, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-61
Mar  2 00:48:24 wlceventd: wlceventd_proc_event(511): eth6: Disassoc CC:CC:CC:CC:CC:CC, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar  2 00:49:05 wlceventd: wlceventd_proc_event(511): eth6: Disassoc DD:DD:DD:DD:DD:DD, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar  2 00:49:05 wlceventd: wlceventd_proc_event(511): eth6: Disassoc DD:DD:DD:DD:DD:DD, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar  2 00:54:03 wlceventd: wlceventd_proc_event(530): eth6: Auth CC:CC:CC:CC:CC:CC, status: Successful (0), rssi:0
Mar  2 00:54:04 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind CC:CC:CC:CC:CC:CC, status: 0, reason: Unspecified reason (1), rssi:0
Mar  2 00:54:04 wlceventd: wlceventd_proc_event(530): eth6: Auth CC:CC:CC:CC:CC:CC, status: Successful (0), rssi:0
Mar  2 00:54:04 wlceventd: wlceventd_proc_event(559): eth6: Assoc CC:CC:CC:CC:CC:CC, status: Successful (0), rssi:-63
Mar  2 00:54:34 wlceventd: wlceventd_proc_event(530): eth6: Auth DD:DD:DD:DD:DD:DD, status: Successful (0), rssi:0
Mar  2 00:54:34 wlceventd: wlceventd_proc_event(559): eth6: Assoc DD:DD:DD:DD:DD:DD, status: Successful (0), rssi:-66
Mar  2 00:54:40 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind DD:DD:DD:DD:DD:DD, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-68
Mar  2 00:54:40 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind DD:DD:DD:DD:DD:DD, status: 0, reason: Previous authentication no longer valid (2), rssi:-68
Mar  2 00:54:43 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind CC:CC:CC:CC:CC:CC, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-62
Mar  2 00:54:43 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind CC:CC:CC:CC:CC:CC, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-62
Mar  2 00:54:44 wlceventd: wlceventd_proc_event(511): eth6: Disassoc CC:CC:CC:CC:CC:CC, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0

XX:XX:XX:XX:XX:XX = MAC (BSSID on 2.4GHz band) of my RT-AX56 Ai-Mesh Node that keeps dropping.
AA:AA:AA:AA:AA:AA = MAC (BSSID on Ethernet) on my GT-AX11000 Ai-Mesh Router.
CC:CC:CC:CC:CC:CC = MAC address of a confirmed IoT device on my LAN
DD: DD: DD: DD: DD: DD - MAC address of a confirmed IoT device on my LAN

Troubleshooting:

1. Swapped the 2 RT-AX56 Ai-Mesh nodes in each location. The problem now appears on the swapped Ai-Mesh node! So the issue does not appear to follow the device ...

Been looking at this issue for the past 2 months with no luck.

Any help would be greatly appreciated!

Thanks,
Randy

 

[c23chaos]

Any update to this? What was the fix?

 

[ramishka]

Hi, I had a similar issue but with an AX88U and a AX58U. When you have these different model combinations on AiMesh, it's best to have them both on the same firmware version.
I updated mine as below:
AX88U: 3.0.0.4.388_22525
AX58U: 3.0.0.4.388_22525
The issues seem to have resolved more or less now, but still I dont feel like the network is as robust as with the older firmware.