What's new
  • 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!

New Official Firmware Support from Asus

Fresh Tomato does have VLAN support in GUI though and what Asus calls AiMesh can be re-created on 2x RT-AC68U routers plus extra features AiMesh doesn't have in original firmware for this model. Someone on a budget with no big performance needs or expectations can actually do it.
The point of AiMesh is centralized management. Having a bunch of APs and Repeaters doest not re-create that.
A bunch of VLAN capable APs with individual channel and power output control is better than central management with limited control and all "nodes" sharing the same channel available bandwidth. It doesn't re-create AiMesh drawbacks either.
The main purpose of a mesh network—including AiMesh—is to extend your Wi-Fi’s range and allow clients to roam reliably between nodes though features like "Client steering" and "Band steering". Simply setting up access points with the same SSID does not achieve this in my experience, as clients tend to perform poorly when switching from one node to another as the signal weakens and a stronger one becomes available. This has been my daily experience with an iPhone, as well as other clients.
 
including AiMesh

AiMesh has basic implementation of both. In my own experience Asus Nodes vs AP/Repeaters produce exactly the same roaming user experience and it's worse than similar Qualcomm based home mesh systems with built-in mesh capabilities on wireless driver level and with self-adjustment based on signal/distance to Satellites. Asus marketing makes you believe you need AiMesh for "seamless" roaming, but the reality is the client decides where to connect and when to switch. Mesh/multi-AP systems only employ different methods of encouragement this to happen. AiMesh is quite far from controller managed systems and if you have a chance to test Omada multi-AP system you'll see the difference. Your iPhone is one of so called "sticky clients" when used with AiMesh. Apple devices hold the connection until it becomes practically unusable. Your only tool in AiMesh and AP/Repeaters to prevent this from happening is Roaming Assistant and it produces inconsistent results on different Asus devices. You can't even adjust the Tx power per Node in AiMesh in 386/388 firmware, not to mention dynamic Tx power control.
 
AiMesh has basic implementation of both.
Fresh Tomato does have VLAN support in GUI though and what Asus calls AiMesh can be re-created on 2x RT-AC68U routers plus extra features AiMesh doesn't have in original firmware for this model. Someone on a budget with no big performance needs or expectations can actually do it.
A bunch of VLAN capable APs with individual channel and power output control is better than central management with limited control and all "nodes" sharing the same channel available bandwidth. It doesn't re-create AiMesh drawbacks either.
Could you clarify in technical terms how FreshTomato can be configured to provide mesh-like functionality that mitigates some of AiMesh’s limitations?

Specifically, aside from configuring multiple APs with identical SSIDs and possibly coordinating channel and TX power settings, what mechanisms are in place to facilitate seamless client roaming or steering? To my knowledge, FreshTomato lacks support for Layer 2 mesh protocols like 802.11s and does not implement 802.11k/v/r for assisted roaming or BSS transition management.

Without such protocols, what techniques or features are you referring to that would encourage or manage client handoff between APs more effectively than AiMesh?
 
Could you clarify in technical terms how FreshTomato can be configured to provide mesh-like functionality that mitigates some of AiMesh’s limitations?

It offers VLAN support, Tx power, Channel control and Roaming Assistant - all you need. Keep in mind we are talking about options of prolonging the life of unsupported obsolete hardware. Not in general, but for specific hardware with e-waste status in 2025.

802.11k/v/r

Whatever is supported by the wireless drivers works exactly the same way in AiMesh, AP Mode and Repeater configurations. AiMesh add-on software in Asuswrt in particular on top of Broadcom software doesn't provide any extra roaming assist technologies.
 
Roaming Assistant
In FreshTomato? Not from what my research has gathered.

It also lacks the ability to set minimum RSSI per client or node like you can in Aimesh. Plus Aimesh probbly has some proprietary blend that might implement other mesh technologies, that is not available in FreshTomato.

So you're limited to Tx control and Channel control.

Channel control is only useful for providing roaming clues for clients as long as you have a wired backhaul, as they can't receive and send at different channels. I guess the possible exception (if this is possible in FreshTomato) is if you have a router with dedicated backhaul radio.

As far as Tx tuning, I've never done it myself - mapping it out sounds like a nightmare, since you are trying to balance the possibility of better roaming with a loss in performance. Do you happen to know of any resources (preferably a instructional video) where this is demonstrated, that you can recommend? (or mesh tuning in general for that matter. I'm looking into OpenWrt these days, trying to score some dirt cheap Netgear 7800's for a new mesh network on the cheap, with no EOL's looming, and no hassle with testing and risks of everything turning sour everytime I upgrade the firmware)
 
Let's leave behind FT talk, option for people on extreme budget or with old equipment.

Channel control is only useful for providing roaming clues for clients

Channel control is useful for higher bandwidth, has little to do with roaming. APs working on different channel will have higher aggregate throughput to clients than APs working on the same channel. You can test with Router + AP Mode vs AiMesh and will see the difference immediately. In optimal conditions the throughput can be up to 100% higher.

As far as Tx tuning... since you are trying to balance the possibility of better roaming with a loss in performance.

You may want to read more about how Wi-Fi works. Blasting full power is nothing near better performance. Balancing link speeds is better performance. Your home AIO router may reach 1000mW, your client devices may never exceed 40mW. Wi-Fi is a two-way communication and goes through the same obstacles back and forth. About better roaming - the APs have to be spaced out properly (physically or by signal level) and more APs on lower power work better. One old post about this here. Planning your network - you can play with various design centers available for SMB equipment and "port" the results to whatever you have. May give you general idea at least. Omada and UniFi have this tool built into the controller software:

 
Last edited:

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!
Back
Top