What's new

AP v AiMesh?

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

BeachGuy

Senior Member
I have GT-AX6000 as main router and RT-AX58U as node (connected via MoCA ethernet). I had it setup in AiMesh. I checked with ChatGPT and asked best optimization configuration and it suggested to put the RT-AX58U in "AP" mode. I did that and it seems to be better. What is the difference between AiMesh and AP mode if any? Thanks
 
Check with ChatGPT.
It gave me a list of reasons such as less overhead communicating the AiMesh stuff but I was wondering from the "experts" on here and if anybody has an opinion on it. Why would ASUS even have that functionality if AP mode is better?
 
I have GT-AX6000 as main router and RT-AX58U as node (connected via MoCA ethernet). I had it setup in AiMesh. I checked with ChatGPT and asked best optimization configuration and it suggested to put the RT-AX58U in "AP" mode. I did that and it seems to be better. What is the difference between AiMesh and AP mode if any? Thanks
Im sure this has been asked before multiple times....Check out this thread:

 
Last edited:
Im sure this has been asked before multiple times....Check our this thread:


Sorry, I did search but this one didn't come up. Thanks
 
Sorry, I did search but this one didn't come up. Thanks
Here's another:

 
I read it. About 1/2 say AiMesh is better because it uses the same SSID. But when I put node in AP mode I did the same SSID and things are fine.

Still am confused as to why people say AiMesh is better. AP seems better. I have ethernet backhaul via MoCA. Wondering if I should switch back to AiMesh? Any suggestions?
 
I read it. About 1/2 say AiMesh is better because it uses the same SSID. But when I put node in AP mode I did the same SSID and things are fine.
Its a personal choice...I tried both. It's easier to setup Aimesh in my opinion so I ended using my smaller router this way vs AP mode. You can see all your nodes thru the GUI.
 
Is it correct that there is more overhead in Aimesh with the routers communicating than in AP mode? That seems like a benefit to AP mode right there. Here is the rest of what ChatGPT said...

You said:
setting the node as AP as opposed to mesh node is better? Why?
ChatGPT said:
ChatGPT
Using an Access Point (AP) configuration instead of a mesh node setup can be beneficial in certain situations, especially in a wired backhaul setup like yours with MoCA. Here’s a breakdown of why an AP configuration might offer advantages over a mesh configuration for your setup:

1. Reduced Network Complexity
Single Router Handling All Network Management: When the node is set as an AP, the main GT-AX6000 router handles all network management tasks, such as DHCP, NAT, firewall, and routing. This reduces complexity and eliminates potential issues from having two devices share network management tasks.
Simplicity with Wired Backhaul: Since you have a MoCA wired backhaul, the AP setup makes full use of this reliable, high-speed connection without needing the overhead of mesh node coordination. The AP setup essentially lets the main router control both devices as part of one seamless network.
2. Improved Performance and Stability
Dedicated Backhaul Performance: In a mesh setup, the routers communicate constantly to manage the mesh, even with a wired backhaul. AP mode reduces this inter-router communication, freeing up processing power for actual data transfer to clients.
Fewer Firmware Synchronization Issues: Mesh nodes typically need firmware and feature synchronization, which sometimes causes issues (e.g., misconfigurations or settings not being applied consistently). As an AP, the RT-AX58U focuses purely on handling client connections, improving stability.
Less Latency and Overhead: AP mode reduces network latency by minimizing the coordination overhead seen in a mesh, especially beneficial for latency-sensitive applications like gaming or video conferencing.
3. Full Control Over WiFi Settings
Consistent WiFi Settings: In AP mode, the RT-AX58U acts as a “dumb” access point, allowing the GT-AX6000 to control SSIDs, band steering, security settings, and QoS rules for the entire network. This ensures a unified experience and makes network-wide adjustments simpler to manage.
Custom WiFi Configuration: AP mode allows you to fine-tune settings (such as channel selection, transmit power, and band preferences) independently if needed, which can improve performance in environments with interference or dense device networks.
4. Seamless Roaming with Fewer Complications
Roaming Between AP and Router: With AP mode, devices roam between the GT-AX6000 and RT-AX58U based on signal strength and band availability alone. Since they’re on the same network with consistent settings, devices should switch more fluidly, reducing the chance of “sticky” connections or slow handoffs.
No Node-Specific Configurations: In a mesh network, certain configurations, like band steering or roaming thresholds, need to be adjusted at each node. AP mode simplifies this by managing everything centrally through the main router, making roaming more straightforward and consistent.
When a Mesh Node Setup Might Still Be Better
A mesh node setup can be beneficial in cases where:

Wireless Backhaul Is Needed: If a wired backhaul wasn’t available, mesh nodes could help extend the WiFi range while preserving bandwidth on each router.
Dynamic Roaming Controls Are Required: Mesh setups with AI mesh technology provide some advanced roaming features and AI-based optimizations, but these benefits are generally seen only with wireless backhaul or in very large, multi-floor homes with a high device count.
In your setup, where a strong, stable MoCA Ethernet backhaul is available, an AP configuration generally provides a simpler, faster, and more reliable network than a mesh configuration. It leverages the wired backhaul effectively while eliminating the mesh’s added complexity and potential for network conflicts.
 
Is it correct that there is more overhead in Aimesh with the routers communicating than in AP mode? That seems like a benefit to AP mode right there. Here is the rest of what ChatGPT said...

You said:
setting the node as AP as opposed to mesh node is better? Why?
ChatGPT said:
ChatGPT
Using an Access Point (AP) configuration instead of a mesh node setup can be beneficial in certain situations, especially in a wired backhaul setup like yours with MoCA. Here’s a breakdown of why an AP configuration might offer advantages over a mesh configuration for your setup:

1. Reduced Network Complexity
Single Router Handling All Network Management: When the node is set as an AP, the main GT-AX6000 router handles all network management tasks, such as DHCP, NAT, firewall, and routing. This reduces complexity and eliminates potential issues from having two devices share network management tasks.
Simplicity with Wired Backhaul: Since you have a MoCA wired backhaul, the AP setup makes full use of this reliable, high-speed connection without needing the overhead of mesh node coordination. The AP setup essentially lets the main router control both devices as part of one seamless network.
2. Improved Performance and Stability
Dedicated Backhaul Performance: In a mesh setup, the routers communicate constantly to manage the mesh, even with a wired backhaul. AP mode reduces this inter-router communication, freeing up processing power for actual data transfer to clients.
Fewer Firmware Synchronization Issues: Mesh nodes typically need firmware and feature synchronization, which sometimes causes issues (e.g., misconfigurations or settings not being applied consistently). As an AP, the RT-AX58U focuses purely on handling client connections, improving stability.
Less Latency and Overhead: AP mode reduces network latency by minimizing the coordination overhead seen in a mesh, especially beneficial for latency-sensitive applications like gaming or video conferencing.
3. Full Control Over WiFi Settings
Consistent WiFi Settings: In AP mode, the RT-AX58U acts as a “dumb” access point, allowing the GT-AX6000 to control SSIDs, band steering, security settings, and QoS rules for the entire network. This ensures a unified experience and makes network-wide adjustments simpler to manage.
Custom WiFi Configuration: AP mode allows you to fine-tune settings (such as channel selection, transmit power, and band preferences) independently if needed, which can improve performance in environments with interference or dense device networks.
4. Seamless Roaming with Fewer Complications
Roaming Between AP and Router: With AP mode, devices roam between the GT-AX6000 and RT-AX58U based on signal strength and band availability alone. Since they’re on the same network with consistent settings, devices should switch more fluidly, reducing the chance of “sticky” connections or slow handoffs.
No Node-Specific Configurations: In a mesh network, certain configurations, like band steering or roaming thresholds, need to be adjusted at each node. AP mode simplifies this by managing everything centrally through the main router, making roaming more straightforward and consistent.
When a Mesh Node Setup Might Still Be Better
A mesh node setup can be beneficial in cases where:

Wireless Backhaul Is Needed: If a wired backhaul wasn’t available, mesh nodes could help extend the WiFi range while preserving bandwidth on each router.
Dynamic Roaming Controls Are Required: Mesh setups with AI mesh technology provide some advanced roaming features and AI-based optimizations, but these benefits are generally seen only with wireless backhaul or in very large, multi-floor homes with a high device count.
In your setup, where a strong, stable MoCA Ethernet backhaul is available, an AP configuration generally provides a simpler, faster, and more reliable network than a mesh configuration. It leverages the wired backhaul effectively while eliminating the mesh’s added complexity and potential for network conflicts.
Its probably true...but i used my 2nd router in both setups and didn't notice any difference.
 
Its probably true...but i used my 2nd router in both setups and didn't notice any difference.

Ok thanks. Just trying to figure out which setup I should use and if there's an objective reason why. It seems Chat says there's less overhead with AP.
 
I've been running the node in AP mode for a couple of hours and it seems slightly better connectivity (bars) and throughput (tx/rx). Maybe that's the giveup of Aimesh constant communication? System seems a little more stable too.

Also I used to have to force link clients to specific node because they didn't always seem to connect to the best one under Aimesh. Using AP mode they are connecting to best AP.
 
AiMesh is supposed to, (contrary to someone on this thread who deems it doesn't work,) allow you to roam/hop between router and node or node to node without loss of work, similar to cell phones moving along a freeway/road hopping from tower to tower. You'll need to understand how this is accomplished to see where drawbacks can occur:

Mesh accomplishes this with same SSID and password as you noted, but also needs two other conditions, same channel AND bandwidth. So if your router is higher spec than your node your router will be capped by the capability of the node. (It is not advisable to have two vastly different specification router and node in each frequency range, 2.4, 5 GHz, and 6 GHz. AiMesh also establishes self healing properties IF not set to Ethernet Backhaul Mode. This separates a hidden SSID_dwb along with its bandwitdh, to immediately take up the connection say if ethernet cable is unplugged/cut.

Access Point mode doesn't allow you to hop between nodes (router and nodes) without disconnecting and connecting again. An access point CAN be run at it's full potential as with the router, but a connection would likely need to be reeastabilished when jumping among them. An Access Point will stop working if the ethernet connection is broken. (I'd suggest turning on WiFi Agile Multiband when this is chosen):

 
AiMesh is supposed to, (contrary to someone on this thread who deems it doesn't work,) allow you to roam/hop between router and node or node to node without loss of work, similar to cell phones moving along a freeway/road hopping from tower to tower. You'll need to understand how this is accomplished to see where drawbacks can occur:

Mesh accomplishes this with same SSID and password as you noted, but also needs two other conditions, same channel AND bandwidth. So if your router is higher spec than your node your router will be capped by the capability of the node. (It is not advisable to have two vastly different specification router and node in each frequency range, 2.4, 5 GHz, and 6 GHz. AiMesh also establishes self healing properties IF not set to Ethernet Backhaul Mode. This separates a hidden SSID_dwb along with its bandwitdh, to immediately take up the connection say if ethernet cable is unplugged/cut.

Access Point mode doesn't allow you to hop between nodes (router and nodes) without disconnecting and connecting again. (I'd suggest turning on WiFi Agile Multiband when this is chosen):


Thank you for your informed comments, that's what I was looking for. I had main/node same settings for channel and bandwidth and do also for AP mode.

I don't use "Smart Connect" and have separate SSIDs for 2.4GHz and 5GHz. Most of my clients are on 5GHz and I've read that WiFi Agile Multiband is for steering between 2.4GHz and 5GHz mostly. Does it help steering to nodes as well?
 
WiFi Agile Multiband is a WiFi.org design aimed towards large scale implementation, to distribute clients among nodes. It is specifically noted to help in environments where different manufacturers equipment may be used, but an Access Point is an Access Point. Interesting you also set both channel and bandwidth to the same setting with Access Point mode. (That's not typical but I don't know the consequences).

EDIT- SmartConnect is for band steering. As I understand 2.4 and 5 GHz have different operating ranges so as you move further away from a node it would move you from 5 GHz to 2.4 GHz, and the opposite as you move nearer). Without it your mobile device would just stay on 2.4 GHz as you move closer, supposedly. (I haven't done testing on this, but do use SmartConnect on 2.4 and 5 GHz channels).
 
Last edited:
AiMesh is supposed to, (contrary to someone on this thread who deems it doesn't work,) allow you to roam/hop between router and node or node to node without loss of work, similar to cell phones moving along a freeway/road hopping from tower to tower.


That's great! Now I can also run up and downstairs in my house while watching Netflix!!!
 
Claude AI said AiMesh is better. Who/what to believe? 😂

I'm putting it back to AiMesh
 
Last edited:
Who/what to believe?

The moment you start with ChatGPT you limit your information sources significantly. None of the experts will waste time arguing with AI crap with you translating in the middle. So you have no choice but believe ChatGPT or whatever other AI you find there. Good luck!
 
The moment you start with ChatGPT you limit your information sources significantly. None of the experts will waste time arguing with AI crap with you translating in the middle. So you have no choice but believe ChatGPT or whatever other AI you find there. Good luck!

That's why I was checking with the "experts" here
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top