AIMesh: 5 GHz network is not available on a node.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2025 12:31 AM
I have AIMesh system at home:
RT-BE88U as a master ( 3.0.0.6.102_37103 firmware - the latest at the moment)
RT-AX88U as a node ( 3.0.0.4.388_2422 firmware1 - the latest at the moment)
Connected with 1Gbit network cable.
Both running 2.4 and 5 GHz networks.
Wireless network settings are on their defaults.
A node regularly becomes unavailable over 5 GHz. I.e. all clients can connect only over 2.4 even though 5GHz network is seemingly available. The clients connected to the master router can connect without issues.
I know that there is a ton of complains like this, the issue seems to be very common.
What I tried to do:
Setting control channel to fixed 36 or 40 value as advised sometimes: doesn't help.
Rebooting the node (or all routers) - it helps, clients can connect to 5 GHz... For another several hours, and then the issue is back.
Note, that RT-AX88U serving as a node worked as my main router before and there it never lost 5 GHz network. So I don't think it is a hardware issue.
Any ideas how to solve? Tx.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-16-2025 06:22 PM
Hi @Sundow ,
Thank you for your feedback.
To better assist you with the 5GHz network unavailability issue on the AiMesh node, we would like you to confirm the following:
- Node reset: We recommend that you reset the RT-AX88U node to factory settings and re-add it to the AiMesh system. [Wireless Router] When Standard Reset Isn’t Working: Hard Factory Reset - Models list | Official Sup...
- Consistent channel names: Please ensure that the 2.4GHz and 5GHz band names on the main router and node are exactly the same.
- Network cable quality: Ensure that the network cable you are using supports 1Gbps and is in good condition. If possible, try replacing it with a high-quality Cat6 or Cat7 cable.
- Role reversal: You can try setting the current node as the main router and the original main router as a node to see if the issue persists.
- Firmware update impact: Please confirm if this issue started occurring after a firmware update.
Thank you.
