AX product Wi-Fi connection limits

[CaptainSTX]

No, the configuration of the RT-AC66U is exactly the same WPA2 and AES password as I was using on the RT-AX88U.

But it probably isn't both AES-TKIP. Some older devices want/require the TKIP piece which some current routers such as my AX88Pro running Merlin doesn't provide. The newer routers that seem to still provide AES-TKIP are ISP provided routers.

 

[vit5421]

But it probably isn't both AES-TKIP. Some older devices want/require the TKIP piece which some current routers such as my AX88Pro running Merlin doesn't provide. The newer routers that seem to still provide AES-TKIP are ISP provided routers.

Did you try wpa/wpa2 personal in order to select tkip+AES encryption?

 

[CaptainSTX]

Did you try wpa/wpa2 personal in order to select tkip+AES encryption?

Yes, but when you make this choice then hit apply it reverts to AES only. To confirm that it is only AES you can use a Wi-Fi scanner app and it will show that SSID is in fact AES only. During the alpha and beta releases I reported this behavior to Merlin and suggested if not possible or desirable to actually enable TKIP that he remove the option from the pull down list.

 

[sfx2000]

Most consumer router/AP's are going to hit a hard limit on the number of clients per radio...

General rule of thumb here is 32 clients per radio, and something used for network planning.

 

[IanSav]

In my case, as I mentioned before, every device is capable of connecting to the network. The issues appear to relate to the number of devices connecting.

I am now working with ASUS to try and identify the issue.

 

[IanSav]

ASUS have stopped responding to this issue. They requested many changes to my settings to simplify the Wi-Fi complexity but nothing helped.

If anyone has more suggestions they would be welcomed.

 

[Tech9]

Your network's capabilities have to correspond to the number of client devices you plan to have. With 90-100 devices already - see post #14 and plan your next network upgrade accordingly. Just adding more Wi-Fi in form of consumer mesh pods, nodes, satellites with limited client support per radio and all sharing the same channels won't help.

 

[Ronald Schwerer]

@IanSav any updates or solutions to this issue? I've got a similar issue. About 60+ clients total, with 50 IoT on AIMesh IOT. I've even had times where I couldn't connect to the mesh SSID using my phone, even though I could easily connect to the main SSID (same channel) immediately. I was trying to troubleshoot some dropped wireless cameras near the fringes of my property. The cameras (all TP-Link Tapo) had been working flawlessly until a long power outage last week. However I did just recently add a Tapo 4K camera that uses 5GHz band and a Tapo H500 Smart HomeBase to offload some of the video data bandwidth using a separate sub-G band (proprietary AFAIK). The camera can switch to the sub G band when the primary SSID is having problems.

I've tried utilizing my old RT-AC68U's as AiMesh nodes, but I know that isn't going to be a good permanent solution. I'm about to reconfigure a couple as APs.

As an interim solution I've been moving many of the Iot stuff to the 2.4 base SSID. They have been working much better.

Anyway, you left us hanging back in July. I'm sure your problem isn't unique.

 

[Tech9]

You may want to describe your system better, @Ronald Schwerer. About 60 clients on <something> AiMesh with few old routers as "nodes" doesn't say enough even for suggestions. Your old routers have just basic AiMesh compatibility in 2025.