ASUS RT-AC86U Firmware version 3.0.0.4.384.81039

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

netmann

Occasional Visitor
Can I save my current settings and restore it after the firmware upgrade and a god-forbidden factory default reset?

I only have one RT-AC68U.
 

wouterv

Very Senior Member
V1 version:
RT-AC68U_3.0.0.4_384_81039-g21dea07.trx
41044 KB

V2 version:
RT-AC86U_3.0.0.4_384_81039-g21dea07_cferom_ubi.w
68993 KB

I suggest it is safer to wait a while and stay with 3.0.0.4.384.45717.

[EDIT]
I am confused with 86 and 68 :mad:
 
Last edited:

LimJK

Senior Member
Hi,

AiMesh Router: RT-AC5300 (Merlin 384.13)
+ 2 x AiMesh Nodes: RT-AC86U (3.0.0.4.384_81039)
+ Backhaul Ethernet Connection

So far things seem to be working as expected for about 2 days :)

Edit: By the way iOS ASUS Router App Version 1.0.0.5.5 is working for me
 
Last edited:

OzarkEdge

Part of the Furniture
Here is the initial auto channel scanning logged so far in roughly 15 hours:

Aug 22 19:11:17 acsd: selected channel spec: 0x1003 (3)
Aug 22 19:11:17 acsd: Adjusted channel spec: 0x1003 (3)
Aug 22 19:11:17 acsd: selected channel spec: 0x1003 (3)
Aug 22 19:11:17 acsd: eth5: NONACSD channel switching to channel spec: 0x1003 (3)

Aug 22 19:13:17 acsd: selected channel spec: 0x1002 (2)
Aug 22 19:13:17 acsd: Adjusted channel spec: 0x1002 (2)
Aug 22 19:13:17 acsd: selected channel spec: 0x1002 (2)
Aug 22 19:13:17 acsd: acs_set_chspec: 0x1002 (2) for reason APCS_INIT

Aug 22 19:13:18 acsd: selected channel spec: 0xe29b (157/80)
Aug 22 19:13:18 acsd: Adjusted channel spec: 0xe29b (157/80)
Aug 22 19:13:18 acsd: selected channel spec: 0xe29b (157/80)
Aug 22 19:13:18 acsd: acs_set_chspec: 0xe29b (157/80) for reason APCS_INIT

Aug 22 21:21:08 acsd: selected channel spec: 0xe02a (36/80)
Aug 22 21:21:08 acsd: Adjusted channel spec: 0xe02a (36/80)
Aug 22 21:21:08 acsd: selected channel spec: 0xe02a (36/80)
Aug 22 21:21:10 acsd: eth6: NONACSD channel switching to channel spec: 0xe02a (36/80)

Aug 22 23:01:26 acsd: selected channel spec: 0x100b (11)
Aug 22 23:01:26 acsd: Adjusted channel spec: 0x100b (11)
Aug 22 23:01:26 acsd: selected channel spec: 0x100b (11)
Aug 22 23:01:26 acsd: eth5: NONACSD channel switching to channel spec: 0x100b (11)

Aug 22 23:39:19 acsd: selected channel spec: 0xe09b (149/80)
Aug 22 23:39:19 acsd: Adjusted channel spec: 0xe09b (149/80)
Aug 22 23:39:19 acsd: selected channel spec: 0xe09b (149/80)
Aug 22 23:39:19 acsd: eth6: NONACSD channel switching to channel spec: 0xe09b (149/80)

Aug 22 23:40:52 acsd: selected channel spec: 0xe22a (44/80)
Aug 22 23:40:52 acsd: Adjusted channel spec: 0xe22a (44/80)
Aug 22 23:40:52 acsd: selected channel spec: 0xe22a (44/80)
Aug 22 23:40:52 acsd: eth6: NONACSD channel switching to channel spec: 0xe22a (44/80)

Aug 22 23:42:51 acsd: selected channel spec: 0xe09b (149/80)
Aug 22 23:42:51 acsd: Adjusted channel spec: 0xe09b (149/80)
Aug 22 23:42:51 acsd: selected channel spec: 0xe09b (149/80)
Aug 22 23:42:53 acsd: eth6: NONACSD channel switching to channel spec: 0xe09b (149/80)

Aug 22 23:44:04 acsd: selected channel spec: 0xe22a (44/80)
Aug 22 23:44:04 acsd: Adjusted channel spec: 0xe22a (44/80)
Aug 22 23:44:04 acsd: selected channel spec: 0xe22a (44/80)
Aug 22 23:44:04 acsd: eth6: NONACSD channel switching to channel spec: 0xe22a (44/80)

Aug 23 02:29:33 acsd: selected channel spec: 0xe09b (149/80)
Aug 23 02:29:33 acsd: Adjusted channel spec: 0xe09b (149/80)
Aug 23 02:29:33 acsd: selected channel spec: 0xe09b (149/80)
Aug 23 02:29:36 acsd: eth6: NONACSD channel switching to channel spec: 0xe09b (149/80)

Aug 23 09:59:53 acsd: selected channel spec: 0x1001 (1)
Aug 23 09:59:53 acsd: Adjusted channel spec: 0x1001 (1)
Aug 23 09:59:53 acsd: selected channel spec: 0x1001 (1)
Aug 23 09:59:55 acsd: eth5: NONACSD channel switching to channel spec: 0x1001 (1)

Aug 23 10:30:53 acsd: selected channel spec: 0x1003 (3)
Aug 23 10:30:53 acsd: Adjusted channel spec: 0x1003 (3)
Aug 23 10:30:53 acsd: selected channel spec: 0x1003 (3)
Aug 23 10:30:54 acsd: eth5: NONACSD channel switching to channel spec: 0x1003 (3)


So, currently on channels 3 and 149 as reported in the Wireless Log.

I (finally) realized I had to disable the experimental setting 'Use channel width' in WiFi Analyzer Classic to display the correct 5.0 GHz channel.

OE
Channel scanning continues... does not seem happy to stay put.

Also noticed this in log:

Aug 24 04:36:17 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6398)]period_retry = 0
Aug 24 04:36:18 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6426)]retrieve firmware information
Aug 24 04:36:18 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6440)]no need to upgrade firmware
Aug 24 04:36:47 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6398)]period_retry = 1
Aug 24 04:36:48 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6426)]retrieve firmware information
Aug 24 04:36:48 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6440)]no need to upgrade firmware
Aug 24 04:37:17 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6398)]period_retry = 2
Aug 24 04:37:21 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6426)]retrieve firmware information
Aug 24 04:37:21 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6440)]no need to upgrade firmware

Firmware check seems anxious to find an upgrade!

OE
 

netmann

Occasional Visitor
V1 version:
RT-AC68U_3.0.0.4_384_81039-g21dea07.trx
41044 KB

V2 version:
RT-AC86U_3.0.0.4_384_81039-g21dea07_cferom_ubi.w
68993 KB

I suggest it is safer to wait a while and stay with 3.0.0.4.384.45717.

[EDIT]
I am confused with 86 and 68 :mad:
Also, notice the file size difference...
 

Robert Iversen

New Around Here
I run a 3 node AIMesh with AC86U as the main and two AC68U nodes connected by Ethernet cables. Since updating with this firmware release, I am unable to access the web GUI or connect via the mobile app after about an hour. A power cycle of the main router brings it back and I'm good for about another hour... Network traffic is still routing as expected.
This is the same issue that I experienced. I reset all of my routers to factor default after they were upgraded and reconfigured my entire router configuration and then added 2 other routers as nodes that were also reset to factory original settings. Thinking that it might be from an IP conflict, I set the IP addresses as 192.168.1.1 for the router, 192.168.2.1 for Node 1 when a router and before adding as Node 1, and 192.168.3.1 for Node 2 when a router and before adding as Node 2.

I experienced all of the same things. Two routers were manufactured in 2018 and 1 in 2019. I am not sure if it is hardware related because others do not appear to have similar issues.

I can confirm one thing, though: if I turn off my 2 additional Nodes (1 & 2) when setup with the new software, I had no issues with the router at all as a simple router. For me, it appears to be related to the AiMesh.

Once I downgraded the firmware, it was fine. I reported it to Asus to let them know.

For those asking if I reset my router, I did a full factory reset, which I believe will undo everything. I had to reset every detail and there was nothing in any of the logs. Unless there is a factory reset overlooks some saved data, then I am pretty sure I followed that.
 

Robert Iversen

New Around Here
If you have not done so, I would upgrade, webUI factory default reset w/initialize all units, reconfigure from scratch, and cycle power all units. Then consider reporting anything not working right.

OE
I did that as part of my steps... resetting each router separately when they were initially in the router configuration. I then did that a 2nd time and changed their IP addresses (LAN IP) to ensure that it was some IP conflict thing... which I imagine an AiMesh network would handle quite well if they have 2 exact same routers setup as AiMesh.

And to add... I did software and then physical recycles to ensure a system and then forced restart.
 

Robert Iversen

New Around Here
i upload this fw to my 86u and first impresion is ... slow....very slow, dramaticly slow. I added node, and after few moments node is gone, but is visible in wifi log. After router restart node is back to gui.
This was exactly my experience and why I after 2 to 3 hours of factors resets, restarting via the software and physically, changing the LAN IP, and running as only router, with 1 node, and then with 2 nodes, I manually re-installed 3.0.0.4.384.45717 back on each router and it is amazing zipping and responsive for the entire network... is there any way to run any shell script to do a full memory purge (i.e. garbage collection 'gc()') in this software that I may have overlooked?
 

netmann

Occasional Visitor
“I can confirm one thing, though. If I turn off my 2 Nodes when setup with the new software, I had no issues with router at all. It appears to be related to the AiMesh.”

This is one reason I am not using AiMesh. Actually I don’t need it. My 68U router signal is good in the most remote location of my house.
 

Robert Iversen

New Around Here
I like my RT-AC86U router and it has as good coverage, if not better, than my AC3100 router that I gave my son. But we have a large 2 story building with 3 AppleTVs, 4 Amazon FireSticks, 5 smart phones, 2 iPad/notepads, 2-4 of simultaneous Netflix streams, 2 Hulu streams, Xbox one, Nintendo switch, 15 smart devices/hubs, 4 computers, 9 security cameras, a smart home alarm system, smart garage door, a smart sprinkler, and a few other things. 1 router will not reach that or support all of that. LOL.

... it did B.C. But not now. B.C. = before children
 

netmann

Occasional Visitor
I like my RT-AC86U router and it has as good coverage, if not better, than my AC3100 router that I gave my son. But we have a large 2 story building with 3 AppleTVs, 4 Amazon FireSticks, 5 smart phones, 2 iPad/notepads, 2-4 of simultaneous Netflix streams, 2 Hulu streams, Xbox one, Nintendo switch, 15 smart devices/hubs, 4 computers, 9 security cameras, a smart home alarm system, smart garage door, a smart sprinkler, and a few other things. 1 router will not reach that or support all of that. LOL.

... it did B.C. But not now. B.C. = before children
I got you Robert. My house is tiny only 1135 square feet!
 

Robert Iversen

New Around Here
We moved recently from a 1420 sq ft home to a 3000 sq ft home, so my router needed a kick. I did access points, but they did not switch reliably for our phones and other mobile things. This is a frustration for me and why I am using AiMesh... though I wish I could control what WiFi signal to use on my smart phone over the router handling it. Also, it is hard when one node may lose power or a smart device or camera is power recycled, to have it connect to the closest node to ensure the best signal... that is frustrating.
 

sdmf74

Regular Contributor
V1 version:
RT-AC68U_3.0.0.4_384_81039-g21dea07.trx
41044 KB

V2 version:
RT-AC86U_3.0.0.4_384_81039-g21dea07_cferom_ubi.w
68993 KB

I suggest it is safer to wait a while and stay with 3.0.0.4.384.45717.

[EDIT]
I am confused with 86 and 68 :mad:
I am confused also. Is the firmware with the smaller file size for the 68u (and one with larger file size for the 86u)?

Cause Aimesh was telling me that both my 68u & 86u had available firmware updates so I downloaded the 3.0.0.4_384_81039 V2 manually & flashed it to both my 86u router & 68u node!
But when I go to asus downloads page for the 68u it doesnt show any firmware updates since 5/13/2019
 

organshifter

Regular Contributor
I am confused also. Is the firmware with the smaller file size for the 68u (and one with larger file size for the 86u)?

Cause Aimesh was telling me that both my 68u & 86u had available firmware updates so I downloaded the 3.0.0.4_384_81039 V2 manually & flashed it to both my 86u router & 68u node!
But when I go to asus downloads page for the 68u it doesnt show any firmware updates since 5/13/2019
The RT-AC68U and RT-AC86U do not share the same firmware. Each model uses different file formats. While I've never tried myself, I do not believe the firmware files are interchangeable between the two.

RT-AC86U: File format: .W
RT-AC68U: File format: .TRX

Also, as far as I'm aware, the RT-AC68U's newest firmware (RT-AC68U_3.0.0.4_384_81039-g21dea07.trx) is only available through the router's internal configuration page right now. Asus's website hasn't updated yet. With your AiMesh setup, navigating to Administration>Firmware Upgrade (Tab), and checking for an update will find the latest firmware for each model respectively.
 

sdmf74

Regular Contributor
Yeah I already went ahead and reflashed Version 3.0.0.4.384.45717 back to my 68u node then let aimesh check for updates and flashed the new firmware through the gui this time.
However Ive been having the same issue as everyone else. The gui works for a while the it wont wont load, reboot router rinse & repeat (happens again)! Hopefully they update these firmwares with working versions soon. Probably a good time to switch back to merlin.

Another strange thing I noticed is all the smart connect settings are disabled on the new firmware, why would they do that?

 
Last edited:

Sign Up For SNBForums Daily Digest

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