In my remote system, (see sig) I have a GT-AX6000 Main, two RT-AX86U Pro Nodes and an RT-AX86U Node, all Merlin FW (although I am not convinced that has any bearing on it).
When I reboot the Aimesh System (AiMesh Tab), all Nodes come up, all show WIRED Backhaul, but in my Wireless Report (Addon Script) and also in the built-in System Log, Wireless Log, I ALSO see a WIRELESS (Wifi) connection to at least one Mesh Node, generally only on the one device (although I have seen it on the other nodes occasionally**). i.e. DUAL Simultaneous Backhaul Modes (and not this is not some early form of MLO... this is a Wifi 6 System).
It is like (on AiMesh system restart or single-node restart or just main restart) it establishes the Wifi BH, then establishes the WIRED BH, but does not release the WIRELESS BH, just keeps BOTH.
If I deauthorize the Wifi connection with:
where the MAC is that of the Node, then that "wifi-connected node" correctly (IMO) disappears from both the Wireless Report and ALSO from the built-in System Log, Wireless Log.
The WIRED connection remains 'up' without any downtime, all IoTs are happy and everything works.
** I have seen this sometimes if I do a separate Node reboot either via SSH or the WebGUI.
I can of course engineer a script to watch for this and deauthorize the Wifi connection (as above) when it sees (i) the unwanted Wifi connection has been established AND (ii) that the Wired connection is fine. I am cognisant of the desired behaviour for "backup" Wireless connectivity to be pushed to the node if the Wired connection is lost (as a replacement, not in parallel), but that is not the scenario happening here.
Just wondering if anyone else has seen a similar issue or behaviour?
Also wondering if the 3004 Codebase RT-AX58U (on which it happens most) is more susceptible than the 3006 Codebase RT-AX86U Pro nodes; thoughts?
When I reboot the Aimesh System (AiMesh Tab), all Nodes come up, all show WIRED Backhaul, but in my Wireless Report (Addon Script) and also in the built-in System Log, Wireless Log, I ALSO see a WIRELESS (Wifi) connection to at least one Mesh Node, generally only on the one device (although I have seen it on the other nodes occasionally**). i.e. DUAL Simultaneous Backhaul Modes (and not this is not some early form of MLO... this is a Wifi 6 System).
It is like (on AiMesh system restart or single-node restart or just main restart) it establishes the Wifi BH, then establishes the WIRED BH, but does not release the WIRELESS BH, just keeps BOTH.
If I deauthorize the Wifi connection with:
where the MAC is that of the Node, then that "wifi-connected node" correctly (IMO) disappears from both the Wireless Report and ALSO from the built-in System Log, Wireless Log.
The WIRED connection remains 'up' without any downtime, all IoTs are happy and everything works.
** I have seen this sometimes if I do a separate Node reboot either via SSH or the WebGUI.
I can of course engineer a script to watch for this and deauthorize the Wifi connection (as above) when it sees (i) the unwanted Wifi connection has been established AND (ii) that the Wired connection is fine. I am cognisant of the desired behaviour for "backup" Wireless connectivity to be pushed to the node if the Wired connection is lost (as a replacement, not in parallel), but that is not the scenario happening here.
Just wondering if anyone else has seen a similar issue or behaviour?
Also wondering if the 3004 Codebase RT-AX58U (on which it happens most) is more susceptible than the 3006 Codebase RT-AX86U Pro nodes; thoughts?
Last edited:
