[Release] Asuswrt-Merlin 384.11 is available

[L&LD]

This time update was not smooth. And first ewer, it asked for manual reboot, without even needing it?

https://www.snbforums.com/threads/r...-384-11-is-available.56501/page-2#post-488583

https://www.snbforums.com/threads/r...-384-11-is-available.56501/page-3#post-488607

 

[wiz]

Just updated my AC5300 from 10 to 11. Nothing out of the ordinary to report. Thanks Eric!

 

[MDM]

https://www.snbforums.com/threads/r...-384-11-is-available.56501/page-2#post-488583

https://www.snbforums.com/threads/r...-384-11-is-available.56501/page-3#post-488607

Yes, I think it is a more frequent thing to occur on the RT-AC86U, bu newer heard it on my type of router...

 

[L&LD]

Yes, I think it is a more frequent thing to occur on the RT-AC86U, bu newer heard it on my type of router...

If you read the whole thread though, for the single issue I reported (and it was 'solved' fairly easily) there are many more that had no issues at all with their RT-AC86U's.

And don't forget the 8 updates I did from 384.10_0 too that also went smoothly.

 

[QuikSilver]

Updated to latest version from beta2 on two 86u units no issue here. Scripts continue to work as expected as well. Thanks @RMerlin

 

[John Adler]

dirty update from beta 2
all fine !

 

[Mihai]

Asuswrt-Merlin 384.11 is now available for all supported models. This is a fairly big update which brings a number of new features.

The highlights:

• New DNS Privacy feature, with DNS-over-TLS support. Configurable under WAN -> Internet Connection, this feature lets you connect with DNS servers that support DNS-over-TLS (DoT). DoT allows your DNS queries to be encrypted, preventing snooping from your ISP or anyone else in transit. Please visit https://dnsprivacy.org/wiki/ for more info on this protocol.
• Replaced the custom ntpclient with an ntp daemon. This daemon acts as a client (to sync your router's clock with the NTP servers configured on the router's System -> Administration page), but it can also be used as an ntp server for your LAN devices. Server functionality can be enabled on the System Administration page. Afterward, you can either configure your LAN clients to use your router's IP as their NTP server, or enable the option to intercept NTP requests and automatically redirect them to your router's NTPD.
• Updated some of the Network Tools to use Asus's new Netool service (RT-AC86U and RT-AX88U only). This allows the addition of a new visual ping for instance.
• GPL merges: 384_5951 (RT-AX88U), 384_45713 (all other models). Note that the RT-AC87U and RT-AC3200 are still using the 384_45149 binary blobs for their closed source components.
• Component updates: nano (4.0), curl (7.64.1), dropbear (2019.78).
• Reworked the Firmware Upgrade page. The option to enable/disable automated checks are now on that page, and support for the Beta channel has been removed. Also, the popup reporting a new firmware release will now display that new firmware's version.
• Cleanups to the DDNS page (removed the annoying alert() popups, and moved the notification within the page itself)
• Moved some DNS settings (like DNSSEC) from the DHCP to the Internet Connection page
• Moved LED control to the System -> Administration page
• Editing devices on the Network Map will no longer restart your entire network, only dnsmasq itself. It means that blocking Internet access through it might not immediately come into effect, however the previous behaviour made it impossible to edit multiple clients.
• Custom config/script changes: added service-event-end (run at the end of an rc service event, same parameter as service-event), stubby.postconf/add support (for customizing the DNS Privacy configuration). pre-mount will now receive the filesystem as a second argument.
• Reboot Scheduler should be more reliable and less likely to corrupt plugged USB disks now
• Security issue CVE-2019-1543 resolved in OpenSSL 1.1.x

Please review the changelog for a complete list of changes.

Anyone donating through Paypal: if you do so specifically for the addition of DNS-over-TLS, please leave a note in your donation, so I can forward your donation to @themiron who did about 90% of the implementation. (the last 10% I did was mostly webui stuff around it, like implementing the preset management).


Downloads are here.
Changelog is here.

I have a question about the asuswrt-merlin 384.12 alpha 1 build when it will be available?

 

[L&LD]

I ha


I have a question about the aauswrt-merlin 384.12 alpha 1 build when it will be available?

I think RMerlin deserves a little break first?

Where did you see that mentioned? What do you think it will contain that you want to test?

 

[Swistheater]

I think RMerlin deserves a little break first?

Where did you see that mentioned? What do you think it will contain that you want to test?

He teased us with a bone beta.

 

[heysoundude]

He teased us with a bone beta.

SMH.

 

[L&LD]

He teased us with a bone beta.

The bone beta offer is now gone.

 

[predatorz]

Dirty upgrade to 384.11 from 384.10
Thanks for the hardwork.

 

[bluepoint]

traceroute to www.google.com (216.58.192.36), 30 hops max, 60 byte packets
 1  96.120.21.221 (96.120.21.221)  10.748 ms  10.505 ms  10.001 ms
 2  68.86.171.233 (68.86.171.233)  13.893 ms  13.474 ms  16.879 ms
 3  68.87.166.77 (68.87.166.77)  15.970 ms  15.550 ms  15.548 ms
 4  68.86.95.45 (68.86.95.45)  24.055 ms  23.210 ms  23.597 ms
 5  68.86.82.154 (68.86.82.154)  22.786 ms  22.546 ms  22.302 ms
 6  66.208.233.242 (66.208.233.242)  21.924 ms 66.208.228.98 (66.208.228.98)  20.614 ms  21.426 ms
 7  * * *
 8  216.239.59.14 (216.239.59.14)  21.945 ms 108.170.226.225 (108.170.226.225)  20.938 ms 108.170.226.229 (108.170.226.229)  20.575 ms
 9  216.58.192.36 (216.58.192.36)  19.271 ms  17.590 ms 108.170.226.225 (108.170.226.225)  23.326 ms

On the RT-AC5300 a trace route after upgrading to this release merlin.

Notice it is not listing the hostnames

Even the fix in 68P does not looks right The hops are not aligned properly. Some hops are sharing two lines. I think formatting is the right word to describe these traceroutes abnormality.

traceroute to www.google.com (172.217.10.132), 30 hops max, 38 byte packets
 1  *  *  *
 2  b3386.nycmny-lcr-21.verizon-gni.net (100.41.218.202)  5.449 ms  b3386.nycmny-lcr-22.verizon-gni.net (100.41.218.204)  7.047 ms  6.527 ms
 3  *  *  *
 4  0.et-9-1-2.gw15.nyc1.alter.net (140.222.227.25)  2.607 ms  0.et-9-0-2.gw15.nyc1.alter.net (140.222.1.43)  2.771 ms  2.702 ms
 5  72.14.208.130 (72.14.208.130)  3.117 ms  3.318 ms  3.089 ms
 6  *  *  *
 7  108.170.237.206 (108.170.237.206)  3.467 ms  108.170.237.214 (108.170.237.214)  3.428 ms  72.14.233.226 (72.14.233.226)  5.777 ms
 8  108.170.248.2 (108.170.248.2)  3.709 ms  216.239.51.109 (216.239.51.109)  3.574 ms  216.239.46.249 (216.239.46.249)  3.469 ms
 9  lga34s16-in-f4.1e100.net (172.217.10.132)  3.148 ms  216.239.56.17 (216.239.56.17)  6.300 ms  108.170.227.151 (108.170.227.151)  4.249 ms

 

[RMerlin]

Even the fix in 68P does not looks right The hops are not aligned properly. Some hops are sharing two lines. I think formatting is the right word to describe these traceroutes abnormality.

The traceroute command doesn't do any particular formatting. What you are seeing is the expected output, the traceroute you posted is perfectly normal.

 

[Alfsu]

@RMerlin just want to report the following:

Uploading the firmware update (384.11) on an AC68U fails when DDNS (internal) and Let's Encrypt are enabled. After disabling both, the update went through successfully. Don't know if this behavior is router specific though.

As always, thank you so much for your time and efforts to keep this project going strong!

 

[Swistheater]

@RMerlin just want to report the following:

Uploading the firmware update (384.11) on an AC68U fails when DDNS (internal) and Let's Encrypt are enabled. After disabling both, the update went through successfully. Don't know if this behavior is router specific though.

As always, thank you so much for your time and efforts to keep this project going strong!

It could be due to the changes on the ddns page, no need to worry.

 

[bluepoint]

The traceroute command doesn't do any particular formatting. What you are seeing is the expected output, the traceroute you posted is perfectly normal.

I'm probably expecting Windows tracert(icmp) results were each hops are stack nicely while Asus builtin traceroute's(udp) does not.

tracert yahoo.com

Tracing route to yahoo.com [98.138.219.232]
over a maximum of 30 hops:

  1     2 ms     1 ms     2 ms  router.asus.com
  2    12 ms    23 ms     4 ms  media-router-fp2.prod1.media.vip.ne1.yahoo.com [98.138.219.232]

Trace complete.

Compare it with traceroute. Look at hop 2, it contains 2 hops(look at the ip of the nodes, there are two)

traceroute to www.google.com (172.217.10.132), 30 hops max, 38 byte packets
1 * * *
2 b3386.nycmny-lcr-21.verizon-gni.net (100.41.218.202) 5.449 ms b3386.nycmny-lcr-22.verizon-gni.net (100.41.218.204) 7.047 ms 6.527 ms

 

[CriticJay]

RMerlin, did you say earlier in the thread that there was some merge that wasn't done properly on 384.11? Should we wait for a minor version bump (384.11.1) before updating (if we haven't already updated)?

 

[Howard_inGA]

RT-AC5300
Dirty Upgrade was a piece of cake! Both usb ports were in normal use, and neither was dismounted. I came from Beta 2, and so far, so good on this release!
One bit of weirdness: after the upgrade and a reboot, the internet connection to the modem showed an 'x' indicating no internet. Indeed, it was disconnected! I clicked the internet button, and the connection was immediately restored with full IpV6 up and running (Cloudflare and Dot running).

UPDATE:
-Tried another reboot, and again, got 'Internet status: Disconnected' on the Network Map default page. I had to click the Globe icon twice to restore the connection to the modem. Weird!
-Found usb 3 drive (8TB) not connected. Powered down the router, pulled the media drive, along with the thumb drive used for router data storage. Repaired the thumb drive (corrupted per Win10), and deleted all data there. Plugged both back into the router, then powered the router up. All problems seem resolved after this process.

 

[djrm]

Well, i said 1h but clearly so many time is not needed to flash, factory reset and set iptv config, of course minimal and manual, the only settings i configured is my isp ppoe and iptv. The result... didnt work, same result, channels freeze 2sg later i set it on tv decoder and no multicast on pc with vlc.

Will flash again beta2 and restore config now.

Dirty upgrade on AX88u and Movistar IPTV works as with beta2... I have been watching some minutes the Tv in different channels and works ok... Maybe due the different router model...