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

[RandomName23]

Thanks!

I have a fairly smallish home but I was trying to use aimesh to improve backyard and frontyard coverage for security cameras. Apparently, a side-effect of having closely spaced nodes seems to be causing stationary devices (TV, chromecast etc) drop wifi sporadically.

I have made the following additional changes now -- Airtime Fairness & Universal beam-forming - Disabled and Roaming assistant threshold at -65/-70 dBm.

hopefully, I should be able to monitor if they are getting kicked off by "roam assist" feature unnecessarily.

This is where being able to change the transmission power of the radios (or even turn them off) on the Aimesh nodes would be really helpful.

 

[TonyRI]

Current version on my RT-AC68 Current Version : 3.0.0.4.384_20287-g51c2770

Latest Version : 3.0.0.4.384_20308-gead790e but were do you download it from the Auto update feature does not work
on Asus support pages no such firmware Whats UP!

Also Fail to grab release note

Was pleased to see the Check Firmware UI button working today which upgraded both my 86U Main (previously 10007) and 68R Node (previously 20287) to new version 20308

Checking button again now indicates that the firmware is current, as expected.

Notice that the previous "More Config" button on the node settings now works correctly when selecting Connection Priority "Auto". Even though there is an unmanaged switch in between Main and Node, I no longer have to force the Wired backhaul Connection status by selecting "Ethernet".

Main and Node are playing well together.

The only issue that I see is the wired client connected to the node will always show on the Network Map, it has an assigned IP an works correctly, however it will appear, disappear and reappear as a wired client on the node.

Thanks for the Update. Centralized Management worked as expected, was convenient and easy. I think that they are now much closer to the design intent. It would be nice to be able to see a list of fixes/release notes.

 

[mogulman]

Current version on my RT-AC68 Current Version : 3.0.0.4.384_20287-g51c2770

Latest Version : 3.0.0.4.384_20308-gead790e but were do you download it from the Auto update feature does not work
on Asus support pages no such firmware Whats UP!

Also Fail to grab release note

I have one AP master going to 2 nodes (SSID AiMesh)
another AP master going to 1 node (SSID AiMesh86)

All RT-AC68Ps

Ok after I rebooted the Master AP (SSID AiMesh) the auto update worked
to Current Version : 3.0.0.4.384_20308-gead790e on Master and one Node other still on old version 3.0.0.4.384_20287-g51c2770

I used the auto update and my 86u and 1900p both updated.

 

[scope666]

I used the auto update and my 86u and 1900p both updated.

Same here with an 86U and 68U ... interesting that you can update via auto update, but the web site still has the old versions.

 

[TonyRI]

Same here with an 86U and 68U ... interesting that you can update via auto update, but the web site still has the old versions.

Firmware Engineers work quicker than Web Designers?

 

[TonyRI]

(New Version 20308) Oops... Noticed one Issue with the "Network Map" button under "General" Settings. Does not appear to function anymore. Now have to click on "View List"/Clients Icon to see lists

EDIT: Sorry, I was having an "elderly" moment here... All is working well

 

[LimJK]

I used the auto update and my 86u and 1900p both updated.

Thank you to all you brave souls ... I followed your footstep ... did the Firmware upgrade from the GUI.
also thanks to Arthur and the rest from the ASUS team, Thank You!

 

[mlippold]

(New Version 20308) Oops... Noticed one Issue with the "Network Map" button under "General" Settings. Does not appear to function anymore. Now have to click on "View List"/Clients Icon to see lists

Both of these are working for me on 20308 on a RT-AC5300 so you may want to try a reboot of the router (I will note that I don't have a mesh setup - so if it is still broken after you reboot the routers maybe it is related to that).

I did notice that after I made some client changes in QOS and applied them (simply changed some priorities) that my Twitch stream on a FireTV started repeatedly buffering (And no... it wasn't that a higher priority client was eating up the bandwidth - I have 100 mbps down and the load was only at around 4 mbps the whole time the buffering started). After a reboot of the router it is all working fine now. It still seems like something is broken when making networking changes and applying them.

 

[LimJK]

(New Version 20308) Oops... Noticed one Issue with the "Network Map" button under "General" Settings. Does not appear to function anymore. Now have to click on "View List"/Clients Icon to see lists

Tony,
It is working for me I followed the instruction to manually reboot my RT-AC5300 AiMesh Router

 

[y2jdmbfan]

Thank you to all you brave souls ... I followed your footstep ... did the Firmware upgrade from the GUI.
also thanks to Arthur and the rest from the ASUS team, Thank You!

View attachment 11808

I noticed you have the 5300 and 2 of the new 86U's. Did the 5300 not give you enough range requiring the 2 additional 86U's?

 

[Volfi]

BUG: I am runnig .20282 on AC88U and .10007 on AC86U. Whenever I click on firmware version on top, it will show firmware version and immediately start the upgrade. Nothing will be upgraded though.

// edit: after restart, I can get into FW upgrade page without FW upgrade autostart, and do it manually, using http://dlcdnet.asus.com/pub/ASUS/wireless/RT-AC86U/FW_RT_AC86U_300438410007.ZIP file. Still, the bug should be fixed.

 

[LimJK]

I noticed you have the 5300 and 2 of the new 86U's. Did the 5300 not give you enough range requiring the 2 additional 86U's?

Oops,
(1) I like speed I now get about 400-500 mbps wirelessly
(2) WiFi signal got 4 walls to cross due to the layout of my place
(3) I used to run RT-AC5300 as Router with RT-AC68U as AP; without AiMesh it was a pain when I am in zone of uncertainty between Router and AP.

Now I am happy ... to support ASUS, I bought 2 RT-AC86U to replace my very old RT-AC68U

 

[Ken Atkinson]

Tried latest update 20308 from PC connected said updaing nothing happened , initiated via android app and both routers have upgraded , seem to be working okay but I haven't rebooted either my main AC88U or mesh AC66U-B1..

Edit, my echo's not connecting , rebooting routers

 

[LimJK]

Arthur or anyone else,

Will the GUI "Firmware Upgrade", Auto Upgrade from "Beta Firmware" to the current 3.0.0.4.384_20308-gead790e or do I have to manually upgrade from Beta to Released Firmware first?

Specifically I have helped a friend setup 2 weeks ago the following scenario (Wired Backhaul):

AiMesh Router:

• RT-AC5300 Beta Firmware: 9.0.0.4_382_19612

AiMesh Nodes:

• RT-AC5300 Beta Firmware: 9.0.0.4_382_19612
• RT-AC86U Released Firmware: 3.0.0.4.384.10007

 

[Ciprip]

I noticed you have the 5300 and 2 of the new 86U's. Did the 5300 not give you enough range requiring the 2 additional 86U's?

It did, but I wanted to play arround with the mesh setup, as I'm moving to a bigger house soon. Most devices stay connected to the 5300
Both setups work perfectly so far!

 

[mogulman]

This is happening now without RDP even being involved. Log with notes. Seems like AiMesh (over ethernet) seems to reconnect whenever my PC reconnects. Here is the log with my notes while it happened. If I don't do anything, it seems like it takes 5 minutes for PC1 to reconnect on it's own. I sent you a copy of this with MAC addresses via the Feedback email.

*** Cleared Log, Resume from Sleep PC2 (30:e1:71:xx:xx:xx)
Jan 31 14:00:34 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
*** Standby/Sleep PC2
Jan 31 14:01:00 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.
*** PC1 (ec:f4:bb:xx:xx:xx) loses network connection, pings to router timeout, but still shows link up from PC.
Jan 31 14:01:00 kernel: net_ratelimit: 134 callbacks suppressed
Jan 31 14:01:05 kernel: net_ratelimit: 181057 callbacks suppressed
Jan 31 14:01:10 kernel: net_ratelimit: 169700 callbacks suppressed
Jan 31 14:01:15 kernel: net_ratelimit: 176202 callbacks suppressed
Jan 31 14:01:20 kernel: net_ratelimit: 179251 callbacks suppressed
Jan 31 14:01:25 kernel: net_ratelimit: 180408 callbacks suppressed
Jan 31 14:01:30 kernel: net_ratelimit: 170621 callbacks suppressed
Jan 31 14:01:35 kernel: net_ratelimit: 175121 callbacks suppressed
Jan 31 14:01:40 kernel: net_ratelimit: 169601 callbacks suppressed
Jan 31 14:01:45 kernel: net_ratelimit: 171405 callbacks suppressed
Jan 31 14:01:50 kernel: net_ratelimit: 172444 callbacks suppressed
Jan 31 14:01:55 kernel: net_ratelimit: 182709 callbacks suppressed
*** Resume PC2 again
Jan 31 14:02:00 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
*** PC1 has network connectivity again
Jan 31 14:02:00 kernel: net_ratelimit: 176069 callbacks suppressed
Jan 31 14:02:05 kernel: net_ratelimit: 88224 callbacks suppressed
Jan 31 14:02:23 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 0
Jan 31 14:02:23 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 1
Jan 31 14:02:26 kernel: wfd_registerdevice Successfully registered dev wds0.0.3 ifidx 1 wfd_idx 0
Jan 31 14:02:26 kernel: Register interface [wds0.0.3] MAC: b0:6e:bf:xx:xx:xx
Jan 31 14:02:27 kernel: wfd_registerdevice Successfully registered dev wds1.0.3 ifidx 1 wfd_idx 1
Jan 31 14:02:27 kernel: Register interface [wds1.0.3] MAC: b0:6e:bf:xx:xx:xx
Jan 31 14:02:30 roamast: eth5: add client [f0:03:8c:xx:xx:xx] to monitor list
*** Standby PC2 again
Jan 31 14:03:45 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.
*** PC1 loses network connection again. waiting
Jan 31 14:04:10 kernel: net_ratelimit: 126559 callbacks suppressed
Jan 31 14:04:15 kernel: net_ratelimit: 176078 callbacks suppressed
Jan 31 14:04:20 kernel: net_ratelimit: 177879 callbacks suppressed
Jan 31 14:04:25 kernel: net_ratelimit: 166737 callbacks suppressed
Jan 31 14:04:30 kernel: net_ratelimit: 179658 callbacks suppressed
Jan 31 14:04:35 kernel: net_ratelimit: 166097 callbacks suppressed
Jan 31 14:04:40 kernel: net_ratelimit: 165306 callbacks suppressed
Jan 31 14:04:45 kernel: net_ratelimit: 165562 callbacks suppressed
Jan 31 14:04:50 kernel: net_ratelimit: 167024 callbacks suppressed
Jan 31 14:04:55 kernel: net_ratelimit: 165358 callbacks suppressed
Jan 31 14:05:00 kernel: net_ratelimit: 176627 callbacks suppressed
Jan 31 14:05:05 kernel: net_ratelimit: 176284 callbacks suppressed
Jan 31 14:05:10 kernel: net_ratelimit: 164857 callbacks suppressed
Jan 31 14:05:15 kernel: net_ratelimit: 165861 callbacks suppressed
Jan 31 14:05:20 kernel: net_ratelimit: 165095 callbacks suppressed
Jan 31 14:05:25 kernel: net_ratelimit: 182026 callbacks suppressed
Jan 31 14:05:30 kernel: net_ratelimit: 174007 callbacks suppressed
Jan 31 14:05:35 kernel: net_ratelimit: 178554 callbacks suppressed
Jan 31 14:05:40 kernel: net_ratelimit: 166444 callbacks suppressed
Jan 31 14:05:45 kernel: net_ratelimit: 181106 callbacks suppressed
Jan 31 14:05:50 kernel: net_ratelimit: 170976 callbacks suppressed
Jan 31 14:05:55 kernel: net_ratelimit: 176695 callbacks suppressed
Jan 31 14:06:00 kernel: net_ratelimit: 166212 callbacks suppressed
Jan 31 14:06:00 roamast: eth5: add client [50:c7:bf:xx:xx:xx] to monitor list
Jan 31 14:06:05 kernel: net_ratelimit: 168028 callbacks suppressed
Jan 31 14:06:10 kernel: net_ratelimit: 176777 callbacks suppressed
Jan 31 14:06:15 kernel: net_ratelimit: 165737 callbacks suppressed
Jan 31 14:06:20 kernel: net_ratelimit: 172389 callbacks suppressed
Jan 31 14:06:25 kernel: net_ratelimit: 167916 callbacks suppressed
Jan 31 14:06:30 kernel: net_ratelimit: 164802 callbacks suppressed
Jan 31 14:06:35 kernel: net_ratelimit: 163943 callbacks suppressed
Jan 31 14:06:40 kernel: net_ratelimit: 176568 callbacks suppressed
Jan 31 14:06:45 kernel: net_ratelimit: 167171 callbacks suppressed
Jan 31 14:06:50 kernel: net_ratelimit: 170062 callbacks suppressed
Jan 31 14:06:55 kernel: net_ratelimit: 173788 callbacks suppressed
Jan 31 14:07:00 kernel: net_ratelimit: 170299 callbacks suppressed
Jan 31 14:07:05 kernel: net_ratelimit: 170278 callbacks suppressed
Jan 31 14:07:10 kernel: net_ratelimit: 182016 callbacks suppressed
Jan 31 14:07:15 kernel: net_ratelimit: 173293 callbacks suppressed
Jan 31 14:07:20 kernel: net_ratelimit: 174585 callbacks suppressed
Jan 31 14:07:25 kernel: net_ratelimit: 166974 callbacks suppressed
Jan 31 14:07:30 kernel: net_ratelimit: 165805 callbacks suppressed
Jan 31 14:07:36 kernel: net_ratelimit: 166469 callbacks suppressed
Jan 31 14:07:41 kernel: net_ratelimit: 165415 callbacks suppressed
Jan 31 14:07:46 kernel: net_ratelimit: 167554 callbacks suppressed
Jan 31 14:07:51 kernel: net_ratelimit: 166086 callbacks suppressed
Jan 31 14:07:56 kernel: net_ratelimit: 167929 callbacks suppressed
Jan 31 14:08:01 kernel: net_ratelimit: 166486 callbacks suppressed
Jan 31 14:08:06 kernel: net_ratelimit: 159741 callbacks suppressed
Jan 31 14:08:11 kernel: net_ratelimit: 167145 callbacks suppressed
Jan 31 14:08:16 kernel: net_ratelimit: 184738 callbacks suppressed
Jan 31 14:08:21 kernel: net_ratelimit: 174394 callbacks suppressed
Jan 31 14:08:26 kernel: net_ratelimit: 165252 callbacks suppressed
Jan 31 14:08:31 kernel: net_ratelimit: 170875 callbacks suppressed
Jan 31 14:08:36 kernel: net_ratelimit: 179260 callbacks suppressed
Jan 31 14:08:41 kernel: net_ratelimit: 178970 callbacks suppressed
Jan 31 14:08:56 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 0
Jan 31 14:08:56 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 1
Jan 31 14:09:00 kernel: wfd_registerdevice Successfully registered dev wds0.0.3 ifidx 1 wfd_idx 0
Jan 31 14:09:00 kernel: Register interface [wds0.0.3] MAC: b0:6e:bf:xx:xx:xx
Jan 31 14:09:00 kernel: wfd_registerdevice Successfully registered dev wds1.0.3 ifidx 1 wfd_idx 1
Jan 31 14:09:00 kernel: Register interface [wds1.0.3] MAC: b0:6e:bf:xx:xx:xx
Jan 31 14:09:06 kernel: net_ratelimit: 103843 callbacks suppressed
*** PC1 regains network connection

This is still happening with the new firmware. 20308 on both main and node. AiMesh enabled.

 

[arthurlien]

This is still happening with the new firmware. 20308 on both main and node. AiMesh enabled.

Still looking for it....

 

[arthurlien]

Arthur or anyone else,

Will the GUI "Firmware Upgrade", Auto Upgrade from "Beta Firmware" to the current 3.0.0.4.384_20308-gead790e or do I have to manually upgrade from Beta to Released Firmware first?

Specifically I have helped a friend setup 2 weeks ago the following scenario (Wired Backhaul):

AiMesh Router:

• RT-AC5300 Beta Firmware: 9.0.0.4_382_19612

AiMesh Nodes:

• RT-AC5300 Beta Firmware: 9.0.0.4_382_19612
• RT-AC86U Released Firmware: 3.0.0.4.384.10007

I think you can use "Auto Upgrade", such as check and upgrade.... (don't Click "Beta Firmware")

 

[LimJK]

I think you can use "Auto Upgrade", such as check and upgrade.... (don't Click "Beta Firmware")

Arthur,
Thank You for your reply

 

[RMerlin]

Unsticking this thread. Please upgrade to 384_20308, and move to this new thread for feedback.

https://www.snbforums.com/threads/o...4-384-20308-for-all-supported-products.44375/