What's new

Release [Fork] Asuswrt-Merlin 374 LTS release 45EC

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

john9527

Part of the Furniture
The next release 46E8 is now available

LATEST RELEASE: Update-45EC
19-November-2020
Merlin fork 374.43_45ECj9527
============================

Picks up a few fixes for problems reported since the last release...

Update-45EC Highlights
• Fixed DNSFilter broken with 45EA
• Fixed unnecessary NTP timesync warning when NTP sync is disabled
• Fixed incompatible ext4 format options introduced with new e2fsprogs
• Fixed Adguard DoT servers not working (still need to use the old IP addresses with DoT)

Update-45EA Highlights
• Updated nano, curl, zlib, e2fsprogs, OpenSSL, dnsmasq
• Use secure connection for GoogleDDNS
• Fixed false timezone error for some timezones
• Enabled TOP memory report
• Fixed incorrect start/stop times for Network Services Filter
• New lan-start script support
• Updated stubby AdGuard servers
• Masquerade all client outbound traffic regardless of source subnet for OpenVPN client
• Increase number of ADDONS mount points to 20
• Increase max number of samba/ftp user accounts to 15
• Color code each guest wireless network in wireless log
• Fixed OpenVPN client killswitch not always working following reboot
• Fixed wireless configuration error in ARM 5G
• Changed services-start and services-stop to blocking scripts due to potential nvram memory collisions


Download: https://1drv.ms/f/s!Ainhp1nBLzMJgXEJCQVqKPjosiia

Full ChangeLog: Changelog.txt in the download directory

Overview/Installation: LTS_OVERVIEW.pdf in the download directory

Previous release threads:
https://www.snbforums.com/threads/fork-asuswrt-merlin-374-43-lts-releases-archive.18914/

SHA256
c7d40bfbd669990822cd44f369bb0d6cb8d0c0ff557e915b2f19bd76fb64f265 RT-N16_374.43_45ECj9527.trx
35371bd846cee5a74288b70be8afb1765320055d195040111dc94329d7fab58a RT-AC66U_374.43_45ECj9527.trx
1abdc61bf6728c055d5479d7f0acc35d9c8aeb7432882bedc53fbe3d47924925 RT-N66U_374.43_45ECj9527.trx
21bb1a4eadb290fed7ba8ebf9a99f3088c55f462dcc8e24a4db13db840e15530 RT-AC68U_374.43_45ECj9527.trx
1cd9bb3c0377ed3ceac21005b32593c95bf99dcc763809b0360a06a15721eb1c RT-AC56U_374.43_45ECj9527.trx
 
Last edited:
Hi John, welcome back.

I using new developing build 46D2 and can report CHACHA20-POLY1305 working just fine on my vpn-nodes.
Code:
Nov  7 20:18:06 openvpn[2589]: Outgoing Data Channel: Cipher 'CHACHA20-POLY1305' initialized with 256 bit key
Nov  7 20:18:06 openvpn[2589]: Incoming Data Channel: Cipher 'CHACHA20-POLY1305' initialized with 256 bit key
Nov  7 20:18:06 openvpn[2589]: Control Channel: TLSv1.3, cipher TLSv1.3 TLS_CHACHA20_POLY1305_SHA256, 1024 bit RSA

Can you add a link to old thread som we can find it when it's get unpinned.

Thank you for new builds!
 
I have a GPS sync clock on this build to get right time but How do I get rid of this warnig text?
Code:
*Reminder: Your system time has not been synchronized with a NTP server.
I have set this in nvarm:
Code:
octopus@RT-AC56U-7EE8:/tmp/home/root# nvram show | grep ntp_
ntp_server0=se.pool.ntp.org
ntp_server1=europe.pool.ntp.org
size: 60338 bytes (5198 left)
ntp_ready=1
ntp_log_x=1
ntp_sync=1
ntp_server_tried=none
ntp_update=0

Thank you
Octopus
 
I have a GPS sync clock on this build to get right time but How do I get rid of this warnig text?
Code:
*Reminder: Your system time has not been synchronized with a NTP server.
I have set this in nvarm:
Code:
octopus@RT-AC56U-7EE8:/tmp/home/root# nvram show | grep ntp_
ntp_server0=se.pool.ntp.org
ntp_server1=europe.pool.ntp.org
size: 60338 bytes (5198 left)
ntp_ready=1
ntp_log_x=1
ntp_sync=1
ntp_server_tried=none
ntp_update=0

Thank you
Octopus
Looks like a bug.... ntp_update=0 should have done it. In the meantime, try
Code:
nvram set svc_ready=1
nvram commit
 
Looks like a bug.... ntp_update=0 should have done it. In the meantime, try
Code:
nvram set svc_ready=1
nvram commit

Thank you
That working fine. :)
 
Did the typical firmware installation from the prior version to the latest firmware update in the GUI on my old RT-N16. After the 4 minutes it took to update, a message popped up saying that I would have to manually reboot. Since the browser window offered no "Reboot" command button and the N16 does not have a on/off switch I unplugged the router waited 15 seconds then replugged it in.

My computer can no longer access the router. I see the power button is on, and depending on which ethernet port I have the cable plugged in, it shows the lit ethernet port.

I tried the 30/30/30 hard reset. Hold reset for 30 seconds, unplug the power for 30 seconds, plug the power back in for 30 seconds while continuously holding the reset button. still no connection. lights come on

I went to the asus website to download the asus recovery tool and read/remind myself of the method(s) to recover from a failed firmware installation. My browser would not show those recovery utilities. Has something changed that asus no longer offers the firmware recovery tools/utilities?

Edit: Using Brave I couldn't get the list of utilities to render. When I tried Firefox I see the "Utilities" menu and the "ASUS Firmware Restoration version 2.1.0.2" tool. weird.
 
My computer can no longer access the router. I see the power button is on, and depending on which ethernet port I have the cable plugged in, it shows the lit ethernet port.
Sorry you are having a problem. What firmware were you upgrading from?

First thing I would try is just a factory reset.

The code size has been slowly creeping up and on the MIPS based routers can cause JFFS to be corrupted. If the factory reset works, you can then restore your settings from backup and reformat/reload JFFS.
 
LATEST RELEASE: Update-45EA
29-October-2020
Merlin fork 374.43_45EAj9527
============================

Update-45EA Highlights
• Updated nano, curl, zlib, e2fsprogs, OpenSSL, dnsmasq
• Use secure connection for GoogleDDNS
• Fixed false timezone error for some timezones
• Enabled TOP memory report
• Fixed incorrect start/stop times for Network Services Filter
• New lan-start script support
• Updated stubby AdGuard servers
• Masquerade all client outbound traffic regardless of source subnet for OpenVPN client
• Increase number of ADDONS mount points to 20
• Increase max number of samba/ftp user accounts to 15
• Color code each guest wireless network in wireless log
• Fixed OpenVPN client killswitch not always working following reboot
• Fixed wireless configuration error in ARM 5G
• Changed services-start and services-stop to blocking scripts due to potential nvram memory collisions


Download: https://1drv.ms/f/s!Ainhp1nBLzMJgXEJCQVqKPjosiia

Full ChangeLog: Changelog.txt in the download directory

Overview/Installation: LTS_OVERVIEW.pdf in the download directory

Previous release threads:
https://www.snbforums.com/threads/fork-asuswrt-merlin-374-43-lts-releases-archive.18914/

SHA256
1d6e2a981d8af9b57bd037d6fe696d694be052e46d9cd69a4da8d019e65263c3 RT-N16_374.43_45EAj9527.trx
c98d772c7b360e6dc4cc7262048ba9dd3527c6926a0c5a7dfb037756b675a290 RT-AC66U_374.43_45EAj9527.trx
63b33633dd7eb6b53bafeb735fb7c5ad0954d4dbe86d820e019516aa3c4ef8f9 RT-N66U_374.43_45EAj9527.trx
1267fcc6aff5d3665583bf0da991e8ff327927450d508bf1104b45c27208cdde RT-AC68U_374.43_45EAj9527.trx
48f5ca1ac895638930f3f34f2f1b341fc776f261a570cf75349621e52735c188 RT-AC56U_374.43_45EAj9527.trx
Welcome back John! We are glad to see you back to run your awesome Fork!
 
Thank you John. New Firmware works flawlessly here (vlan).
Good to hear....thanks.

Not sure how you are setting up your vlan, but you may want to look at using the new lan-start script (I added this to support my vlan). Putting the vlan setup here avoids losing the vlan config when making some changes from the gui, for instance changing the wireless parameters.
 
Sorry you are having a problem. What firmware were you upgrading from?

First thing I would try is just a factory reset.

The code size has been slowly creeping up and on the MIPS based routers can cause JFFS to be corrupted. If the factory reset works, you can then restore your settings from backup and reformat/reload JFFS.

Please, don't apologize! I'm just amazed that such an old router (which I mothballed years ago) is still being supported somewhere. I treat it like an old fixer car. Tinker here and there, and if it works, great. If it doesn't work tinker some more. As I've gotten older seems that I forget the precise particulars of restore/recovery. (or I think, with the stability of Merlin and your firmwares, I haven't had this issue in years)

Getting past that: I was updating from RT-N16 LTS fork 374.43_44EAj9527 to your latest build. I did try the Method 1 recovery. The power light immediately rapidly blinks until I release the WPS button where it goes to a slow blink, then after a few minutes power light stays on. Computer still doesn't recognise the N16.

Since this is maybe trending OT for this thread, I'm looking for a thread that addresses restore/recovery (in all it's glory ;)--like I vaguely remember confirming rescue mode ttl=64 vs. ttl=100).
 
Not sure how you are setting up your vlan, but you may want to look at using the new lan-start script

I had to split the config to init-start and services-start before to have it working reliably, so I guess, this will not change with that.
init-start
Code:
#!/bin/sh
robocfg vlan 1 ports "0 1 2 4 5t"
robocfg vlan 201 ports "4t 5t"
robocfg vlan 202 ports "3 4t 5t"

services-start
Code:
#!/bin/sh
vconfig add eth0 201
vconfig add eth0 202
ifconfig vlan201 up
ifconfig vlan202 up

brctl addbr br1
brctl delif br0 wl0.1
brctl delif br0 wl1.1
brctl addif br1 vlan201
brctl addif br1 wl0.1
brctl addif br1 wl1.1
ifconfig br1 up

brctl addbr br2
brctl delif br0 wl0.2
brctl addif br2 vlan202
brctl addif br2 wl0.2
ifconfig br2 up

nvram set lan_ifnames="vlan1 eth1 eth2"
nvram set lan_ifname="br0"
nvram set lan1_ifnames="vlan201 wl0.1 wl1.1"
nvram set lan2_ifnames="vlan202 wl0.2"
nvram set lan1_ifname="br1"
nvram set lan2_ifname="br2"

nvram commit
killall eapd
eapd
But it is working great as an AP together with pfSense for me anyway. :D
 
Last edited:
john9527
Hello! Thanks for the new release! Everything works perfectly!
However, there are 2 irrelevant questions.
How to fix this error in the system log file:
Jan 1 03:00:33 wsdd2[414]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
And also this one:
Nov 9 08:06:08 openvpn[577]: Options error: Unrecognized option or missing or extra parameter(s) in [PUSH-OPTIONS]:3: block-outside-dns (2.4.9)
This error message occurs despite the fact that I did not set the "block-outside-dns" parameter in the OpenVPN settings.
 
This error message occurs despite the fact that I did not set the "block-outside-dns" parameter in the OpenVPN settings.
Are you talking about the router's VPN server or VPN client? That parameter appears to only be valid for Windows clients.
 
How to fix this error in the system log file:
Jan 1 03:00:33 wsdd2[414]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
This is an artifact of wsdd2 during start/stop of everything not being up yet or being shut down. It can be ignored. If you aren't trying to share a router USB drive to Windows and have it show up in Network, you can turn off wsdd with
Code:
nvram set wsdd_enable=0
nvram commit
I'll also take a look and see if I can move it in the start/stop sequence.

And also this one:
Nov 9 08:06:08 openvpn[577]: Options error: Unrecognized option or missing or extra parameter(s) in [PUSH-OPTIONS]:3: block-outside-dns (2.4.9)
This error message occurs despite the fact that I did not set the "block-outside-dns" parameter in the OpenVPN settings.
It's being shown as a PUSH-OPTION, being sent by your VPN provider. Looks like they only live in a Windows only world.... as @ColinTaylor said it's a Windows only option.
 
After managing a firmware recovery on my RT-N16 using the latest stock firmware at ASUS, and then trying to then update firmware to John's Latest Fork I get this message:
===================================
Invalid Firmware Upload
To comply with regulatory amendments, we have modified our certification rule to ensure better firmware quality. This version is not compatible with all previously released ASUS firmware and uncertified third party firmware. Please check our official websites for the certified firmware.
===================================
I have tried to install every prior version of stock firmware and it's a no-go. Any way around this issue?
 
Did you try doing it via firmware recovery mode?
 
After managing a firmware recovery on my RT-N16 using the latest stock firmware at ASUS, and then trying to then update firmware to John's Latest Fork I get this message:
===================================
Invalid Firmware Upload
To comply with regulatory amendments, we have modified our certification rule to ensure better firmware quality. This version is not compatible with all previously released ASUS firmware and uncertified third party firmware. Please check our official websites for the certified firmware.
===================================
I have tried to install every prior version of stock firmware and it's a no-go. Any way around this issue?
Use the Asus Firmware Restoration/Recovery tool available on their website for every product...it's the only way to upload the Fork firmware after using the official version. Just look around for the howto as it's pretty easy. https://www.asus.com/ca-en/Networking/RTN16/HelpDesk_Download/
 
After managing a firmware recovery on my RT-N16 using the latest stock firmware at ASUS, and then trying to then update firmware to John's Latest Fork I get this message:
===================================
Invalid Firmware Upload
To comply with regulatory amendments, we have modified our certification rule to ensure better firmware quality. This version is not compatible with all previously released ASUS firmware and uncertified third party firmware. Please check our official websites for the certified firmware.
===================================
I have tried to install every prior version of stock firmware and it's a no-go. Any way around this issue?
Glad to hear you have it recovered!

Check the installation notes in LTS_OVERVIEW.pdf
The comments would also apply to trying to revert to an OEM level prior to those listed.
 

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