[Release] Asuswrt-Merlin 384.13 is 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 is now available for all supported models. The main change of this release is the addition of support for AiMesh (both router and nodes) for those models that are compatible (RT-AC87U and RT-AC3200 are not supported).

Update (14-Dec-2019): 384.13_2 is now available for RT-AC87U and RT-AC3200, including various fixes such as Let's Encrypt support for ACMEv2.

Update:
384.13_1 for the RT-AC87U, which resolves AP mode for that model.

This release also includes a number of fixes. The highlights:
  • AiMesh support for both router and nodes. See the AiMesh section below for more information. Please visit the Wiki for more information.
  • Updated RT-AX88U to GPL 384_6210.
  • dnsmasq now uses OpenSSL instead of Nettle for DNSSEC cipher operations. This allows dnsmasq to validate a wider range of ciphers.
  • Note for developers, the dhcp_staticlist format was changed to revert back to the same format as stock firmware (for AiMesh compatibility). The hostname field was moved to a separate variable, dhcp_hostnames. Note that this variable will be stored in a jffs file on the RT-AC86U and RT-AX88U due to limitations on variable length for their HND platform. That means that a backed up config file will not restore these hostnames when restored (but using a JFFS backup will).
  • Some changes also had to be done to the webs_* variables that are used by the new firmware checks, which might affect script developers that were accessing those variables.
  • A number of minor issues were fixed, see the Changelog for details

Please only post in this thread about this specific release.

Downloads are here.
Changelog is here.
 
Last edited:

snapieee

Occasional Visitor
Asuswrt-Merlin 384.13 is now available for all supported models. The main change of this release is the addition of support for AiMesh (both router and nodes) for those models that are compatible (RT-AC87U and RT-AC3200 are not supported). This release also includes a number of fixes. The highlights:

  • AiMesh support for both router and nodes. See the AiMesh section below for more information. Please visit the Wiki for more information.
  • Updated RT-AX88U to GPL 384_6210.
  • dnsmasq now uses OpenSSL instead of Nettle for DNSSEC cipher operations. This allows dnsmasq to validate a wider range of ciphers.
  • Note for developers, the dhcp_staticlist format was changed to revert back to the same format as stock firmware (for AiMesh compatibility). The hostname field was moved to a separate variable, dhcp_hostnames. Note that this variable will be stored in a jffs file on the RT-AC86U and RT-AX88U due to limitations on variable length for their HND platform. That means that a backed up config file will not restore these hostnames when restored (but using a JFFS backup will).
  • Some changes also had to be done to the webs_* variables that are used by the new firmware checks, which might affect script developers that were accessing those variables.
  • A number of minor issues were fixed, see the Changelog for details

Please only post in this thread about this specific release.

Downloads are here.
Changelog is here.

Awesome work!!!!! [emoji106]
Thnx Eric
 

AntonK

Very Senior Member
Upgrade from Beta smooth as silk. Thanks RMerlin!
 

MDM

Senior Member
Dirty upgrade from 13 beta, all is fine.

Except one little thing I noticed:
Annotation 2019-08-01 031029.png

I can not see, but I can choose "www.yandex.ru" and "www.vk.com"... No biggie ;)
 

nzwayne

Regular Contributor
Dirty upgrade on the three units of my hours old AiMesh 384.13 beta1 to 384.13 with AX88U + 2x AC86U's. Firstly the AX88U, all good with all cables plugged + the USB drive (never had a problem with them installed..), AMTM, Diversion, Skynet. As requested by the code on finish, a manual Reboot. After System Log went quiet on AX88U,onto first AC86U, but it went offline after the code update. Power Off/On brought that unit back online. 2nd AC86U all went ok, came back online by itself.
Thanks Eric, Awesome!!
AiMesh update.jpg AiMesh update1.jpg
 

MDM

Senior Member
@nzwayne
I know it is completely off topic, or rather of subject.
But I am just too curious; what the hell is "On 7.0kW Inverter"? o_O:D
 
Last edited:

LimJK

Very Senior Member
RMerlin,

Thank You! :)
Moving from Beta 1, Everything is working with my Merlin-AiMesh Router configuration, for my case including:
  • AiProtection (All turned ON)
  • Smart Connect Dual Band (Still missing TriBand as per Stock Firmware, despite Wired Backhaul)
  • DHCP (list of 43 devices)
  • IPv6 (Native)
  • VPN (Single OpenVPN Server)
  • DDNS (Asus DDNS)
Thank You! :)
 

nzwayne

Regular Contributor
@nzwayne
I know it is completely of topic, or rather of subject.
But I am just too curious; what the hell is "On 7.0kW Inverter"? o_O:D
My basement has 1x AC86U Router, sitting on top of one of my two DC->AC inverters (5.0kW & 7.0kW) for my 35x solar panels. Using the "location" field to help remind me physically where the router is.
 

MDM

Senior Member
My basement has 1x AC86U Router, sitting on top of one of my two DC->AC inverters (5.0kW & 7.0kW) for my 35x solar panels. Using the "location" field to help remind me physically where the router is.
Ahahaha, thanks you made me laugh. It just reads as if you went nuclear with your router consuming 7kW :D
Once again, sorry for the off topic I just had to... :)

I am also surprised it can emit WiFi under those circumstances, such inverter emits usually quite the noise..
 

hamsterbasher

New Around Here
Upgraded my AC3100 with no issues. Smooth as silk but my AIMesh Node which is an AC88U didnt go smooth. Tried twice but the node never recovered. It boots but sits with just power and both wireless lights on solid. If I flash back to 3.0.0.4.384 then its fine and Node is back up. Anyone out there with a AC88U as a node got it to work?
 

Marin

Very Senior Member
Upgraded my AiMesh router and the three nodes with 384.13. Everything (including VPN) is working great and reporting no issues at this time.
 

RMerlin

Asuswrt-Merlin dev
Dirty upgrade from 13 beta, all is fine.

Except one little thing I noticed:
View attachment 18810
I can not see, but I can choose "www.yandex.ru" and "www.vk.com"... No biggie ;)

Try a different browser. They are written in Cyrillic, and they show up properly for me under Chrome.

upload_2019-7-31_22-26-44.png


Upgraded my AC3100 with no issues. Smooth as silk but my AIMesh Node which is an AC88U didnt go smooth. Tried twice but the node never recovered. It boots but sits with just power and both wireless lights on solid. If I flash back to 3.0.0.4.384 then its fine and Node is back up. Anyone out there with a AC88U as a node got it to work?

Do a factory default reset on the node and re-add it.
 

Gar

Very Senior Member
A-OK. Thanks again!
 

pinkfloyd1173

Senior Member
Hey Guys I have a question.

I have always wondered what is the second file used for, exsample ,"SHA256File"

I have always seen a second file and never really new if I needed to do something with it, always just downloaded the regular file for my router at the time?

Thanks in advance.
 

RMerlin

Asuswrt-Merlin dev
Hey Guys I have a question.

I have always wondered what is the second file used for, exsample ,"SHA256File"

I have always seen a second file and never really new if I needed to do something with it, always just downloaded the regular file for my router at the time?

It's a text file that contains a signature generated for the firmware file. It allows people to confirm that the firmware image they downloaded hasn't been modified or corrupted, by generating a SHA256 signature themselves and comparing it with those I publish in multiple locations (including on my website, which is completely separate from the download servers).
 

pinkfloyd1173

Senior Member
It's a text file that contains a signature generated for the firmware file. It allows people to confirm that the firmware image they downloaded hasn't been modified or corrupted, by generating a SHA256 signature themselves and comparing it with those I publish in multiple locations (including on my website, which is completely separate from the download servers).

I see, thank you for the explanation good sir. Also thanks again for all your hard work on the FW stuff for all of us.
 

Zastoff

Very Senior Member
Smooth update from beta1 to 384.13 :) (RT-AC87u)
Thanks RMerlin
 
Last edited:
Status
Not open for further replies.

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