[Release] Asuswrt-Merlin 384.14 (and 384.13_2) are now available

  • 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.
Status
Not open for further replies.

RMerlin

Asuswrt-Merlin dev
Asuswrt-Merlin 384.13_2 (RT-AC87U and RT-AC3200), and 384.14 (other models) are now available.

Jan 1st: 384.14_2 is available for the RT-AC68U, RTAC88U/3100/5300 and RT-AC86U, addressing a few issues specific to these models. Changes since 384.14:

Code:
  - FIXED: Missing cifs kernel module
  - FIXED: stubby was linked with OpenSSL 1.0 instead of 1.1
  - FIXED: some routers were reporting the Internet connection being
           disconnected.  If you were affected and you had flashed
           a customized bootloader, then please reflash your original
           bootloader, as your modded bootloader is invalid, and other
           potential issues may appear over time.
  - FIXED: Random traffic spikes logged in Traffic Monitor (regression
           from 384_81351)

The 384.13_2 release mostly focuses on fixes backported from 384.14. Since the 382 and 384 codebases are now too different, compiling these two older models with newer GPL code is not possible unless obtaining special binary components from Asus, which I was not able to do for 384.14.

The 384.14 release for other models focuses on GPL merges and fixes.

The highlights:
  • GPL updates: 384_6436 (RT-AX88U), 384_81351 (other models, with 384_81116 binary blobs used for the RT-AC88U/RT-AC3100), which contains Let's Encrypt fixes.
  • Added option to prevent automatic DoH upgrade by Firefox. By default this option will only prevent automatic upgrade if you use DNSFilter or DNSPrivacy (DNS-over-TLS). You can change it to always prevent the upgrade. Note that this option has no impact if you manually decide to enable DoH in Firefox, only for its automatic option currently only available in the US.
  • Updated components: miniupnpd 20190824, dnsmasq 2.80-95-g1aef66b, OpenSSL (1.0.2t/1.1.1d), curl (7.66), OpenVPN (2.4.8) and nano (4.4).
  • Made self-generated SSL certificate compliant with new IOS 13 and MacOS 10.15 requirements (reduced duration to two years, and added missing attribute)
  • Re-implemented the faketc script (which injects fq_codel support into Adaptive QoS) as a binary executable for better performance (reducing the chances of warning messages during QoS initialization if QoS took too long to initialize)
  • Enhancements to the IPv6 firewall webui (now accepts empty fields to denote "Any IP", and improved EUI-64 handling)
  • Re-added low nvram notification (was lost a few years ago in the move to 382)
  • A number of fixes to Let's Encrypt support
  • A number of misc fixes, please see the changelog for the complete list
Downloads are here.
Changelog is here.

Please keep posts focused on this specific release. Also note that I intend to lock this thread after a few weeks, once the release-specific issues have been handled, to avoid this thread devolving into a generic support discussion.
 
Last edited:

RMerlin

Asuswrt-Merlin dev
Reserved post.
 

Smokey613

Senior Member
Is there any benefit upgrading to 384.13_2 if I am running an RT-AC68U?
 

dave14305

Part of the Furniture
I was almost on my way up to bed. Now I've upgraded to 384.14. So far so good. Nervous about GPL 384_81351. But very happy to see this baby shipped! I think there's a hidden message that 12/13 is the release date for 14. 12/13->14. See? I'm tired -- I should be asleep.
Re-implemented the faketc script (which injects fq_codel support into Adaptive QoS) as a binary executable for better performance (reducing the chances of warning messages during QoS initialization if QoS took too long to initialize)
I would swear that the faketc is running blazing fast, but I realized that I won't see it under tcd in htop anymore because it no longer spawns a shell for each command, and the debug feature is not present in the new binary.

I did have to update my router name on the LAN page, as expected.
 

Morac

Senior Member
Updating my AC88U from 384.13 to 384.14 and so far so good. One thing I noticed is that it updated much faster than usual. I think it was done in under 2 minutes. Usually it’s at least 3.

Did ASUS optimize their update code in 384.13?

In any case I decided to do a power off reset after updating since I wanted to do anyway in a few weeks since I had one lockup after about 60 days after installing 384.13 and I was over that.
 

indark

Senior Member
qos does not work for AX88, was fine for the beta 3
assuming it will need asus to fix their GPL since it's same behavior as their latest official firmware?

I also need to manually set channel for 5Ghz to be able to see the 5Ghz for some of the client.
does not need to w/ the official firmware though.
it's an interesting behavior for AX88
 

Makaveli

Very Senior Member
Just upgraded that did seem alittle quicker than last time.

Everything is running great.
 

AndreiV

Very Senior Member
Asuswrt-Merlin 384.13_2 (RT-AC87U and RT-AC3200), and 384.14 (other models) are now available.
Flashed to AC3200 , no issues , working well, thank you Eric.

The 384.13_2 release mostly focuses on fixes backported from 384.14. Since the 382 and 384 codebases are now too different, compiling these two older models with newer GPL code is not possible unless obtaining special binary components from Asus, which I was not able to do for 384.14.
Not really expecting any new features or upgrades to newer code on this model , with your firmware it works perfectly , security updates would obviously be appreciated .
 

RMerlin

Asuswrt-Merlin dev
qos does not work for AX88, was fine for the beta 3
There has been zero code change between beta 3 and final release, changes were purely HTML/CSS tweaks on the webui.

Code:
[email protected]:~/amng$ git log 384.14-beta3-ax..384.14-ax
commit 7606e531c85a09c4369a652fc20ff8ac683ba0a3 (HEAD -> rtax88, tag: 384.14-ax, origin/rtax88)
Merge: 487221d66a cdb88358fe
Author: Eric Sauvageau <[email protected]>
Date:   Fri Dec 13 19:27:52 2019 -0500

    Merge branch 'master' into rtax88

commit cdb88358fe8af3e52cf774749fdc984871d95c05
Author: Eric Sauvageau <[email protected]>
Date:   Fri Dec 13 19:22:01 2019 -0500

    Bumped revision to 384.14 final

commit 57cfecda72e8e5d21a5c10e46c15fee01cb35631
Author: Eric Sauvageau <[email protected]>
Date:   Fri Dec 13 19:21:37 2019 -0500

    Updated documentation

commit 742e8cf6c216d16ce76e4e6ef8e1f9a6ff8922ac
Author: Eric Sauvageau <[email protected]>
Date:   Tue Dec 10 22:17:02 2019 -0500

    webui: right-align values on the QoS stats tables

commit 487221d66a0c7f1120909bb28656505d01d30165
Author: Eric Sauvageau <[email protected]>
Date:   Tue Dec 10 22:10:10 2019 -0500

    webui: there's no popup help for this item, so remove the anchor

commit 488bedbdcb3510f849fe91406fb5bbdcd993a28f (tag: 384.14-beta3)
Author: Eric Sauvageau <[email protected]>
Date:   Sat Dec 7 00:15:53 2019 -0500

    Updated documentation
 

Stardust

Regular Contributor
Upgraded from 384.13 without a problem.
Thanks for your work :)
 

indark

Senior Member
There has been zero code change between beta 3 and final release, changes were purely HTML/CSS tweaks on the webui.

Code:
[email protected]:~/amng$ git log 384.14-beta3-ax..384.14-ax
commit 7606e531c85a09c4369a652fc20ff8ac683ba0a3 (HEAD -> rtax88, tag: 384.14-ax, origin/rtax88)
Merge: 487221d66a cdb88358fe
Author: Eric Sauvageau <[email protected]>
Date:   Fri Dec 13 19:27:52 2019 -0500

    Merge branch 'master' into rtax88

commit cdb88358fe8af3e52cf774749fdc984871d95c05
Author: Eric Sauvageau <[email protected]>
Date:   Fri Dec 13 19:22:01 2019 -0500

    Bumped revision to 384.14 final

commit 57cfecda72e8e5d21a5c10e46c15fee01cb35631
Author: Eric Sauvageau <[email protected]>
Date:   Fri Dec 13 19:21:37 2019 -0500

    Updated documentation

commit 742e8cf6c216d16ce76e4e6ef8e1f9a6ff8922ac
Author: Eric Sauvageau <[email protected]>
Date:   Tue Dec 10 22:17:02 2019 -0500

    webui: right-align values on the QoS stats tables

commit 487221d66a0c7f1120909bb28656505d01d30165
Author: Eric Sauvageau <[email protected]>
Date:   Tue Dec 10 22:10:10 2019 -0500

    webui: there's no popup help for this item, so remove the anchor

commit 488bedbdcb3510f849fe91406fb5bbdcd993a28f (tag: 384.14-beta3)
Author: Eric Sauvageau <[email protected]>
Date:   Sat Dec 7 00:15:53 2019 -0500

    Updated documentation
was some weird glitch, I did couple factory reset (both hardware/software) before I commented :( thought it had to do w/ the new GPL. reflash again and now it's working properly. :)
 

SheikhSheikha

Regular Contributor
RT-AC5300 M&M Nuclear re-installation of 384.14 (I kept my other AC5300 on 384.13 for the moment)
Compared to 384.13 The WiFi signal strength remains significantly lower (as already noticed in Beta3) The values are: 8% lower on 5GHz-2, 7% lower on 5GHz-1 and 12% lower on 2.4GHz(!!).
 
Last edited:

Zastoff

Very Senior Member
Smooth update to 384.13_2 on RT-AC87u :)
Thanks RMerlin
 

octopus

Very Senior Member
Updated to 384.14 and working fine.
Uptime 0 days 0 hour(s) 22 minute(s) 5 seconds

Thank you Rmerlin!
 

XIII

Very Senior Member
Upgraded from 384.14 Beta 3 to the final version.

Still no remote HomeKit access (as with Beta 3), but this might be my/Apple’s fault.

Tips for fixing this?
 
Status
Not open for further replies.

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

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