[Release] Asuswrt-Merlin 384.16 (and 384.13_6) are now available

[AntonK]

You will need to do a factory default reset afterward. Latest Asus firmware now encrypts the user password, so my firmware won't be able to handle the encrypted password that will be present in nvram.

Hi RMerlin. I was able to upgrade without issue as I haven't run stock firmware in quite some time. In the future, should you incorporate the latest 3.0.0.4.384.81790 GPL into your firmware, would the upgrade be seamless? Or do you expect there would be hoops to jump through?

Thanks,
Anton

 

[whitey019]

RT-AC86U doin fine!

 

[motox22a]

Total "cherry" NOOB here (Upgrade for first time)...
Wanted to try flashing my newly acquired RT-AC86u across the network (wired) upgrade 384.15>384.16.
Safely removed Disk drive/rebooted/flashed.
Hooked up drive again and rebooted once more for good measure.
All looking good. Just did my other "backup" RT-AC86u as well.

 

[cmillar6]

Since the upgrade to 384.16 on my AC88u I've noticed this flooding my syslog, any idea what the cause is?

Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:21 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:22 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:22 dnsmasq[323]: failed to send packet: Operation not permitted
Apr 5 20:00:22 dnsmasq[323]: failed to send packet: Operation not permitted

 

[distilled]

Dirty flashed 86u with 68u mesh node, upgrading from beta3. Everything is hunky dory.

 

[QuikSilver]

Another smooth upgrade from beta3 for my 86u, Thanks!

 

[SomeWhereOverTheRainBow]

Great job @RMerlin for another awesome release.

 

[Gar]

Great job @RMerlin for another awesome release.

Same here

 

[barkmann]

ran into trouble enabling dual wan after a clean .16 upgrade on my ac86u. Simply would not connect on primary, reporting dhcp issues. Using ethernet port4 as primary. Went back to 15 and all was well again. cheers

 

[SomeWhereOverTheRainBow]

On my RT-AX88U, my connection speed improved overall with beta 3 and have held with the final release.

 

[Deleted member 62525]

Trying to upgrade RT86U from 384.15 to latest and tried twice but get the same error

 

[SomeWhereOverTheRainBow]

Trying to upgrade RT86U from 384.15 to latest and tried twice but get the same error

try re-downloading the file, then upload it.

 

[Deleted member 62525]

Trying to upgrade RT86U from 384.15 to latest and tried twice but get the same error

What I had to do is unplug the USB, reboot and then did the upgrade. This worked for me.

 

[SomeWhereOverTheRainBow]

What I had to do is unplug the USB, reboot and then did the upgrade. This worked for me.

The notorious mounted USB hang. I un-mount and disable jffs before running update for safe measure.

 

[tului]

Any pressing security patches since .16b3? Can't really immediately go to upgrade unless some massive hole exists.

 

[SomeWhereOverTheRainBow]

Any pressing security patches since .16b3? Can't really immediately go to upgrade unless some massive hole exists.

- FIXED: CVE-2020-8597 security issue.

for more info, read
https://access.redhat.com/security/cve/cve-2020-8597

The impact level is ranked,

This rating is given to flaws that can easily compromise the confidentiality, integrity, or availability of resources. These are the types of vulnerabilities that allow local users to gain privileges, allow unauthenticated remote users to view resources that should otherwise be protected by authentication, allow authenticated remote users to execute arbitrary code, or allow remote users to cause a denial of service.

 

[eclp]

Smooth update to AX88U and AiMesh-AX58U.

This constant message remains in the syslog and regularly:

kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not

 

[pablo11]

You will need to do a factory default reset afterward. Latest Asus firmware now encrypts the user password, so my firmware won't be able to handle the encrypted password that will be present in nvram.

Yep I completed the flash a few hours ago. All good.
Just been too busy to reply.
I noticed that the password was unusable so I reset it - just as you said.

Thanks mate.

Sent from my BLA-L29 using Tapatalk

 

[heysoundude]

Can you post a screen shot?

Nah, it’s been done already. Have a look around on the alpha thread.


Sent from my iPhone using Tapatalk

 

[RMerlin]

@RMerlin Is it possible to tell from the source what asus gpl release your release is based on for a given model?

If not, would you consider adding something like that? AFAICT currently to find out you have to scroll through prior release notes looking for the latest a gpl update entry for a given model.

It's in the changelog.

Sent from my SM-T720 using Tapatalk