Release [Fork] Asuswrt-Merlin 374.43 LTS releases (V44EA)

  • ATTENTION! As of November 1, 2020, you will not be able to reply to threads 6 months after the thread is opened. Threads will not be locked, so posts may still be edited by their authors.

john9527

Part of the Furniture
Just updated to the latest firmware and really like your final implementation of the FTP TLS function in addition to port selection. You did a great job of moving the PORT selection change to the FTP Share (makes more sense) and the explanation within that selection is perfect even for a novice. Thanks very much John.
Wording in consultation with @ColinTaylor :)
 

JohnSmith

Regular Contributor
Upgraded RT-AC66U A1 - Qty3 , from ASUS Merlin V374.43_41EAj9527 to ASUS Merlin LTS Fork V374.43_42E7j9527 via dirty firmware upgrade, and all working properly as Access Points (AP's).
 

Gar

Very Senior Member
Working well on my 56u with a simple config, thanks and welcome back.
 

john9527

Part of the Furniture
@john9527, do you have plans to integrate nextdns into the firmware?
The NextDNS servers can work with stubby DoT, so I've added them to the available stubby resolvers. Those that have updated to the 42E7 release can use the
stubby-update-resolvers.sh
command to make them available.
nextdns.png
If you mean integrating the NextDNS client....it's a REALLY BIG piece of work to do something like that, so at this point I'd say that's not likely to happen.
 
Last edited:

dave14305

Part of the Furniture
The NextDNS servers can work with stubby DoT, so I've added them to the available stubby resolvers. Those that have updated to the 42E7 release can use the stubby-update-resolvers.sh command to make them available.
For people to use a custom NextDNS configuration profile with ad-blocking, etc., they will need to be able to update the tls_auth_name with the name of their custom configuration. So a static definition is probably only good to use the service in a vanilla manner.

Code:
round_robin_upstreams: 0
upstream_recursive_servers:
  - address_data: 45.90.28.0
    tls_auth_name: "abc1234.dns1.nextdns.io"
  - address_data: 2a07:a8c0::0
    tls_auth_name: "abc1234.dns1.nextdns.io"
  - address_data: 45.90.30.0
    tls_auth_name: "abc1234.dns2.nextdns.io"
  - address_data: 2a07:a8c1::0
    tls_auth_name: "abc1234.dns2.nextdns.io"
 

Builder71

Very Senior Member
Good to see you posting again John, all the best to you.

I installed 42E7 without problems on my RT-N66U.

Funfact: Recently my ISP decided to stop supporting Bridged IPTV, now only Routed IPTV is possible.
As you know Bridged IPTV is easy to configure on the ASUS LAN -> IPTV tab. Routed... not so easy. :rolleyes:
Long story short, I found some slick scripts to configure Routed IPTV.
Works great on my old and trusty RT-N66U, because of you, still providing security updates and other fixes for it. :)

Awesome!
 

john9527

Part of the Furniture
Just an FYI on the NextDNS servers....looks like they are generating some rebind attack msgs that I never saw on Cloudflare or Quad9. Your mileage may vary :)
 

LtJeronimo

New Around Here
I would like to move to John's fork on my AC66U (non B-1). Right now I'm on the latest 380 MerlinWRT.
When opening the restoration tool a message pops up that the A1 version of the AC66U is not supported even though I downloaded
the utility from the AC66U's support page. Has anyone else encountered this and would it still be safe to downgrade the firmware with the utility?


 

ColinTaylor

Part of the Furniture
When opening the restoration tool a message pops up that the A1 version of the AC66U is not supported even though I downloaded the utility from the AC66U's support page.
I can't see anything in your screen shot that says version A1 is not supported.

The message shown is telling you that you should only upload a firmware that matches your router model. It also points out that the "RT-AC66U_B1" is not the same model as "RT-AC66U" so they have different firmware.

EDIT: I think I see the confusion. The message is wrong, perhaps mistranslated from Chinese. The message talks about "hardware version" when it really means "model number". "RT-AC66U_B1" is a model not a hardware version.
 
Last edited:

SarahG

New Around Here
Welcome back John! Thank you for all of your work maintaining this port! I actually just bought an AC68U for my folks' house which will soon run your 374 branch, based on how rock solid it runs on my N66U.
 

acale75

Occasional Visitor
The NextDNS servers can work with stubby DoT, so I've added them to the available stubby resolvers. Those that have updated to the 42E7 release can use the
stubby-update-resolvers.sh
command to make them available.
View attachment 22278
If you mean integrating the NextDNS client....it's a REALLY BIG piece of work to do something like that, so at this point I'd say that's not likely to happen.
Thanks a lot John. I'll give a it try
 

dave14305

Part of the Furniture
Thanks John and Dave.
I have selected the nextdns servers. Is it possible to link them to my nextdns id?
@john9527 I think you need to remove your custom ID from the tls name in stubby-resolvers.csv on OneDrive.

@acale75 You could use a stubby.postconf script to replace the tls_auth_name with you own config id.
 

ColinTaylor

Part of the Furniture
@john9527 I think you need to remove your custom ID from the tls name in stubby-resolvers.csv on OneDrive.
Exactly what I was thinking.

@acale75 You could use a stubby.postconf script to replace the tls_auth_name with you own config id.
Replace 123456 with your own ID.
/jffs/configs/dnsmasq.conf.add
Code:
# NextDNS
add-cpe-id=123456
# Uncomment the following lines to send devices MAC and local IPs
# and identify them in NextDNS Logs and Analytics sections.
add-mac
add-subnet=32,128
/jffs/scripts/stubby.postconf
Code:
#!/bin/sh

CONFIG=$1
source /usr/sbin/helper.sh

pc_replace "dns1.nextdns.io" "123456.dns1.nextdns.io" $CONFIG
pc_replace "dns2.nextdns.io" "123456.dns2.nextdns.io" $CONFIG
EDIT: Updated stubby.postconf because of change in posts #10342/10344.
 
Last edited:

john9527

Part of the Furniture
@john9527 I think you need to remove your custom ID from the tls name in stubby-resolvers.csv on OneDrive.
Not too worried.....I'm not registered. Just hit the 'try it for free' link to see the docs. Didn't realize that's how they made the account link.
I'm not using it, for me it generates pages of rebind attack warnings.

Do you know if there is a 'generic' auth-id to use'?
 

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