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

[SheikhSheikha]

Upgrade to 384.16 on both routers. Smooth fast and stabile. The client disruption that I encountered in Beta3 disruption though continues. Still trying to find out if this is the VPN provider of the router but given the fact that both routers show different behavior (at random the log shows /usr/sbin/l2tpd[12420]: Too many retransmissions on tunnel (46298/12555); closing down) with no clear pattern.
It happens at different moments in both routers. I am more and more inclined to think it is on my router's side. Anyone a suggestion or am I a lone ranger with my L2TP client? (I changed nodes etc but that did not show any difference. Anyway Eric and team thank you for this update.

 

[Ltvscout]

I'm currently running 384.13 on my 68U. Should I do a factory reset after upgrading to 384.16?

 

[netware5]

Dirty flash from 384.15. No issues so far. Thanks @RMerlin!

 

[bughit]

It's in the changelog.

Chanegelog for a specific release does not mention the asus version unless it was updated. The asus merge sometimes does not happen for multiple releases.

 

[RMerlin]

how long does it normally take ?

Anywhere between 24 hours and 3 months. In short, there is no constants.

Site Survey doesn't report and map 160Mhz AC.

Tell that to Broadcom...

 

[RMerlin]

Chanegelog for a specific release does not mention the asus version unless it was updated. The asus merge sometimes does not happen for multiple releases.

The info is still in the changelog. I'm not going to bloat each individual changelogs with 10+ model specific entries, just read past entries, like you would do to see what previous things were also changed/fixed.

 

[Mutzli]

I'm currently running 384.13 on my 68U. Should I do a factory reset after upgrading to 384.16?

I wouldn't if you don't experience any issues or memory leaks after flashing the latest firmware.

 

[Asad Ali]

Chanegelog for a specific release does not mention the asus version unless it was updated. The asus merge sometimes does not happen for multiple releases.

Open/download the changelog file from here:

https://github.com/RMerl/asuswrt-merlin.ng/blob/master/Changelog-NG.txt

And then simply do a search for "GPL" and you have info for every GPL merge, Easy-Peasy.

 

[Stevens243]

Dirty flash from .15 FW. Did the Mesh Node first, then the router. No issues to report. Easy, clean and seamless. I had already updated AMTM to 3.1.6 and no conflicts on that end either.

 

[Deleted member 22229]

Just updated to 384.16 AX58U. Working good !!!

 

[kernol]

As always with release versions - stable and rock steady for all as per my signature - many thanks to the Maestro and the Alpha Beta testers.

 

[Jasso]

Upgraded to 384.16 now getting shed loads of these in system log, any ideas anyone?

dnsmasq(316): failed to send packet: Operation not permitted

 

[Billy Chaney]

Uploaded 384.16 20 hrs ago. All is good. No problems at all.

 

[DarkKnight75]

How's wifi performance on ac86u?
I'm still running 384.12 as I had issues with 384.14 and .15

 

[Makaveli]

How's wifi performance on ac86u?
I'm still running 384.12 as I had issues with 384.14 and .15

You will have to try it in your own environment to be sure.

what works well for someone else may not work for you due to that fact.

 

[JWoo]

Just updated to 384.16 AX58U. Working good !!!

Me too. RT-AX58U best router ever. @RMerlin best firmware ever.

 

[Thermaltake]

from .15 to .16 AC88U. Everything working fine so far.

 

[krgck]

No issues with AC88U, once again king delivers quality.

 

[mlippold]

Updated RT-AC5300 .15 to .16 dirty - No issues so far.

 

[Igor]

Who uses the USB 3.0 connector? Does the flash drive work with firmware 384.16?
ASUS RT-AC68U does not work.