What's new

[Official Release] AiMesh Firmware v3.0.0.4.384.20308 for All Supported Products

  • 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!

@arthurlien has mentioned they're going to look into it.

https://www.snbforums.com/threads/o...-supported-products.44375/page-15#post-381728

Strange thing is, I never saw this until recently. It didn't start with a firmware update, either, from what I could see. It just started happening with no changes on my end.

I hadn't noticed it either , but traffic appears to be going via ethernet so will just park it for now and wait for next firmware update

Strange that it does not show a wired connection also tho,
 
I hadn't noticed it either , but traffic appears to be going via ethernet so will just park it for now and wait for next firmware update

Strange that it does not show a wired connection also tho,
It's possible it's because it's a wired connection, since that's how I'm set up too, but I had this setup shortly after installing .10007 and never noticed it until now. Agreed that it's odd they show as wireless, not wired. Since it shouldn't be doing this in the first place, we'll just chalk it up to a bug being a bug, I guess.
 
It's possible it's because it's a wired connection, since that's how I'm set up too, but I had this setup shortly after installing .10007 and never noticed it until now. Agreed that it's odd they show as wireless, not wired. Since it shouldn't be doing this in the first place, we'll just chalk it up to a bug being a bug, I guess.

Thought I'd read at some point the connection remained in case ethernet backhaul was lost. Basically just maintains a control/ pilot channel as a fallback, so will see very minimal traffic used by that link.
 
Thought I'd read at some point the connection remained in case ethernet backhaul was lost. Basically just maintains a control/ pilot channel as a fallback, so will see very minimal traffic used by that link.
Maybe. But then when it was initially set up as wireless, wouldn't they be there all the time, then? Why would they only display on the client list once a hardwire was plugged in?
 
I don't know why people can't understand this, if you disable RA it is NOT AIMesh doing the seamless handoff, it is your CLIENT deciding it wants to switch nodes. If you disable RA you essentially just have an access point with some of the Aimesh added features like centralized management.
Not sure what part of this article you didn't understand:

https://www.smallnetbuilder.com/basics/wireless-basics/33180-how-to-fix-wi-fi-roaming

RA appears to make the router boot the client off forcefully, not seamlessly. Seamless transitions have to be managed by the client device. The real magic of AIMesh is only in making multiple routers look like a single giant router that covers your whole house. Client devices need to decide when to switch nodes. It's hard to be graceful when booted off.
The current implementation of AIMesh isn't flexible enough for my purposes as I need more control over nodes (as well as power control). From what I've learned, I don't see much benefit for a two-node system over a simple access point, so I think I'll be returning my second router today.
 
Not sure what part of this article you didn't understand:

https://www.smallnetbuilder.com/basics/wireless-basics/33180-how-to-fix-wi-fi-roaming

RA appears to make the router boot the client off forcefully, not seamlessly. Seamless transitions have to be managed by the client device. The real magic of AIMesh is only in making multiple routers look like a single giant router that covers your whole house. Client devices need to decide when to switch nodes. It's hard to be graceful when booted off.
The current implementation of AIMesh isn't flexible enough for my purposes as I need more control over nodes (as well as power control). From what I've learned, I don't see much benefit for a two-node system over a simple access point, so I think I'll be returning my second router today.
Depends on if you are doing wireless backhaul or ethernet for benefits of a two-node system. Also, I guess you don't understand how RA works either. Too bad.
 
RA appears to make the router boot the client off forcefully, not seamlessly. Seamless transitions have to be managed by the client device. The real magic of AIMesh is only in making multiple routers look like a single giant router that covers your whole house. Client devices need to decide when to switch nodes. It's hard to be graceful when booted off.

If all AiMesh RA does is drop client connections and hope those clients "seamlessly" find another node, much like AP mode RA does now, then ASUS marketing of AiMesh is going to disappoint a lot of customers... I don't see the business sense in this.

At least AiMesh has caused me to dig a little deeper... here's a few interesting WiFi links:
http://www.emperorwifi.com
https://www.networkcomputing.com/wireless-infrastructure/wifi-fast-roaming-simplified/1993108957
https://www.networkcomputing.com/wireless-infrastructure/4-wifi-band-steering-myths/1861851560

OE
 
Last edited:
Depends on if you are doing wireless backhaul or ethernet for benefits of a two-node system. Also, I guess you don't understand how RA works either. Too bad.
I don't. Please explain. Because one thing I haven't really learned in all these threads is what "magic" a mesh system actually does to help coax a client to transfer. That goes for all mesh systems. If the linked article is correct, the client always decides when to switch, so what does the mesh do, exactly, to help this process? And what difference does it make if it's a wireless or wired backend? ELI5, if you can.
 
With 10 days up time on my AC66U B1 I have noticed the RAM usage is creeping up. 52% used initially and 57% now. Single router no mesh. Any feeling if this is normal or RAM use will hit a limit?

Sent from my P01M using Tapatalk
 
I don't know why people can't understand this, if you disable RA it is NOT AIMesh doing the seamless handoff, it is your CLIENT deciding it wants to switch nodes. If you disable RA you essentially just have an access point with some of the Aimesh added features like centralized management.
Because RA will not work welll in some case, for my setup enable RA will just disconnect the device without roaming, and I am talking about at least 3sec disconnected from wifi
Sure I had try lower the RA to -70dbm but it just won't do the switch anymore
 
If all AiMesh RA does is drop client connections and hope those clients "seamlessly" find another node, much like AP mode RA does now, then ASUS marketing of AiMesh is going to disappoint a lot of customers... I don't see the business sense in this.

At least AiMesh has caused me to dig a little deeper... here's a few interesting WiFi links:
http://www.emperorwifi.com

OE
for firmware 10007 at least it better then multi AP, base on my test I found it switch to different node before the rssi too low, usually it will do the switch about -50dbm for 2.4 in my case, RA had set to -70dbm, and enable/disable RA don't make a different.

For multi AP in my setup it need the device disconnect because of weak wifi signal before it connect to another AP

I didn't do the test on newer firmware but I see the roaming need to wait longer for 20308

p.s. I didn't dig in AImesh too much but it seems the same concept as evil twin ap, I can be wrong on this.
 
Last edited:
I don't. Please explain. Because one thing I haven't really learned in all these threads is what "magic" a mesh system actually does to help coax a client to transfer. That goes for all mesh systems. If the linked article is correct, the client always decides when to switch, so what does the mesh do, exactly, to help this process? And what difference does it make if it's a wireless or wired backend? ELI5, if you can.
Yes, ultimately the client decides. There is an old saying you can lead a horse to water but you can't make it drink. Same applies here.

For anyone who has clients that disconnect when using RA and it takes a few seconds to connect again I'm curious what would happen if you used a static IP address (assuming you are using DHCP). So if you set the IP address directly on your device is the time that it is disconnected less or the same?
 
Yes, ultimately the client decides. There is an old saying you can lead a horse to water but you can't make it drink. Same applies here.

For anyone who has clients that disconnect when using RA and it takes a few seconds to connect again I'm curious what would happen if you used a static IP address (assuming you are using DHCP). So if you set the IP address directly on your device is the time that it is disconnected less or the same?
Interesting idea but I don't see a way to set a fixed IP on my android phone. Might not work it you have other wifi networks you use. Even on a laptop it would need to be configurable for each SSID.
 
for firmware 10007 at least it better then multi AP, base on my test I found it switch to different node before the rssi too low, usually it will do the switch about -50dbm for 2.4 in my case, RA had set to -70dbm, and enable/disable RA don't make a different.

For multi AP in my setup it need the device disconnect because of weak wifi signal before it connect to another AP

I didn't do the test on newer firmware but I see the roaming need to wait longer for 20308

p.s. I didn't dig in AImesh too much but it seems the same concept as evil twin ap, I can be wrong on this.

Similar here with firmware 20308... my RT-AC68U AiMesh RA RSSI defaults to -70 dBm on 5.0 GHz and -55 on 2.4 GHz. And the client switches node better than with AP Mode. It does step through the 2.4 band before settling on the 5.0 band, but who knows what the client is trying to do, and there is no SmartConnect node band steering here in the 68Us.

I don't expect uninterrupted service when moving to a different node with this equipment... just having it settle on the best node/band in less than 30 seconds using wireless backhaul (slower) once I get there is good. I'm using the same SSID for both bands... now I think I will hide my SSIDs to tidy up the neighborhood.

(Edit: Hiding the SSIDs breaks the AiMesh. AND hides the guest SSIDS, which is not true for my older ASUS RT-N66U. So, don't try this at home!)

The distance/obstacles between nodes (band range/overlap) varies for each installation and may require tweaking the RSSI disconnect thresholds.

Centralized management, not having to juggle multiple SSIDs/connections, using spare/old routers as nodes, and not having to buy/upgrade another vendor's entire canned-mesh system is a win for me.

OE
 
Last edited:
I'm new to the forum and new to iamesh .. I have the same problem.. Have RA enabled and most times I just get booted off without being reconnected to my other node even though I'm right beside it .. Or I could be right beside the node but my device would rather keep the weaker signal unless I turn off and on WiFi on my device then it will switch .. Another example is I Have a Wi-Fi camera outside my house and the tge camera would rather connect to the weaker signal then the node that is 5 feet away unless I reboot my main router then it will connect to the node that's 5 feet away ..
 
Just noticed another anomaly with app reporting, under devices my laptop showing bandwidth 100 but its a gigabit connection , router and laptop shows port correctly as 1GB connected.
 
Similar here with firmware 20308... my RT-AC68U AiMesh RA RSSI defaults to -70 dBm on 5.0 GHz and -55 on 2.4 GHz. And the client switches node better than with AP Mode. It does step through the 2.4 band before settling on the 5.0 band, but who knows what the client is trying to do, and there is no SmartConnect node band steering here in the 68Us.

I don't expect uninterrupted service when moving to a different node with this equipment... just having it settle on the best node/band in less than 30 seconds using wireless backhaul (slower) once I get there is good. I'm using the same SSID for both bands... now I think I will hide my SSIDs to tidy up the neighborhood.

(Edit: Hiding the SSIDs breaks the AiMesh. AND hides the guest SSIDS, which is not true for my older ASUS RT-N66U. So, don't try this at home!)

The distance/obstacles between nodes (band range/overlap) varies for each installation and may require tweaking the RSSI disconnect thresholds.

Centralized management, not having to juggle multiple SSIDs/connections, using spare/old routers as nodes, and not having to buy/upgrade another vendor's entire canned-mesh system is a win for me.

OE
It's also been said that hiding your SSID is actually less secure.

https://www.howtogeek.com/howto/286...hiding-your-wireless-ssid-really-more-secure/
 
Interesting idea but I don't see a way to set a fixed IP on my android phone. Might not work it you have other wifi networks you use. Even on a laptop it would need to be configurable for each SSID.
I agree with that. Just trying to see if it makes any difference then folks who have that issue could maybe work with an ASUS engineer to find a more permanent fix if that is indeed an issue. So far it seems that most people having issues with their devices disconnect are using an Android based device. Unfortunately I don't have any to roam around my house with to test. The devices I roam around the house with are iOS based and they don't exhibit this behavior.

Does this work on your Android based device?

If you go to wifi settings you can hold down on your connected ssid/network name and set dhcp to static.
 
Last edited:
Just noticed another anomaly with app reporting, under devices my laptop showing bandwidth 100 but its a gigabit connection , router and laptop shows port correctly as 1GB connected.

App Devices/device/Bandwidth (greyed) shows 100 Mbps up and down for all devices... this is meaningless, imo.

BTW, I have a Dell Latitude Win10 Pro with an Intel Dual Band Wireless-AC 8265 adapter. I had to enable Network Connection/network/Wireless Properties/'Look for other wireless networks while connected to this network' to fix this client's band steering. It then immediately switched from 2.4 (n-only 150 Mbps) to 5.0 (n/ac 866 Mbps). Same SSID on both bands.

The WiFi client is not always right! :)

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