Release Asuswrt-Merlin 386.12 is now available for AC models

[RMerlin]

Asuswrt-Merlin 386.12 is now available for all supported AC models

Nov 21st: 386.12_4 is now available. This resolves a crash related to OpenVPN 2.6.7.

386.12_4 (21-Nov-2023)
  - UPDATED: openvpn to 2.6.8 (fixes a crash introduced in 2.6.7)

Nov 12th:: 386.12_2 is now available. This resolves the constant dcd crashes.

386.12_2 (12-Nov-2023)
  - UPDATED: openssl to 1.1.1w.
  - UPDATED: curl to 8.4.0.
  - UPDATED: openvpn to 2.6.7.
  - FIXED: WPS not working on SDK6/SDK7 devices (affecting
           RT-AC68U and RT-AC88U/3100/5300)
  - FIXED: dcd constantly crashing (updated Trend Micro
           components)

Changes since 386.11:

386.12 (4-Sept-2023)
  - UPDATED: Merged with GPL 386_51997.
  - UPDATED: curl to 8.1.2.
  - UPDATED: OpenVPN to 2.6.6.
  - UPDATED: openssl to 1.1.1u.
  - UPDATED: tor to 0.4.7.13.
  - CHANGED: FTP server will now only support strong ciphers
             in TLS mode.
  - FIXED: QOS Classification showing no Upload data on some
           WAN configurations.
  - FIXED: Radio temperature graphs weren't updating
  - FIXED: nvram usage reported on Sysinfo page was inaccurate
           as it included JFFS stored values.

Downloads are here.
Changelog is here.

 

[RMerlin]

Reserved post.

 

[BlackIce]

Asuswrt-Merlin 386.12 is now available for all supported AC models

Changes since 386.11:

386.12 (4-Sept-2023)
  - UPDATED: Merged with GPL 386_51997.
  - UPDATED: curl to 8.1.2.
  - UPDATED: OpenVPN to 2.6.6.
  - UPDATED: openssl to 1.1.1u.
  - UPDATED: tor to 0.4.7.13.
  - CHANGED: FTP server will now only support strong ciphers
             in TLS mode.
  - FIXED: QOS Classification showing no Upload data on some
           WAN configurations.
  - FIXED: Radio temperature graphs weren't updating
  - FIXED: nvram usage reported on Sysinfo page was inaccurate
           as it included JFFS stored values.

Downloads are here.
Changelog is here.

Installed without issue AND Custom Device Icons working!! Thankyou Merlin for fixing that.

 

[jeff3820]

Upgraded RT-AC86U from 386.11 to 386.12 without any issues. All working well.

 

[Tomo]

Dirty upgrade from .11 on main router (ac86u) and on the node (ac68u), all perfect !

 

[Wanabo]

Upgraded RT-AC88U (mesh master) and a RT-AC86U_RT-AC2900 (slave) from 386.11 to 386.12. No issues discovered yet.
It seems my RT-AC88U lost 2.4 Ghz a couple of months ago. I was hoping a new firmware would trigger 2.4 Ghz to go working again.
I don't think it's related to firmware, but to the router itself. When I have a little bit more spare time, i'll do a factory reset to see if this revives 2.4 Ghz. For the moment I'll manage with 2.4 Ghz from my mesh slave.

 

[pavlfz]

All working perfectly here. Thanks!

 

[heysoundude]

I had to reboot my AC86 before the upgrade would "take;" I've never had to do that before.
I'm taking that as a sign I need to do a reset after many, many dirty flashes.

Thank you for your continued efforts on our behalf, @RMerlin !!

 

[visortgw]

I had to reboot my AC86 before the upgrade would "take;" I've never had to do that before.
I'm taking that as a sign I need to do a reset after many, many dirty flashes.

Thank you for your continued efforts on our behalf, @RMerlin !!

Not necessarily. It may simply indicate that there was not enough free RAM prior to reboot.

 

[heysoundude]

Not necessarily. It may simply indicate that there was enough free RAM prior to reboot.

wasn't?

 

[Benjamin John]

I keep seeing this after upgrading to the latest version. RT-AC68U 386_12_0
wanduck: WARNING - router is in manufacturing mode, and can behave unexpectedly (did you mess with your bootloader?)

 

[RMerlin]

I keep seeing this after upgrading to the latest version. RT-AC68U 386_12_0
wanduck: WARNING - router is in manufacturing mode, and can behave unexpectedly (did you mess with your bootloader?)

As the message says, did you? Do you have a real RT-AC68U or a hacked, unsupported device?

 

[JackZhao]

Thanks for the hard works!

Is there any way to update the firmware from a VPN client? It maintained the old version and failed to update from my OpenVPN client.

 

[KrypteX]

Is it required to clean NVRAM with the `clear_vpnclients.sh` script when upgrading directly from 386.10 to 386.12?

Version 386.11 specifically mentioned the need of doing so in https://www.snbforums.com/threads/asuswrt-merlin-386-11-is-now-available-for-ac-models.84975/

Note that existing settings are not automatically removed, you must run the following command over SSH to remove them from nvram and the /jffs/openvpn/ directory:
clear_vpnclients.sh

 

[Benjamin John]

As the message says, did you? Do you have a real RT-AC68U or a hacked, unsupported device?

I have a ASUS t-mobile branded RT-AC68U.

 

[heywire]

I had to reboot my AC86 before the upgrade would "take;" I've never had to do that before.
I'm taking that as a sign I need to do a reset after many, many dirty flashes.

Thank you for your continued efforts on our behalf, @RMerlin !!

It required a physical reboot, or just clicking Reboot within the WebGUI (or SSL)? And did it cease to work until you did so, or was it just the upgrade that did not "take" before you did?

I'm asking because physical access to the router is a bit of a hassle, so I have to plan the upgrade if it requires physical access.

 

[Deleted member 84281]

I have a ASUS t-mobile branded RT-AC68U.

Thats the problem. It's not a supported model and it's illegal to run this firmware on it.

 

[Pergola Fabio]

upgraded rt-ac88u from 386.5 to 386.12 , long shot, but everything seems to be OK!

thnx!

 

[Benjamin John]

Thats the problem. It's not a supported model and it's illegal to run this firmware on it.

Wow, I never knew that. I think I had this router since 2016 and have run merlin on it for a few years. First time seeing this message.

 

[heysoundude]

It required a physical reboot, or just clicking Reboot within the WebGUI (or SSL)? And did it cease to work until you did so, or was it just the upgrade that did not "take" before you did?

I'm asking because physical access to the router is a bit of a hassle, so I have to plan the upgrade if it requires physical access.

Rebooted from the GUI...
Tried to upload a couple times, as I described, but until I rebooted (and unmounted my entware drive with unbound, diversion etc) and then upload/flash, I only got that "standby" message rather than the expected progress bar.
It's weird, because before I unmounted the entware drive, the router theoretically (as I understand things) would've had the 2GB swap partition available. the firmware image is only 79MB
(It's quite possible I need a refresher on swaps...)

Anyway, you should be good...no physical access req'd