What's new

[Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

  • 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!

Hi @john9527. I have upgraded my N66U router's firmware to the latest V23E3, coming from V22E4. With this latest firmware, I can no longer set the RT66U's Domain Name (from LAN > DHCP Server) to " home.lan". It gives me the following error popup: "Domain name cannot be a registered domain!" From the beginning of using your firmware (V03) I have always used home.lan as the dns suffix. With the latest firmware I can for example successfully use "internal.lan".

Because " home.lan" cannot be an registered domain, what is causing this error you think? I am not exactly sure if this was also the case in the V23E1 firmware. It still exists in V23E3 though.
 
Because " home.lan" cannot be an registered domain, what is causing this error you think? I am not exactly sure if this was also the case in the V23E1 firmware. It still exists in V23E3 though.
There must be a cosmic convergence going on somewhere.....I also use home.lan as my domain and just ran into this and fixed it two days ago o_O Pretty sure it was part of some code I backported from ASUS.

Temporary workaround.....don't use a domain that is exactly 3,4 or 8 characters long.

EDIT: Corrected character length for domain name.
 
Last edited:
I also use home.lan as my domain and just ran into this and fixed it two days ago o_O Pretty sure it was part of some code I backported from ASUS.

Temporary workaround.....don't use a domain that is exactly 3,4 or 8 characters long.

Cool, confirmed then :). So from your comment I understand that it will be fixed in the next release. I will wait for it, for now I will temporary use internal.lan.

Thanks John. Awesome firmware and awesome support!
 
Pushed another small refresh to the current stable release. No high severity fixes, just fixing a couple of annoying reported problems.

Enjoy...and thanks again to everyone for their continued support!

LATEST RELEASE: Update-23E4
23-March-2017
Merlin fork 374.43_2-23E4j9527
Download http://bit.ly/1YdgUcP
============================

The key updates:
  • Fix displayed CTF status may be incorrect on LAN/Switch Control page - @cybrnook
  • Fix some router domain names may be incorrectly flagged as being a registered domain - @zonnebril
  • Fix some OpenVPN Client read/write stats may be reversed

SHA256
Code:
8f942b8ba8da56ed1e8953c1f20cfdc9dac6f06fa11c85778d283074a34b2c30  RT-AC56U_3.0.0.4_374.43_2-23E4j9527.trx
11b1f1ddc5f190c98c53b4d7a366da24a4e422cd9efa4870b0f266c01c27c604  RT-AC66U_3.0.0.4_374.43_2-23E4j9527.trx
39d3158cfd444a5fa137b144d22340d014627c33340e3cfb58a5003fc7be8e64  RT-AC68U_3.0.0.4_374.43_2-23E4j9527.trx
fa03328f12608e9ac2f87510e2d69eb3fa970ca48e9aa4d84a309b53f2322067  RT-N16_3.0.0.4_374.43_2-23E4j9527.trx
bb602560e97e46446179976475afc395d9c773be3daa28db7c26b722b9bd6cce  RT-N66U_3.0.0.4_374.43_2-23E4j9527.trx
 
A double release day! :) Pushed a new beta which needs some runtime...

BETA RELEASE: Update-24B6
26-March-2017
Merlin fork 374.43_2-24B6j9527
Download http://bit.ly/1UGjcOX
============================

Following are the major changes (full changelog is in the zip files)

Update-24B6 Highlights
  • Security
    • Update Busybox to 1.25.1 (Merlin/themiron backport)
      This took a couple of hours playing 'whack-a-mole' with compiler errors, and is a significant update. Because of its scope and required other component updates it can affect everything from USB attached devices to scripting and WAN connections. I'm hoping to get at least a couple of beta users for a few weeks of runtime before rolling it out as the stable release.
    • Update OpenVPN to 2.4.1
  • Other Updates
    • NEW: Support for Host-Uniq on PPPoE connections (Vodafone Italy)
    • NEW: Possible support for DFS channels on EU AC66 routers
      Please follow the same directions in Merlin_Fork_Options.txt for the N66 routers to try it out.
    • CHANGED: Update dnsmasq to 2.77-e33b487
      This is a pre-release of the next dnsmasq and includes DNSSEC and IPv6 fixes for some early testing.

As always, a reminder to users with MIPS routers to have a backup of /jffs in case the jffs space needs to be reformatted due to increases in firmware size.

SHA256
Code:
ba9903b7876c9ae336586294cffffd74a27e21b81e340604a58df0c29e54e79a  RT-AC68U_3.0.0.4_374.43_2-24B6j9527.trx
52593fd2659c20b491d48ab7f04ed3d234b936836ae469f2ed66c9053d549965  RT-AC56U_3.0.0.4_374.43_2-24B6j9527.trx
b46d95ea7776e057c64a5a0bce2f16d16043af4db97c6d18c6f1728c190a28d5  RT-N16_3.0.0.4_374.43_2-24B6j9527.trx
9d248e95a3b7dfac0d20b492c9a3feedea8d4cd0a3a01b81db8d02f35ad8f0ff  RT-AC66U_3.0.0.4_374.43_2-24B6j9527.trx
9802f521e3f7ecb506b94207111fd8d58f63bad58550434511ea26078941c138  RT-N66U_3.0.0.4_374.43_2-24B6j9527.trx
 
Last edited:
Pushed another small refresh to the current stable release. No high severity fixes, just fixing a couple of annoying reported problems.
  • Fix some router domain names may be incorrectly flagged as being a registered domain -

Thanks John. This fixed the domain name problem for me.
 
The key updates:
  • Fix displayed CTF status may be incorrect on LAN/Switch Control page - @cybrnook
23E4, loaded up and so far uneventful (which is great).

I made a backup using your utility. Performed a nvram erase, and upon reboot Switch Control was set to CTF Level 1 and Tools tab reflected CTF. So, looks great!

Restored using your utility and am back up and running!

Thanks as always.
 
Howdy all been an long time since I rapped at ya. Is anyone else having trouble connecting to the vpn clients on their n66u with firmware 23E4 (I also had this issue with 23E3)?

I have tried the openvpn client (which used to work, not my first rodeo) and to simplify things, the pptp vpn client and cannot get a connection up with either. Per usual, probably my issue but thought I would check in with the community.
 
Different model (RT-AC68P), but no issues connecting to Private Internet Access as a client. Just be aware that OpenVPN has been updated to 2.4.0, and that brought a handful of new options/hardening with it. So you might need to adjust your settings somewhat. Or , paste out your openvpn connection log so someone can help point out the issue.
 
Different model (RT-AC68P), but no issues connecting to Private Internet Access as a client. Just be aware that OpenVPN has been updated to 2.4.0, and that brought a handful of new options/hardening with it. So you might need to adjust your settings somewhat. Or , paste out your openvpn connection log so someone can help point out the issue.

Probably better to confirm the pptp client is working for others as it is so much simpler to configure... You have no issues connecting the pptp client? I know this seems obvious- but I am confirming the connection by my ip address and it isn't changing. :)
 
Last edited by a moderator:
Thanks @john9527 for the update. Back to home.lan! :)
B.t.w. John, is it a new feature that the router shows the "manually reboot" message after firmware update? I have been seeing this in the latest firmwares only. Just curious :)
 
Thanks @john9527 for the update. Back to home.lan! :)
B.t.w. John, is it a new feature that the router shows the "manually reboot" message after firmware update? I have been seeing this in the latest firmwares only. Just curious :)

Update to 23E4. Thx John.
Got the same message like zonnebril.
 

Attachments

  • Reboot.png
    Reboot.png
    19.4 KB · Views: 375
Thanks @john9527 for the update. Back to home.lan! :)
B.t.w. John, is it a new feature that the router shows the "manually reboot" message after firmware update? I have been seeing this in the latest firmwares only. Just curious :)
Not a new feature....but a fact of life.....
I think it depends on the router being able to grab enough memory to be able to restart everything. I hit it on about 1 out of every 15 updates.
 
@000111 - Whose pptp server are you trying to connect to (commercial, work, private)? Haven't changed anything on the pptp client forever, since it's basically been deprecated.
 
Got it sorted- thanks John.
Glad to hear you figured it out.
I did a little playing, and was able to connect to PIA via pptp client...but found that the auto-negotiation for encryption wasn't working too well, and I had to force the right level via nvram, (exposing this to the gui was in a later level that I hadn't backported.....it is backported now :) )
 
Last edited:
Hi John,

I am a first time user of your firmware and jumped the gun and flashed BETA RELEASE: Update-24B6 on my RT-AC68U. All is working well. I just noticed however that with my Stealthmode scripts i have used with Merlin's firmware without issues when the stealthmode is turned on from my cron job all the LEDS switch off initially but then the USB2 LED turns back on.

I am using the scripts from https://github.com/RMerl/asuswrt-merlin/wiki/Scheduled-LED-control

Is this a bug or is it expected behaviour? I just noticed in your release notes for the latest Beta that you made some changes and mentioned it could affect anything from USB attached devices to WAN connections. Could this be causing the USB2 to turn back on?

Thanks in advance

Shaun
 
Is this a bug or is it expected behaviour?
No, I wouldn't have expected any problems. I just double checked the led commands from the command line on my AC68P and they worked fine.

So, two questions.....
- Did you do a factory reset after loading this fork?
- What is the rev level of your AC68U? (only rev A1, A2 and B1 are supported....C1 and E1 are not)
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top