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

[FlaXXMaN]

Hello All,
I purchased a RT-AC3100 as a master node, and using a RT-AC1900P as a wireless node.
-I also continue to get the firmware updates on mobile app even though firmware is up to date. If i go in router web page and look, its fine until i click "check" and then it shows updates available. I've even tried doing the firmware update anyways just to see if it would dismiss it, but still shows up.
-The wireless node does drop to "offline" after several hours. It seems to be somewhat working however wireless clients never transfer to the wireless node once they've attached to the main node, but just shows offline on the master node. Rebooting the wireless node makes it appear as Online again.

When its working, speeds are great - i have some PC's wired into the wireless node and get decent speeds...hopefully a fix comes out for the "offline" issue and i'll be all set.
Is there a way to access the config of the wireless node? I was thinking in the meantime, i could setup a automatic restart daily or something on it? Trying to hit the webpage of it just pushes me to the master node.

 

[Ciprip]

Everything runs fine for me, on the two independent setups I have.
- 3 x TM AC1900 converted to AC68P
- 1 x GT AC5300 (Main) + AC68U (Unmodified Node).
Almost no issues, but on both setups, if I use a browser to login to the routers and go under Administration -> Firmware update, it immediately displays the firmware upgrade percentage bar. Nothing happens if I wait it out but also if I use the back button to exit out of the update.

Mobile app works without any issues what so ever.

Anyone else ran into this?

 

[Rajesh Honnawarkar]

Everything runs fine for me, on the two independent setups I have.
- 3 x TM AC1900 converted to AC68P
- 1 x GT AC5300 (Main) + AC68U (Unmodified Node).
Almost no issues, but on both setups, if I use a browser to login to the routers and go under Administration -> Firmware update, it immediately displays the firmware upgrade percentage bar. Nothing happens if I wait it out but also if I use the back button to exit out of the update.

Mobile app works without any issues what so ever.

Anyone else ran into this?

See https://www.snbforums.com/threads/a...-version-3-0-0-4-384-20287.44216/#post-376254 and some of the following threads...

 

[Ciprip]

See https://www.snbforums.com/threads/a...-version-3-0-0-4-384-20287.44216/#post-376254 and some of the following threads...

I figured it out, at least for me. I only encounter the issue if I access the admin page thrugh the DNS page. If it's accede usig the local IP address, the issue doesn't occur.
Most likely a bug in regards to the DDNS handling.

 

[Richard Li]

You realize you did not pay for AiMesh tho, right? AiMesh is a totally new feature added afterward. It's a complex system, and will take time to stabilize. Asus are trying something that nobody has ever done here: implementing mesh networking on top of existing products that weren't originally designed for it.

Agreed, that is why I did a lot of tests and help out the debugging with ASUS team. They are doing amazing things and need a lot of effort to make it stable, especially when doing a setup with hybrid devices like me 2 x 88U + 1 x 68U.

 

[Flipmode11]

Should I be using Merlin firmware or this firmware?
I've used Merlin successfully with AC66u for couple years with no issues...

Do you recommend the RT-AC3100 or the RT-AC68U?
Network? 5 VoIP devices and 10 notebooks.

Other clients have had no issue with AC68U with 35 users.
Just that the AC68u and AC3100 are the same price.

Thanks!

 

[Richard Li]

SOOOOO FRUSTRATED, the new 3.0.0.4.384_20287 took 4 minutes node to went offline!!

Also, keep triggering the firmware upgrade progress page until you restart, seriously NO ONE AT ASUS NOTICE THIS BEFORE RELEASiNG this???

TWO AC68U CONNECTED WIRELESSLY

It is supposed to be a PRODUCTION WORKING AND TESTED FIRMWARE, WE PAID $$$$$ FOR THIS ROUTERS, YOU ARE NOT DOING ANY "FAVOR" TO US, YOU ARE NOT MERLING THAT DONATES HIS WORK FOR LOVE AND NEVER EVER EVER HE RELEASE THIS KIND OF UNPROFESSIONAL WORK, SHAME!!

This start sounding like a BAD JOKE!!!

Sorry but true

I have done my upgrade manually, one by one using the manual link in the setup, here is my procedures:
1. Upgrade the nodes first, I just want to make sure the router/ap to keep up without rebooting before all the nodes are done.
2. After each node upgrade, need to wait a while for the node to connect the router after rebooted, I just use ping to check if everything stable before upgrading the other one.

Each device need 3-4 mins for upgrading, this is a must, you need to upload, flash, reboot each device.

And I got an upgraded version.

 

[Richard Li]

Should I be using Merlin firmware or this firmware?
I've used Merlin successfully with AC66u for couple years with no issues...

Do you recommend the RT-AC3100 or the RT-AC68U?
Network? 5 VoIP devices and 10 notebooks.

Other clients have had no issue with AC68U with 35 users.
Just that the AC68u and AC3100 are the same price.

Thanks!

Merlin's firmware cannot support AiMesh in future release since AiMesh is close source. So it depends if you need AiMesh.

 

[Richard Li]

I have experienced Wifi disconnection even though my STA did not moved around, let see what can we do to nail down the problem:

I have a MiPad with MAC address [c4:0b:cb:50:ab:e3] placed in my room and I used it to play a network game and experienced many Wifi disconnection. From the syslog in the node, I have figure out a list of add client action, in which it is the disconnection point.

I used my devices as AP setup all the time without any problem, this kind of disconnection experience is after setting up AiMesh with both firmware 10007 and 20287. Just want to know is there anyway to enable debugging log level so that the problem can be tracked and resolved. I am willing to help for the testing.

Jan 28 09:58:57 roamast: wl0.1: disconnect weak signal strength station [00:28:f8:72:92:32]
Jan 28 09:58:57 roamast: wl0.1: remove client [00:28:f8:72:92:32] from monitor list
Jan 28 10:06:49 roamast: wl0.1: add client [38:a4:ed:bd:81:8f] to monitor list
Jan 28 10:37:09 roamast: wl1.1: add client [c4:0b:cb:50:ab:e3] to monitor list
Jan 28 10:52:09 roamast: wl1.1: add client [c4:0b:cb:50:ab:e3] to monitor list
Jan 28 10:58:19 roamast: wl0.1: add client [00:28:f8:72:92:32] to monitor list
Jan 28 10:58:19 roamast: wl0.1: add client [ac:c1:ee:e5:d5:58] to monitor list
Jan 28 10:58:19 roamast: wl1.1: add client [38:a4:ed:bd:81:8f] to monitor list
Jan 28 10:58:37 roamast: discover candidate node [B0:6E:BF:6B:A2:A0](rssi: -63dbm) for weak signal strength client [AC:C1:EE:E55:58](rssi: -83dbm)
Jan 28 10:58:37 roamast: wl0.1: disconnect weak signal strength station [ac:c1:ee:e5:d5:58]
Jan 28 10:58:37 roamast: wl0.1: remove client [ac:c1:ee:e5:d5:58] from monitor list
Jan 28 10:58:39 roamast: wl1.1: add client [c4:0b:cb:50:ab:e3] to monitor list
Jan 28 11:04:32 roamast: discover candidate node [B0:6E:BF:6B:A2:A0](rssi: -32dbm) for weak signal strength client [00:28:F8:72:92:32](rssi: -73dbm)
Jan 28 11:04:32 roamast: wl0.1: disconnect weak signal strength station [00:28:f8:72:92:32]
Jan 28 11:04:32 roamast: wl0.1: remove client [00:28:f8:72:92:32] from monitor list
Jan 28 11:07:09 roamast: wl1.1: add client [c4:0b:cb:50:ab:e3] to monitor list
Jan 28 11:21:59 roamast: wl0.1: add client [38:a4:ed:bd:81:8f] to monitor list
Jan 28 11:21:59 roamast: wl1.1: add client [ec:d0:9f:32:1e:52] to monitor list
Jan 28 11:28:29 roamast: wl1.1: add client [38:a4:ed:bd:81:8f] to monitor list
Jan 28 11:37:04 roamast: wl0.1: add client [38:a4:ed:bd:81:8f] to monitor list
Jan 28 11:58:49 roamast: wl1.1: add client [38:a4:ed:bd:81:8f] to monitor list
Jan 28 12:07:34 roamast: wl0.1: add client [38:a4:ed:bd:81:8f] to monitor list
Jan 28 12:07:44 roamast: wl1.1: add client [c4:0b:cb:50:ab:e3] to monitor list
Jan 28 12:14:24 roamast: wl1.1: add client [a0:c5:89:4a:0d:b7] to monitor list
Jan 28 12:22:34 roamast: wl0.1: add client [a0:c5:89:4a:0d:b7] to monitor list
Jan 28 12:28:39 roamast: wl1.1: add client [38:a4:ed:bd:81:8f] to monitor list
Jan 28 12:31:14 roamast: wl0.1: add client [ac:c1:ee:e5:d5:58] to monitor list
Jan 28 12:31:42 roamast: discover candidate node [34:97:F6:22:C4:00](rssi: -72dbm) for weak signal strength client [AC:C1:EE:E55:58](rssi: -85dbm)
Jan 28 12:31:42 roamast: wl0.1: disconnect weak signal strength station [ac:c1:ee:e5:d5:58]
Jan 28 12:31:42 roamast: wl0.1: remove client [ac:c1:ee:e5:d5:58] from monitor list
Jan 28 12:32:22 roamast: discover candidate node [B0:6E:BF:6B:A2:A0](rssi: -46dbm) for weak signal strength client [A0:C5:89:4A:0D:B7](rssi: -73dbm)
Jan 28 12:32:22 roamast: wl0.1: disconnect weak signal strength station [a0:c5:89:4a:0d:b7]
Jan 28 12:32:22 roamast: wl0.1: remove client [a0:c5:89:4a:0d:b7] from monitor list
Jan 28 12:37:39 roamast: wl0.1: add client [38:a4:ed:bd:81:8f] to monitor list
Jan 28 12:57:29 roamast: wl1.1: add client [c4:0b:cb:1e:87:ea] to monitor list

 

[Richard Li]

I have some more experience about how to put AiMesh system in a stable state. Once I have setup the AiMesh, if I want to work out some restarting, the rebooted system may not be stable anymore. I have tried many different reboot procedures and found that this is the way that gives the stability to the system:

1. boot up the nodes first
2. boot up the main router/ap

If I reverse the order during boot up, the final system may not be stable:

1. boot up the main router/ap first
2. boot up the nodes

I do not know why, but this is what I observed. So if your AiMesh system performs weird , try shutdown the whole system and boot up the nodes first, then followed by the main router/ap

 

[Richard Li]

A few questions about the functionalities of AiMesh:

1. Will AiMesh scan the environment and choose the best channels for different router/node? What is the frequency of this checking and may cause the router/node to change channel?
2. Will AiMesh dynamically adjust the TxPower of each router/node to achieve best result? Sometimes router/nodes may not be too separated due to physical limitations, and lowering the TxPower in some setup can achieve better result.

 

[Ronald Schwerer]

Hey moderators. Can we get a pinned thread like this ( [Official Release] AiMesh Firmware v3.0.0.4.384.10007 for All Supported Products) for the 20287 release? As it is we are getting a 20287 thread for each of the supported product variations. Seems silly and a poor way to share information. Keep in mind that all the AC1900 based products (AC1900*, AC68*, maybe more) share the same firmware image.
Also, I get that converted TM-AC1900 units should keep their conversion issues on a dedicated thread, but once successfully converted and running AiMesh there's no difference and no reason to keep them isolated.

 

[qxl0]

I brought two RT-AC88U Asus routers from Amazon.com. and tried to set up a Aimesh network.
1. Upgraded both to the latest firmware which is 384.20287
2. Set up one as my main router, which is successfully connected to my Fios
3. The problem is to add my other AC88U as the Aimesh node. No matter what I tried, it always failed to be added.
The router can find it easily. But it always failed to add it as Aimesh node at the end.

I tried several ways to reset the node AC88U by
1. hard reset by pushing down the reset button on the back
or
2. by connecting to it and use the wizard page to set it as an Aimesh node

I tried at least 10 times without luck!!! It always failed after a lengthy syncing and give out the failure message.


So disappointed with ASUS.

Why not give us the exact error message so we know what to do and try? Why just gave out the general failure message??

Also I feel so surprised that I can't do that for two of AC88U routers.

Thanks

 

[Quad80]

I just updated my RT-AC68R and RT-AC68U both to version 3.0.0.4.384_20287-g51c2770, from 10007.

Apparently, the UPDATE FIRMWARE button that appears when you CHECK in the GUI for new FW, doesn't do anything anymore? I rebooted the router after using the button, after watching what looked like a FW progress bar, but the 10007 FW was still there!?!

I downloaded the 20287 update to my PC and updated the node and router manually. Updated the node first and router second, and everything was reconnected after router update completed.

New here, but I just set up a mesh network with two RT-AC3100s and I noticed the same thing when trying to update from 10007 to 3.0.0.4.384_20287. The button will look like it's working, but even after a manual reboot, the firmware doesn't update. Funny enough, when I updated to 10007 a couple weeks ago, I couldn't get the manual update to work and had to use the button in the settings. Seems I have the opposite issue now. Firmware updates seem to be a bit glitchy, at any rate.

But while I'm here, since I'm new to this AiMesh setup, there is one question I haven't been able to officially confirm. It looks like WPS has to stay on, at least for 2.4. Is that accurate? If I try to turn it off, it tells me the AiMesh connectivity will be affected if I do. I'd rather have WPS off entirely, as I've never used it and I know it has been insecure for many years now. If I turn it off, does it kill the mesh connection? How can I secure this?

 

[Richard Li]

I brought two RT-AC88U Asus routers from Amazon.com. and tried to set up a Aimesh network.
1. Upgraded both to the latest firmware which is 384.20287
2. Set up one as my main router, which is successfully connected to my Fios
3. The problem is to add my other AC88U as the Aimesh node. No matter what I tried, it always failed to be added.
The router can find it easily. But it always failed to add it as Aimesh node at the end.

I tried several ways to reset the node AC88U by
1. hard reset by pushing down the reset button on the back
or
2. by connecting to it and use the wizard page to set it as an Aimesh node

I tried at least 10 times without luck!!! It always failed after a lengthy syncing and give out the failure message.


So disappointed with ASUS.

Why not give us the exact error message so we know what to do and try? Why just gave out the general failure message??

Also I feel so surprised that I can't do that for two of AC88U routers.

Thanks

I think I can help, I have setup my AiMesh system with 3 devices: 88U as AP and 88U + 68U nodes.
It is a bit tricky to add AiMesh nodes, I have some experiences:

1. Need to make sure router and nodes need to be factory reset (press WPS button -> power on -> wait for power led to flash -> release WPS button)
2. place router and node close to one another, but not too close
3. node should be standalone without anything plug in any ethernet ports
4. do minimal settings in the router and start binding the node, I have tried to fail in adding the node when I did too much settings. The actual case is to setup MAC address filtering and load in a list of MAC addresses, after that I always failed to bind the node.
5. You need to have WPS on for the binding to work.

Hope this helps.

2 x 88U should be able to work properly, most of the problem I found is I have another 68U.

 

[y2jdmbfan]

Is anyone else having a problem running the Windows 10 Speedtest.net desktop app after installing an 86U? When I run it now, it completely kills the Internet connection on this PC. As soon as I kill the program, net connection comes back. Didn't happen when connection to my previous OnHub's.

 

[Ken Atkinson]

New here, but I just set up a mesh network with two RT-AC3100s and I noticed the same thing when trying to update from 10007 to 3.0.0.4.384_20287. The button will look like it's working, but even after a manual reboot, the firmware doesn't update. Funny enough, when I updated to 10007 a couple weeks ago, I couldn't get the manual update to work and had to use the button in the settings. Seems I have the opposite issue now. Firmware updates seem to be a bit glitchy, at any rate.

But while I'm here, since I'm new to this AiMesh setup, there is one question I haven't been able to officially confirm. It looks like WPS has to stay on, at least for 2.4. Is that accurate? If I try to turn it off, it tells me the AiMesh connectivity will be affected if I do. I'd rather have WPS off entirely, as I've never used it and I know it has been insecure for many years now. If I turn it off, does it kill the mesh connection? How can I secure this?

Ok to switch off WPS , only needed on Mesh setup which it will switch on itself hence your warning msg.

 

[arthurlien]

Issue with MediaBridge mode is still present with 384.20287. Works perfectly for 30 min and after problem come back, no internet or lan access for the devices behind the bridge.Need reboot and its ok for a while.
https://www.snbforums.com/threads/rt-ac68u-version-3-0-0-4-384-10007.43114/page-2#post-373792

May i know which version you are using in your router ?

PS. I had test and work normal over 2 hours...

 

[Quad80]

Ok to switch off WPS , only needed on Mesh setup which it will switch on itself hence your warning msg.

Thanks! Switched off and all seems well

I assume that if I ever need to reboot or the power goes out or whatever, that it'll still come up and sync the node properly, since it's already paired. Or will I need to re-sync manually now that WPS is disabled?

 

[Flipmode11]

Oh geez, I don't know what to do. AC68u or AC3100.... :/
Is the 3100 that much better in performance?