Hi,
Thought I would try and layout the issues I have noticed since upgrading and the behaviours in a way that may help or be similar to other people.
I had a RT-AX88U as my main router in an Aimesh, the other 2 nodes were a RT-AX53U and RT-AX55.
There were a few small managed Netgear switches between the router (AX88U) and the nodes.
All was fine with the mesh but I got fed up with the ax88u Lan ports locking up every few days so I decided to get a new router.
I bought a Asus TUF AX6000.
Setup the new router, it connected fine to my broadband.
Went to setup my first Aimesh node. Thought I would use the AX88u as my first node.
The setup went OK, the first attempt on resetting the AX88u failed so did it again and it added. It was near my router and was using WiFi.
I then plugged an ethernet cable in from my switch to the WAN port of the AX88U. The router seen this and said it was using ethernet as the backhaul with Great connectivity.
I unplugged it and moved it to the room where I wanted it situated, plugged the WAN port into the switch and waited.
It didn't show up as connected in the router Aimesh page.
I has this a bit when I first setup the Aimesh years ago so unplugged the WAN port to see if it could see any of the WiFi from the router.
After a few minutes it did and showed up as connected in the Aimesh page on the UI on the router, so I plugged in the WAN port and went back and checked the router UI and it said connectivity Great connected via ethernet.
I went to a spot where I knew my phone would only see the Aimesh node (AX88U) and it wouldn't connect. My phone a pixel 6 pro would connect, see there was no internet and disconnect again.
Hmmmm.
I thought fine. I'll try the RT-AX55 as an Aimesh node.
I powered off the AX88U, repeated the same process with the AX55. Every step was the same.
End result the same. Node was in the router UI as great connection, Ethernet, but anything connected to the node wouldn't get any internet access.
I thought I'll try the AX-53U expecting the same result.
Same process, same buggy behaviour about it needing to connect via WiFi after it rebooted before the ethernet would work.
This time though it worked. Clients would get internet when connecting to the AX-53U mesh node.
I'm a bit meh in my opinions about the Aimesh. The only advantage is the fact wifi 5 devices don't re-associate when handing off between APs.
I'm in 2 minds whether to just setup the Aimesh nodes as standalone APs, however the LAN port issues on the AX88u have put me off that idea for it with the LAN ports locking up.
I am guessing this will be firmware related and no point sending back the TUF AX6000 for a replacement one.
Not sure if anyone else has a similar issue with the TUF AX6000 or if anyone has them working fine as Aimesh routers with a variety of nodes?
Edit!!! Now working, turned out to be a Netgear switch power brick. Aimesh all working fine.
Thought I would try and layout the issues I have noticed since upgrading and the behaviours in a way that may help or be similar to other people.
I had a RT-AX88U as my main router in an Aimesh, the other 2 nodes were a RT-AX53U and RT-AX55.
There were a few small managed Netgear switches between the router (AX88U) and the nodes.
All was fine with the mesh but I got fed up with the ax88u Lan ports locking up every few days so I decided to get a new router.
I bought a Asus TUF AX6000.
Setup the new router, it connected fine to my broadband.
Went to setup my first Aimesh node. Thought I would use the AX88u as my first node.
The setup went OK, the first attempt on resetting the AX88u failed so did it again and it added. It was near my router and was using WiFi.
I then plugged an ethernet cable in from my switch to the WAN port of the AX88U. The router seen this and said it was using ethernet as the backhaul with Great connectivity.
I unplugged it and moved it to the room where I wanted it situated, plugged the WAN port into the switch and waited.
It didn't show up as connected in the router Aimesh page.
I has this a bit when I first setup the Aimesh years ago so unplugged the WAN port to see if it could see any of the WiFi from the router.
After a few minutes it did and showed up as connected in the Aimesh page on the UI on the router, so I plugged in the WAN port and went back and checked the router UI and it said connectivity Great connected via ethernet.
I went to a spot where I knew my phone would only see the Aimesh node (AX88U) and it wouldn't connect. My phone a pixel 6 pro would connect, see there was no internet and disconnect again.
Hmmmm.
I thought fine. I'll try the RT-AX55 as an Aimesh node.
I powered off the AX88U, repeated the same process with the AX55. Every step was the same.
End result the same. Node was in the router UI as great connection, Ethernet, but anything connected to the node wouldn't get any internet access.
I thought I'll try the AX-53U expecting the same result.
Same process, same buggy behaviour about it needing to connect via WiFi after it rebooted before the ethernet would work.
This time though it worked. Clients would get internet when connecting to the AX-53U mesh node.
I'm a bit meh in my opinions about the Aimesh. The only advantage is the fact wifi 5 devices don't re-associate when handing off between APs.
I'm in 2 minds whether to just setup the Aimesh nodes as standalone APs, however the LAN port issues on the AX88u have put me off that idea for it with the LAN ports locking up.
I am guessing this will be firmware related and no point sending back the TUF AX6000 for a replacement one.
Not sure if anyone else has a similar issue with the TUF AX6000 or if anyone has them working fine as Aimesh routers with a variety of nodes?
Edit!!! Now working, turned out to be a Netgear switch power brick. Aimesh all working fine.
Last edited: