Wifi Mode issue

[SwoopdySwoop]

I’m currently running a network consisting of three GT-AX6000 units and one RT-AX88U. After encountering frequent system-wide crashes, I performed a full factory reset on all nodes and upgraded to Asuswrt-Merlin firmware version 3006.102.5. Since the update, overall network stability has improved significantly, and the random crash issues are resolved.

However, I’ve run into a persistent problem with client roaming and node association. All wireless clients remain connected to the primary GT-AX6000, regardless of signal strength or proximity to other nodes. The secondary GT-AX6000 units and the RT-AX88U appear to be functioning normally in the AiMesh network, but clients do not transition between them as expected.

I’ve verified:

• AiMesh is properly synchronized across all nodes.
• Signal strength thresholds and roaming assistant settings are set to defaults.
• Band steering and Smart Connect are enabled.
• All nodes are on the same firmware version and SSID.

Despite these configurations, clients remain anchored to the main router.

Could you please advise on any advanced configuration tweaks or known firmware-level issues that could affect roaming behavior on 3006.102.5?

 

[ComputerSteve]

I’m currently running a network consisting of three GT-AX6000 units and one RT-AX88U. After encountering frequent system-wide crashes, I performed a full factory reset on all nodes and upgraded to Asuswrt-Merlin firmware version 3006.102.5. Since the update, overall network stability has improved significantly, and the random crash issues are resolved.

However, I’ve run into a persistent problem with client roaming and node association. All wireless clients remain connected to the primary GT-AX6000, regardless of signal strength or proximity to other nodes. The secondary GT-AX6000 units and the RT-AX88U appear to be functioning normally in the AiMesh network, but clients do not transition between them as expected.

I’ve verified:

• AiMesh is properly synchronized across all nodes.
• Signal strength thresholds and roaming assistant settings are set to defaults.
• Band steering and Smart Connect are enabled.
• All nodes are on the same firmware version and SSID.

Despite these configurations, clients remain anchored to the main router.

Could you please advise on any advanced configuration tweaks or known firmware-level issues that could affect roaming behavior on 3006.102.5?

I have had the same problems and all this community says is get rid of the nodes - you have too many ! Point is the roaming stinks ! I don't think there is a fix !

 

[SwoopdySwoop]

Hey there,

With all due respect, I don’t believe there’s any real issue with having multiple nodes in a mesh setup. My home has concrete walls throughout, which is exactly why I invested in ASUS routers — specifically for their AiMesh capabilities. It’s one of the main reasons I chose this brand in the first place.

Also, from what I understand, you can actually fine-tune the degradation points for each node, so that explanation doesn’t really seem to fit the situation. When I was running the OEM firmware, everything worked exactly as intended — the nodes would hand off seamlessly from one to another, and the overall node handoff worked great.

However, since switching to the latest third-party firmware (Asuswrt-Merlin), I’ve started to notice these issues showing up. It’s starting to look more and more like the problem might be related to the firmware itself rather than the hardware setup.

I’d really appreciate it if anyone familiar with this could help point me in the right direction. Maybe there’s a setting or tweak I’m overlooking that could stabilize things again. Any suggestions or insights would be greatly appreciated!

 

[bbunge]

Flash the nodes with Asus firmware. Remove them from the mesh, they should factory reset, then add them back into the mesh. There is no advantage to using Merlin firmware on AiMesh nodes.
Avoid using DFS channels. Also best to set the 2.4 GHz to 20 MHz and the 5 GHz to 80 MHz especially if you live in an area subject to RADAR hits.