iOS and iPadOS 18.3.2 issues with AiMesh WiFi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2025 07:05 AM
After updating my iPhone XR and iPad Pro 11' to the latest OS version, I have experienced issues with them in my home AiMesh network. Although the devices are placed near the secondary node, they always connect to the primary. Even when I force them to connect to the secondary node, the router warns me that due to a weak signal, the connection could be dropped. All other devices connect to the secondary node without issue when they are far from the primary.
I have a TUF-AX4200 acting as the primary node in my AiMesh network and a TUF-AX3000 v2 as the secondary, both running the latest available firmware.
Have anybody faced the same issue? Could it be a TUF-AX3000 v2 issue? I've seen that the UF-AX3000 v2 3.0.0.4.388_23856 firmware fixed client binding issues in Mesh scenarios.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2025 07:21 AM
TUF-AX3000 firmware link here, not sure where the _23856 is coming from as highest listed is _22611?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2025 12:16 PM
Hi @jzchen, the _23856 firmware is the latest for the TUF-AX3000 V2. The_22611 one is the latest for TUF-AX3000 no V2.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
I've just found a workaround for this issue. Although everything worked fine before and both devices support WPA2 and WPA3, I changed the WiFi Authentication Method from "WPA2/WPA3-Personal" to "WPA2-Personal" only. Now, the iPhone XR and iPad Pro 11" connect to the nearest AiMesh node and roam seamlessly between them.
I consider this a workaround because WPA2/WPA3-Personal should be supported in this AiMesh configuration, as all nodes are compatible with that authentication method.
Hopefully, the next TUF-AX3000 V2 firmware update will address this issue.
