XT8's unable to connect to each other
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
I was using the RT-AX86U previously and the XT8's as aimesh nodes, as soon as i upgraded to the BE7200 the XT8's refuse to connect to each other wirelessly and will only connect to the BE7200. I set up aimesh with the AX86U again to test and it worked flawlessly. I think Asus needs to pass this along to the firmware team and fix this issue with the BE7200.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
Hi @deepakjulka69 ,
Regarding your issue, could you please confirm if the AiMesh node has been upgraded to the latest firmware that supports AiMesh? We recommend resetting the AiMesh node to its default settings first. Please refer to the FAQ below for detailed steps.
[AiMesh] How to setup AiMesh system (Web GUI)? | Official Support | ASUS Global
Additionally, please perform a hard reset on the BE7200 and then reconfigure it.
We greatly appreciate your understanding and cooperation.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Yes, it's running the latest firmware and I've factory reset it many times. The bedroom node is much closer to the 3rd floor node but the 3rd floor node won't connect to it. This worked just fine on my AX86u. I'm certain the BE7200 firmware is the issue and the firmware team needs to fix it. Please pass this along to them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
have you forwarded this issue to the firmware team? It seems I'm not the only one dealing with this issue as @JonathanE stated he's experiencing it as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello, anything new regarding this issue? It is a problem that should be addressed as it suggests something wrong with optimization between APs in the mesh-network.
