ASUS RT-AC86U Firmware version 3.0.0.4.384.81039

[podkaracz]

First stable realase for years gg

 

[VANT]

First stable realase for years gg

really

 

[podkaracz]

really

Yes i used to have huge ping spikes and wifi spam with this dirty upgrade using web ui it seems like its not jumping as high anymore in tolerance range of 10ms~ not 200ms~ like before

 

[sdmf74]

Just did a factory reset on both routers, reconnected aimesh & everything was working great till I renamed my devices in network map
Anybody else had the gui lock up on them after changing your devices names in network map? or is yours just randomly freezing? (well not freezing but rather gui fails to load).

time for another reboot

another issue.. cant "apply" mac & ip address binding on network map screen under client status. But it works if you enable manual assignment in the LAN>DHCP SERVER screen

and for some reason the default device names are completely different than they have ever been, ie instead of recognizing my Yamaha RX-V3800 as CL-436 or something like usual its now showing as "accelerated concepts" not sure where it is getting that from.

 

[Ronald Schwerer]

First stable realase for years gg

Where's the sarcasm emoticon?

 

[OzarkEdge]

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

There is not much other WiFi near me but the excessive channel scanning and changing continues for no obvious reason, even after swapping router and node and re-installing (so not a hardware difference/defect). And the webUI locked up after adding the node. And the default Smart Connect rules appear mostly disabled. Edit: And... I've seen odd CPU behavior similar to that being discussed in this 68U 81039 thread.

Edit: I've downgraded to 45717, separate SSIDs, and fixed channels to wait for stable firmware... and stable Smart Connect which they seem to still be dicking around with.

For those confused, this thread is for 86U firmware.

OE

 

[follower]

Did ASUS put some kind of malicious codes into the firmware?
We will have a lot of issues forever unless ASUS removes useless features.

 

[OzarkEdge]

We will have a lot of issues forever unless ASUS removes useless features.

A better plan may be to move to another supplier when it's time to upgrade networking hardware.

OE

 

[sdmf74]

Did ASUS put some kind of malicious codes into the firmware?

The first clue should have been the "dea" in the firmware model #

 

[tallytr]

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.

We have a 3700sqft house and perfectly fine with one RT-AC86U, however, I had to move the modem+router in the upstairs office, that did the trick, great Wi-Fi even in the basement rooms now, no more need for Ai-Mesh....

 

[OzarkEdge]

We have a 3700sqft house and perfectly fine with one RT-AC86U, however, I had to move the modem+router in the upstairs office, that did the trick, great Wi-Fi even in the basement rooms now, no more need for Ai-Mesh....

Well done! Although it was probably unwanted work, simpler home networking is better.

OE

 

[tallytr]

Well done! Although it was probably unwanted work, simpler home networking is better.

OE

In our case most rooms have CAT 5 cable so it was super easy to plug the network modem in upstairs...
Also over the years running CAT 6 cable to most devices, PC's, printers, Apple TV via network switches... so mostly using Wi-Fi for phones and some other IOT stuff....

 

[VANT]

my 86u in idle

when i make this screen httpd hung up and now i had no gui

 

[Robert Iversen]

We have a 3700sqft house and perfectly fine with one RT-AC86U, however, I had to move the modem+router in the upstairs office, that did the trick, great Wi-Fi even in the basement rooms now, no more need for Ai-Mesh....

In a thin walled and unobstructed building that has perfect access to your Wi-Fi, this is great. In many scenarios and when I’d like to have full access to my 5GHz AC bands or want to plug in some media device to the router or nodes, my set up is very nice. As with any type of network, this is challenging and has its ups and downs.

ASUS has been really good for us, so besides this last release I’m happy.

 

[netmann]

direct download link for 68U but still version v1: https://dlcdnets.asus.com/pub/ASUS/wireless/RT-AC68U/FW_RT_AC68U_300438481039.zip
and for 86U updated v2: https://dlcdnets.asus.com/pub/ASUS/wireless/RT-AC86U/FW_RT_AC86U_300438481039_v2.zip

The question is why 81039 is available on Asus download website for RT-AC86U, but NOT for RT-AC68U! Perhaps the firmware was only meant for 86U and a mistake for the direct download for 68U!

 

[Grisu]

The question is why 81039 is available on Asus download website for RT-AC86U, but NOT for RT-AC68U! Perhaps the firmware was only meant for 86U and a mistake for the direct download for 68U!

Why do you think so???
If it is downloadable than they released it.
And it is always first on the download sever and later on visible on their pages, now you can even find it:
https://www.asus.com/de/Networking/RTAC68U/HelpDesk_BIOS/

 

[netmann]

Why do you think so???
If it is downloadable than they released it.
And it is always first on the download sever and later on visible on their pages, now you can even find it:
https://www.asus.com/de/Networking/RTAC68U/HelpDesk_BIOS/

The firmware still not listed on Asus USA site for 68U as of writing this post! It’s been 5 days!

 

[Grisu]

The firmware still not listed on Asus USA site for 68U as of writing this post! It’s been 5 days!

And ... where is your problem, you got the download link, it is listed in Taiwan, Australia, Italy, France, Germany and Singapore and many many more if you would search.
World will keep turning on this 5 day with weekend!

Never heard about patience?

And keep in mind there are some issues with this release, maybe US prevents their customers to use this buggy firmware!

 

[OzarkEdge]

And keep in mind there are some issues with this release, maybe US prevents their customers to use this buggy firmware!

Now there's a happy thought!

OE

 

[Jonathan Dunlap]

I've updated to my 86u latest firmware (3.0.0.4.384_81039-g21dea07), and I've noticed the memory usage is a lot higher (and the UI is slower). It's using 357mb of memory which is higher than I remember it. This is after a full factory reset and a hard power reboot. Most of the settings are at their default, except ip-v6 passthrough is enabled, QoS disabled, ai protection on.

Log:

May  5 05:05:14 kernel: klogd started: BusyBox v1.24.1 (2019-08-13 17:54:15 CST)
May  5 05:05:14 kernel: Linux version 4.1.27 (jenkins@asuswrt-build-server) (gcc version 5.3.0 (Buildroot 2016.02) ) #2 SMP PREEMPT Tue Aug 13 18:30:08 CST 2019
May  5 05:05:14 kernel: CPU: AArch64 Processor [420f1000] revision 0
May  5 05:05:14 kernel: Kernel command line: coherent_pool=1M cpuidle_sysfs_switch
...
...
Aug 26 15:33:48 miniupnpd[3891]: version 1.9 started
Aug 26 15:33:48 miniupnpd[3891]: HTTP listening on port 52203
Aug 26 15:33:48 miniupnpd[3891]: Listening for NAT-PMP/PCP traffic on port 5351
Aug 26 15:33:49 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth 48:D6:D5:06:1B:54, status: 0, reason: d11 RC reserved (0)
Aug 26 15:33:49 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc 48:D6:D5:06:1B:54, status: 0, reason: d11 RC reserved (0)
Aug 26 15:33:50 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 70:4F:57:D2:FA:5D, status: 0, reason: Class 3 frame received from nonassociated station (7)
Aug 26 15:33:51 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 70:4F:57:D2:FA:5D, status: 0, reason: d11 RC reserved (0)
Aug 26 15:33:51 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth5: Assoc 70:4F:57:D2:FA:5D, status: 0, reason: d11 RC reserved (0)
Aug 26 15:33:52 dhcp6 client: bound address 2605:e000:9fc0:4f:d8fb:ceec:4194:d8b4/128, prefix 2605:e000:1313:e28f::/64
Aug 26 15:33:56 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth6: Auth A0:99:9B:13:40:6D, status: 0, reason: d11 RC reserved (0)
Aug 26 15:33:56 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth6: Assoc A0:99:9B:13:40:6D, status: 0, reason: d11 RC reserved (0)
Aug 26 15:33:59 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 3C:28:6D:00:BF:A1, status: 0, reason: Class 3 frame received from nonassociated station (7)
Aug 26 15:33:59 wlceventd: WLCEVENTD wlceventd_proc_event(386): eth5: Deauth_ind 3C:28:6D:00:BF:A1, status: 0, reason: Class 3 frame received from nonassociated station (7)
Aug 26 15:34:01 wlceventd: WLCEVENTD wlceventd_proc_event(420): eth5: Auth 3C:28:6D:00:BF:A1, status: 0, reason: d11 RC reserved (0)
Aug 26 15:34:01 wlceventd: WLCEVENTD wlceventd_proc_event(449): eth5: Assoc 3C:28:6D:00:BF:A1, status: 0, reason: d11 RC reserved (0)
Aug 26 15:34:02 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc012484728 next ffffffc010bf4460 prev ffffffc010bf4460 rep_entry->list ffffffc010bf4460 next ffffffc012484728 prev ffffffc012484728
Aug 26 15:34:02 kernel: bcm_mcast_mld_add:833 mc_fdb->rep_list ffffffc012484728 next ffffffc010bf4620 prev ffffffc010bf4620 rep_entry->list ffffffc010bf4620 next ffffffc012484728 prev ffffffc012484728
Aug 26 15:34:09 rc_service: httpd 3679:notify_rc restart_firewall
Aug 26 15:34:09 miniupnpd[3891]: shutting down MiniUPnPd
Aug 26 15:34:09 modprobe: module ip6t_REJECT not found in modules.dep
Aug 26 15:34:09 modprobe: module ip6t_ROUTE not found in modules.dep
Aug 26 15:34:09 modprobe: module ip6t_LOG not found in modules.dep
Aug 26 15:34:09 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Aug 26 15:34:09 miniupnpd[4197]: version 1.9 started
Aug 26 15:34:09 miniupnpd[4197]: HTTP listening on port 43314
Aug 26 15:34:09 miniupnpd[4197]: Listening for NAT-PMP/PCP traffic on port 5351
Aug 26 15:34:13 rc_service: httpd 3679:notify_rc restart_firewall
Aug 26 15:34:13 miniupnpd[4197]: shutting down MiniUPnPd
Aug 26 15:34:13 modprobe: module ip6t_REJECT not found in modules.dep
Aug 26 15:34:13 modprobe: module ip6t_ROUTE not found in modules.dep
Aug 26 15:34:13 modprobe: module ip6t_LOG not found in modules.dep
Aug 26 15:34:13 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Aug 26 15:34:13 miniupnpd[4224]: version 1.9 started
Aug 26 15:34:13 miniupnpd[4224]: HTTP listening on port 38389
Aug 26 15:34:13 miniupnpd[4224]: Listening for NAT-PMP/PCP traffic on port 5351
Aug 26 15:34:17 rc_service: httpd 3679:notify_rc restart_firewall
Aug 26 15:34:17 miniupnpd[4224]: shutting down MiniUPnPd
Aug 26 15:34:17 modprobe: module ip6t_REJECT not found in modules.dep
Aug 26 15:34:17 modprobe: module ip6t_ROUTE not found in modules.dep
Aug 26 15:34:17 modprobe: module ip6t_LOG not found in modules.dep
Aug 26 15:34:17 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Aug 26 15:34:17 miniupnpd[4246]: version 1.9 started
Aug 26 15:34:17 miniupnpd[4246]: HTTP listening on port 56668
Aug 26 15:34:17 miniupnpd[4246]: Listening for NAT-PMP/PCP traffic on port 5351