Release Asuswrt-Merlin 386.7 is now available for all models

[dcballers]

For the first time ever, I am unable to update. Simply nothing happens when I click the Manual firmware update: Upload link. Usually there's a popup where I can select the file. Have tried soft and hard reboots multiple times. I'm on AC86U with 386.7 and trying to go to 386.7_2. I've had intermittent connectivity ever since updating to 386.7 last week and am eager to upgrade.
Any suggestions?

 

[paul0363]

For the first time ever, I am unable to update. Simply nothing happens when I click the Manual firmware update: Upload link. Usually there's a popup where I can select the file. Have tried soft and hard reboots multiple times. I'm on AC86U with 386.7 and trying to go to 386.7_2. I've had intermittent connectivity ever since updating to 386.7 last week and am eager to upgrade.
Any suggestions?

Try using rescue mode to upload new firmware:

https://www.asus.com/support/faq/1000814/

 

[RMerlin]

Usually there's a popup where I can select the file.

If the file selector does not happen then this is a browser issue, unrelated to the router. This is common if your browser's last selected file was on a network share that is no longer available. It can then take one or two minutes before the connection attempt times out, and the browser reverts to a default location.

 

[Conundrum1911]

Tried upgrading again from 386.5_2 to 386.7_2 and the same thing happened again -- A few hours post upgrade & reboot a bunch of lines saying failed to write /var/lib/msc/dnsmasq.leases due to lack of free space when there is a ton of space still free on the router.

Since it was a dirty upgrade, I've bit the bullet and wiped the JIFFS partition and reset the router to defaults, put back in my wifi, mac filters, static addresses, and port forwards. Fingers crossed it doesn't have issues again, but if it does I'm not sure what else to do but downgrade and keep it there.

 

[The PyroPath]

Had this issue not as WAN IP address (IPv4) but as IPv6 issue.
in 386 5 2 it is ok so I retrieved at first, but in latest test build 386 7 1 , works like a charm so far.
I would suggest whoever has any issue on AX88U, it is most likely to be resolved (IPv6 and WIFI mostly) in the latest test build.
In my experience, in 386 7 1 not needed any hard reset to maintain everything, but a simple reboot to the system made it.
A dirty upgrade is done and my system is up and running for about 48h so far, and it is alright.
Also, in 386 7 (alpha etc) I had VOIP adapter issues as well, which are resolved as well in 386 7 1 test build.
Truly recommending to update FW.

@The PyroPath

Oh balls, was really hoping 386.7_2 would fix the issue, but after 2 days and some hours...

Jul 27 22:03:52 watchdog: restart_firewall due DST time changed(1->0)
Jul 27 22:03:52 rc_service: watchdog 1790:notify_rc restart_firewall
Jul 27 22:03:52 rc_service: watchdog 1790:notify_rc restart_wan
Jul 27 22:03:52 rc_service: waitting "restart_firewall" via watchdog ...
Jul 27 22:03:52 firewall: apply rules error(2931)
Jul 27 22:03:52 firewall: apply rules error(2966)
Jul 27 22:03:52 services: apply rules error(18439)
Jul 27 22:03:52 firewall: apply rules error(4706)
Jul 27 22:03:53 miniupnpd[3387]: shutting down MiniUPnPd
Jul 27 22:03:57 dnsmasq-dhcp[5579]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jul 27 22:03:58 wan: finish adding multi routes
Jul 27 22:03:58 rc_service: udhcpc_wan 21967:notify_rc start_dnsmasq
Jul 27 22:03:58 rc_service: waitting "restart_wan" via watchdog ...
Jul 27 22:04:02 dropbear[22069]: Password auth succeeded for [sensored] from 192.168.0.115:38416
Jul 27 22:04:02 dropbear[22087]: Password auth succeeded for [sensored] from 192.168.0.115:38418
Jul 27 22:04:03 start_ddns: IP address, server and hostname have not changed since the last update.
Jul 27 22:04:12 BWDPI: fun bitmap = 4ff
Jul 27 22:04:12 kernel: CPU: 2 PID: 22128 Comm: cut Tainted: P           O    4.1.51 #2
Jul 27 22:04:12 kernel: Hardware name: Broadcom-v8A (DT)
Jul 27 22:04:12 kernel: task: ffffffc02b4f55c0 ti: ffffffc0257c8000 task.ti: ffffffc0257c8000
Jul 27 22:04:12 kernel: PC is at 0xf72ba5dc
Jul 27 22:04:12 kernel: LR is at 0x345a0
Jul 27 22:04:12 kernel: pc : [<00000000f72ba5dc>] lr : [<00000000000345a0>] pstate: 60070010
Jul 27 22:04:12 kernel: sp : 00000000ffa8d6fc
Jul 27 22:04:12 kernel: x12: 00000000f72ba5d0
Jul 27 22:04:12 kernel: x11: 000000000042a3f4 x10: 000000000042a3f4
Jul 27 22:04:12 kernel: x9 : 00000000000837a7 x8 : 000000000008a00c
Jul 27 22:04:12 A.QoS: qos_count=0, qos_check=0
Jul 27 22:04:12 kernel: x7 : 000000000000000b x6 : 00000000000837a7
Jul 27 22:04:12 kernel: x5 : 000000000042a394 x4 : 000000000042a384
Jul 27 22:04:12 kernel: x3 : 0000000000000000 x2 : 000000000042a394
Jul 27 22:04:12 kernel: x1 : 000000000042a384 x0 : fffffffffffffff2
Jul 27 22:04:15 services: apply rules error(18439)
Jul 27 22:04:15 firewall: apply rules error(4706)
Jul 27 22:04:15 kernel: CPU: 1 PID: 21967 Comm: udhcpc_wan Tainted: P           O    4.1.51 #2
Jul 27 22:04:15 kernel: Hardware name: Broadcom-v8A (DT)
Jul 27 22:04:15 kernel: task: ffffffc02f0d75c0 ti: ffffffc01b73c000 task.ti: ffffffc01b73c000
Jul 27 22:04:15 kernel: PC is at 0x146594
Jul 27 22:04:15 kernel: LR is at 0x147120
Jul 27 22:04:15 kernel: pc : [<0000000000146594>] lr : [<0000000000147120>] pstate: 60050010
Jul 27 22:04:15 kernel: sp : 00000000ffa83050
Jul 27 22:04:15 kernel: x12: 0000000000000000
Jul 27 22:04:15 kernel: x11: 00000000ffae8140 x10: 0000000000000000
Jul 27 22:04:15 kernel: x9 : 0000000000000000 x8 : 0000000000000000
Jul 27 22:04:15 kernel: x7 : 00000000ffae8240 x6 : 0000000000000001
Jul 27 22:04:15 kernel: x5 : 00000000f72b3ab8 x4 : 00000000ffa830a0
Jul 27 22:04:15 kernel: x3 : 0000000000000000 x2 : 00000000ffae809c
Jul 27 22:04:15 kernel: x1 : 000000000083e585 x0 : 0000000000187070
Jul 27 22:04:23 watchdog: restart_firewall due DST time changed(0->1)
Jul 27 22:04:23 rc_service: watchdog 1790:notify_rc restart_firewall
Jul 27 22:04:23 rc_service: watchdog 1790:notify_rc restart_wan
Jul 27 22:04:23 rc_service: waitting "restart_firewall" via watchdog ...
Jul 27 22:04:23 firewall: apply rules error(2931)
Jul 27 22:04:23 firewall: apply rules error(2966)
Jul 27 22:04:23 services: apply rules error(18439)
Jul 27 22:04:23 firewall: apply rules error(4706)
Jul 27 22:04:24 rc_service: watchdog 1790:notify_rc start_dnsmasq
Jul 27 22:04:24 rc_service: waitting "restart_wan" via watchdog ...
Jul 27 22:04:27 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 6A:96:0E:BF:AE:0B, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jul 27 22:04:27 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 6A:96:0E:BF:AE:0B, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jul 27 22:04:28 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 6A:96:0E:BF:AE:0B, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jul 27 22:04:29 wan: finish adding multi routes
Jul 27 22:04:29 rc_service: udhcpc_wan 22191:notify_rc start_dnsmasq
Jul 27 22:04:29 rc_service: waitting "restart_wan" via watchdog ...
Jul 27 22:04:34 start_ddns: IP address, server and hostname have not changed since the last update.
Jul 27 22:04:46 rc_service: udhcpc_wan 22191:notify_rc stop_samba
Jul 27 22:04:46 rc_service: udhcpc_wan 22191:notify_rc start_samba
Jul 27 22:04:46 rc_service: waitting "stop_samba" via udhcpc_wan ...
Jul 27 22:04:46 Samba_Server: smb daemon is stopped
Jul 27 22:04:47 dhcp_client: bound [sensored]/255.255.255.0 via [sensored] for 3600 seconds.
Jul 27 22:05:04 rc_service: watchdog 1790:notify_rc start_dnsmasq
Jul 27 22:05:09 wlceventd: wlceventd_proc_event(505): eth6: Auth E8:C1:D7:0B:FF:4F, status: Successful (0)
Jul 27 22:05:09 wlceventd: wlceventd_proc_event(515): eth6: ReAssoc E8:C1:D7:0B:FF:4F, status: Successful (0)
Jul 27 22:05:10 wlceventd: wlceventd_proc_event(505): wl0.1: Auth E8:68:E7:83:37:C9, status: Successful (0)
Jul 27 22:05:10 wlceventd: wlceventd_proc_event(534): wl0.1: Assoc E8:68:E7:83:37:C9, status: Successful (0)
Jul 27 22:05:11 dnsmasq-dhcp[22291]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jul 27 22:05:11 dnsmasq-dhcp[22291]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jul 27 22:05:11 dnsmasq-dhcp[22291]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jul 27 22:05:11 dnsmasq-dhcp[22291]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jul 27 22:05:11 dnsmasq-dhcp[22291]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jul 27 22:05:11 dnsmasq-dhcp[22291]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jul 27 22:05:14 dnsmasq-dhcp[22291]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)

AND

Jul 27 22:08:15 dropbear[8010]: Error forking: Cannot allocate memory
Jul 27 22:08:15 dropbear[8010]: Error forking: Cannot allocate memory
Jul 27 22:08:15 dropbear[8010]: Error forking: Cannot allocate memory
Jul 27 22:08:16 dropbear[8010]: Error forking: Cannot allocate memory
Jul 27 22:08:18 out of memory [1425]
Jul 27 22:08:18 out of memory [1425]

After this, everything goes to the crapper. Loops of above type of messages, lots of connections being dropped and re-associated, than dropped again, under "wlceventd" notices, more out of memory errors and restarts of firewall and dnsmasq and somewhere during this the WAN is dropped and disconnected. I think it's related to Home Assistant, but don't know if it's caused by a change in the firmware or Home Assistant or ASUSWRT integration...

 

[gbernard]

Upgraded to 386.7_2 from 386.7 on AX88U and now I'm receiving the "Setup Wizard" on every reboot since. First time ever experiencing this after an upgrade.

Same issue, also have just gone back to 386.5_2, had several dropouts with 386.7, first time ever any issues with merlin FW, RT-AX88U here.

 

[RMerlin]

Same issue, also have just gone back to 386.5_2, had several dropouts with 386.7, first time ever any issues with merlin FW, RT-AX88U here.

386.7_2 uses the same radio firmware as 386.5_2 on the RT-AX88U.

 

[New2This]

Did the dirty upgrade, No issues here, All wireless devices seem to be connected

 

[gbernard]

main reason is the setup wizard on every reboot.

 

[jfree23]

Dirty upgrade 386.7 to 386.7_2 does not work on my AX86U.

Router runs fine with 386.7, and FW upgrade process looks OK when started from GUI, but after “upload”, GUI shows only “please wait, applying action” forever. Router appears to go through normal upgrade process, reboots, LEDs all off then on OK, but when I restart GUI or ssh it shows still at 386.7. Upgrade did not happen.

I am running entware, swap file, scripts, and Ups Nut tools. USB flash drive for entware and swap. This is the primary node of a 2 node AIMesh, other node is AC86U and 386.7_2 flashed on that router no problem. Been running Asus and Merlin for quite a while, using GUI and ssh, amtm, entware.

I have tried to flash many times, different browsers, different PCs, checked Sha, redownloaded, “safely removed” USB, reboot before, after, etc, but result is same: all is well, but FW is still 386.7, no change. Read and followed other suggested procedures from this forum, no luck.

Only unusual thing I see in syslog is rc_service stop_upgrade. Does this mean current code is aborting the upgrade? If so, why? I see no indication of the cause, but I may be missing it.

Jul 27 15:22:50 dnsmasq-dhcp[10350]: DHCPACK(br0) 192.168.1.38 00:05:cd:21:7f:de AVR-FR
Jul 27 15:22:51 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 18:74:2E:89:6F:40, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jul 27 15:22:51 hostapd: eth7: STA 18:74:2e:89:6f:40 IEEE 802.11: disassociated
Jul 27 15:23:00 uiDivStats: Entware not found, sleeping for 10s (attempt 7 of 10)
Jul 27 15:23:00 spdMerlin: Entware not found, sleeping for 10s (attempt 7 of 10)
Jul 27 15:23:06 wlceventd: wlceventd_proc_event(505): eth6: Auth 18:74:2E:89:6F:40, status: Successful (0)
Jul 27 15:23:06 hostapd: eth6: STA 18:74:2e:89:6f:40 IEEE 802.11: associated
Jul 27 15:23:06 wlceventd: wlceventd_proc_event(534): eth6: Assoc 18:74:2E:89:6F:40, status: Successful (0)
Jul 27 15:23:06 hostapd: eth6: STA 18:74:2e:89:6f:40 RADIUS: starting accounting session 857BB63FD5E828A4
Jul 27 15:23:06 hostapd: eth6: STA 18:74:2e:89:6f:40 WPA: pairwise key handshake completed (RSN)
Jul 27 15:23:06 dnsmasq-dhcp[10350]: DHCPREQUEST(br0) 192.168.1.134 18:74:2e:89:6f:40
Jul 27 15:23:06 dnsmasq-dhcp[10350]: DHCPACK(br0) 192.168.1.134 18:74:2e:89:6f:40 amazon-a18b871b6
Jul 27 15:23:09 dnsmasq-dhcp[10350]: SLAAC-CONFIRM(br0) 2600:6c64:507f:db3b:1a74:2eff:fe89:6f40 amazon-a18b871b6
Jul 27 15:23:10 uiDivStats: Entware not found, sleeping for 10s (attempt 8 of 10)
Jul 27 15:23:10 spdMerlin: Entware not found, sleeping for 10s (attempt 8 of 10)
Jul 27 15:23:10 rc_service: httpd 1599:notify_rc stop_upgrade
Jul 27 15:23:10 custom_script: Running /jffs/scripts/service-event (args: stop upgrade)
Jul 27 15:23:10 usb: USB is ejected
Jul 27 15:23:11 BWDPI: force to flush flowcache entries
Jul 27 15:23:12 kernel: IDPfw: Exit IDPfw
Jul 27 15:23:12 kernel: mod epilog takes 0 jiffies
Jul 27 15:23:12 kernel: IDPfw: Exit IDPfw
Jul 27 15:23:12 kernel: Exit chrdev /dev/idpfw with major 191
Jul 27 15:23:12 kernel: Exit chrdev /dev/idp with major 190
Jul 27 15:23:12 BWDPI: rollback fc
Jul 27 15:23:12 WEBDAV_Server: daemon is stopped
Jul 27 15:23:12 WEBDAV_Server: arpping daemon is stopped
Jul 27 15:23:12 iTunes: daemon is stopped
Jul 27 15:23:12 FTP_Server: daemon is stopped
Jul 27 15:23:12 Samba_Server: smb daemon is stopped
Jul 27 15:23:12 Timemachine: daemon is stopped
Jul 27 15:23:12 WEBDAV_Server: daemon is stopped

Any suggestions of what to look at, look for, or try? I really don’t want to have to do factory reset and set up from scratch again, especially since 386.7 seems to work fine.



Thanks!

 

[Morris]

386.7 --> 386.7_2

 

[eibgrad]

Any suggestions of what to look at, look for, or try? I really don’t want to have to do factory reset and set up from scratch again, especially since 386.7 seems to work fine.

I thought the primary benefit was for those having wireless issues moving from 386.5_2 to 386.7. Seems pointless to upgrade to 386.7_2 when 386.7 works fines. Some of you guys need to stop chasing upgrades.

 

[vlord]

I run an internal hardwired speedtest server and updating to 386.7_2 on my RT-AX86U led to significantly decreased uploads speeds and lower download consistent over many iterations of testing. I reverted back to 386.7_0 and like magic, speeds significantly increased. I pin my 5G to a specific channel and nothing else changed including the location of the test client.

 

[DannyZR]

For those that have updated from 386.7 to 386.7_2 have you noticed any improvements to overall WiFi speeds on 5GHz?
I was having a 5GHz dropout issue with my RT-AX68Us that are set up as APs alongside my AX86U. Flashed all of them to 386.7 and the network has been pretty stable but I have noticed lower speeds on 5GHz. Before I could get around 800-900mpbs when in the same room as the router, but now that's gone down to 600-700mpbs.

I have seen people in other threads talk about how the latest official Asus firmware has increased speeds over 386.7 for AX86U users.

Router Performance of RT-AX86U - 386.7 vs latest stock

tldr; Is anyone able to see router speedtests on the AX86U (386.7) >1gbps? And if so, any tips/suggestions? Hey everyone, I know I’ve seen some posts with questions about speed tests/router performance. But haven’t seen one that seems to get at the behavior I am seeing. I have a 1.4 gbps...

www.snbforums.com

 

[jfree23]

I thought the primary benefit was for those having wireless issues moving from 386.5_2 to 386.7. Seems pointless to upgrade to 386.7_2 when 386.7 works fines. Some of guys need to stop chasing upgrades.

Right, thanks anyway, I'm OK with 386.7, but if there is something wrong in my setup or environment that prevents upgrades I'd rather find and fix now. Sure I can wait and see what happens with 386.8, 386.9. or 386.10....

 

[Dedel66]

I thought the primary benefit was for those having wireless issues moving from 386.5_2 to 386.7. Seems pointless to upgrade to 386.7_2 when 386.7 works fines. Some of guys need to stop chasing upgrades.

I agree with you. But maybe the yellow blinking upgrade sign could be removed? I think that annoying blinking sign pushes many guys to an update that would not be necessary.

 

[RMerlin]

I think that annoying blinking sign pushes many guys to an update that would not be necessary.

People running outdated firmware that is getting compromised by malware and joining botnets are far more annoying.

A router is a critical piece of network security, and should be kept up-to-date.

 

[Dedel66]

People running outdated firmware that is getting compromised by malware and joining botnets are far more annoying.

A router is a critical piece of network security, and should be kept up-to-date.

I totally agree! But in my opinion this blinking sign should be there if there are security reasons and not for every "small update".

 

[RMerlin]

I totally agree! But in my opinion this blinking sign should be there if there are security reasons and not for every "small update".

You can disable the automatic firmware check in that case, but you'll be on your own to determine when new firmwares are available, and whether you feel necessary to update or not.

It's not as if I released a new firmware every week. My general release schedule is a new firmware every 2-3 months, with possibly one minor update 2-3 weeks later containing fixes for issues detected after release. That release was pushed to all models because it also contains various fixes for these models, it's not just a wireless driver change for a few select models.

merlin@ubuntu-dev:~/amng$ git log --oneline 386.7..386.7_2
021766bdf9 (tag: 386.7_2) Bumped revision to 386.7_2
46e3fb0bb2 Updated documentation
5c92f17bb6 webui: always show form buttons on OpenVPN server page; always fill up user list so applying won't error out
cbedbbd5b0 Updated documentation
c650c57d2d HND5.02ax: revert RT-AX88U and GT-AX11000 wireless firmware to previous version
c8d0c5e6ca webui: hide apply buttons when disabling OpenVPN server instance
dedf2906e7 libovpn: refresh ovpn client routing tables when stopping/starting an ovpn server
64dd3fdbf6 HND5.02L07p2: backport updated RT-AX86U wireless driver from upstream
fa48db53f2 webui: reword description for DNS rebind protection
60a42db71e libovpn: fix parsing of pidof result in watchdog script
ba308d43f5 Updated documentation
96b6f3df59 openssl: updated to 1.1.1q
d1340bd88e rc: dnsfilter: only filter FORWARD (remote) servers in IPv6
73cc5fd97a rc: allow IPv6 traffic through wireless guest networks
5a736a71c2 rc: query an IPv6 prefix of 0 (auto) rather than hardcoding it to 64 as default
33f0ed6ac4 rc: dnsfilter: workaround for IPv6 DNAT to router causing hw csum errors; a few other minor fixes
5812150656 rc: remove accidentally included patch file
03c7224a00 Merge pull request #818 from AdorableJiang/fix_JST
2621025767 openssl: updated to 1.1.1p
eddf5e9f42 dropbear: specify DEFAULT_ROOT_PATH that matches DEFAULT_PATH
ba5b23bffb Bump revision to 386.7_1
562861dde6 fix `JST` time zone error

 

[Dedel66]

Maybe I found another issue:
If I turn Networkmonitoring off my connection is stable shown as "connected" at Network Map Overview.

If I turn monitoring on either "DNS Query" or "Ping" or both, the Internetstatus at Network Map Overview toggles sometimes from "connected" to "disconnected" and back, though it is stable all time.

Somebodyelse realized this behavior?

Was NOT caused by new 386.7_2 !!!
Had a faulty cable to nas, that works as DNS....