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!

Installed easily enough. Enabled SNTP on the Admin page. Checked dnsmasq.conf and didn't see the option added. Manually restarted dnsmasq in ssh and it showed up. Still looking for a client that actually respects that option. :(
Sigh.....yes, it currently needs a dnsmasq restart or reboot to become active. Just added the 2 lines of gui code to do it (to go along with the 2 lines it took in the mainline :) ) Will pick it up in the next release.
 
Google DNS now supports DoT.....the stubby resolvers file has been updated
stubby-update-resolvers.sh
 
Google DNS now supports DoT.....the stubby resolvers file has been updated
stubby-update-resolvers.sh
Confirmed it works for me. May want to interlope and advise the non-forkers how to set it up. :)
 
Just as an FYI...I'm also running a development build now with the latest getdns 1.5.0/stubby 0.2.4/OpenSSL 1.1.1a

But (there's always a but)....I have to statically link the OpenSSL 1.1.1 libraries due to dependencies in some ASUS closed source modules on 1.0.x , so the code images increase in size from 1M (AC68) to 1.6M(N66). May be tolerable on the AC68, but it's a direct takeaway from jffs space on the N66.
 
@john.
did the restore thing.

#a still makes a huge difference for the RT-AC66U

in my room 6 meters away before 60% after 77%
standing in front of the closet which holds the router(1meter away, thin wooden wall) before 85% after 99%

please note that this is on 2.4Ghz before i even changed the power settings so this is with 100mw power settings.
so those regulalions they put on EU/13 are crippeling wifi routers
 
Just as an FYI...I'm also running a development build now with the latest getdns 1.5.0/stubby 0.2.4/OpenSSL 1.1.1a

But (there's always a but)....I have to statically link the OpenSSL 1.1.1 libraries due to dependencies in some ASUS closed source modules on 1.0.x , so the code images increase in size from 1M (AC68) to 1.6M(N66). May be tolerable on the AC68, but it's a direct takeaway from jffs space on the N66.

Does increase in the image size (N66) cause problem while installing or after the installation? I'm asking because JFFS usage on my end is pretty low (0.64 / 11.50 MB).

Also, I'm interested in testing the dev build you mentioned if you need a test subject who installs every alpha/beta fw & software he meets :D
 
Sorry everyone, but I've just had to push an update to 37EA/37LA.

While working with Merlin on a problem in another thread, I discovered that an architecture change in the latest ASUS code affected a backport I did from his builds. Net result was that the VPN DNS servers were now not being used in the VPN client (Accept DNS Configuration settings).

In addition to the above, it also contains a change to advertise the router IP as the NTP server under DHCP option 42 if the SNTP server is enabled (@dave14305 )

LATEST RELEASE: Update-37EA/37LA
9-January-2019
Merlin fork 374.43_37EAj9527
Download http://bit.ly/1YdgUcP
============================

Key Changes:
  • Fix a regression in 37E9 that prevented pushed VPN DNS servers from being used in the client
  • Advertise the router IP as the NTP server under DHCP option 42 if the SNTP server is enabled

SHA256
Code:
(Default Build - All supported routers)
3100ccc623883a3847bb8fe2199b85da1642c837a4408dee17fd10eee04b4498  RT-AC56U_374.43_37EAj9527.trx
692d026824f53da1baaf5650d597a3b311c6441cb69b81d642819ae7e9ca8651  RT-AC66U_374.43_37EAj9527.trx
71832d71513a77e5fb770c239b63c690eeb9dc9bc61b397d7b787e4a68ccf82b  RT-AC68U_374.43_37EAj9527.trx
42afac22c739d95bfce6e81829f64004277fa63df5b802db05b5870d2a9f9f5d  RT-N16_374.43_37EAj9527.trx
b4362dd7586aeee23857fbec79a7b2a053aa8aefa618adc95f0ba293b6f5dcd8  RT-N66U_374.43_37EAj9527.trx

(Legacy Only Builds)
4f7e6f7da32dda771f5da3a13d2b83dae779a57b387ebddf421f8476c0211297  RT-AC68U_3.0.0.4_374.43_2-37LAj9527.trx
9a788110538a5c297b7fe2b9906df8d2f62c1ebca1b8b8ad6b6724f593158949  RT-AC56U_3.0.0.4_374.43_2-37LAj9527.trx
21e6699f3e81281e182f2b2f078b0ad8938552c3d136db9dd93c2796537158d4  RT-N16_3.0.0.4_374.43_2-37LAj9527.trx
1b6ffd3b3dd82058e24304e8fa573ce718040264c097926d87a4050a0c473076  RT-AC66U_3.0.0.4_374.43_2-37LAj9527.trx
9e0f13fa7c0919951c7ace011d0bb66ffef9378d940626a8ea0de1835730227c  RT-N66U_3.0.0.4_374.43_2-37LAj9527.trx

Getting this error in the log...change Samba from SMBV2 to SMBV1+SMBV2 and it goes away!
Did not notice this until 37E9 release

Code:
Jan 10 10:22:35 smbd[1203]: [2019/01/10 10:22:35.692798,  0] smbd/negprot.c:706(reply_negprot)
Jan 10 10:22:35 smbd[1203]:   No protocol supported !
Jan 10 10:22:35 smbd[1204]: [2019/01/10 10:22:35.705012,  0] smbd/negprot.c:706(reply_negprot)
Jan 10 10:22:35 smbd[1204]:   No protocol supported !
Jan 10 10:22:37 smbd[1205]: [2019/01/10 10:22:37.976794,  0] smbd/negprot.c:706(reply_negprot)
Jan 10 10:22:37 smbd[1205]:   No protocol supported !
Jan 10 10:22:37 smbd[1206]: [2019/01/10 10:22:37.990738,  0] smbd/negprot.c:706(reply_negprot)
Jan 10 10:22:37 smbd[1206]:   No protocol supported !
Jan 10 10:22:49 smbd[1208]: [2019/01/10 10:22:49.440699,  0] smbd/negprot.c:706(reply_negprot)
Jan 10 10:22:49 smbd[1208]:   No protocol supported !
Jan 10 10:22:49 smbd[1209]: [2019/01/10 10:22:49.448774,  0] smbd/negprot.c:706(reply_negprot)
Jan 10 10:22:49 smbd[1209]:   No protocol supported !
Jan 10 10:22:56 smbd[1210]: [2019/01/10 10:22:56.256748,  0] smbd/negprot.c:706(reply_negprot)
Jan 10 10:22:56 smbd[1210]:   No protocol supported !
Jan 10 10:22:56 smbd[1211]: [2019/01/10 10:22:56.268173,  0] smbd/negprot.c:706(reply_negprot)
Jan 10 10:22:56 smbd[1211]:   No protocol supported !
 
Getting this error in the log...change Samba from SMBV2 to SMBV1+SMBV2 and it goes away!
Did not notice this until 37E9 release
There were no changes in Samba/USB in 37E9. One of your clients is still set to use SMBV1.
 
Getting this error in the log...change Samba from SMBV2 to SMBV1+SMBV2 and it goes away!
Did not notice this until 37E9 release
There were no changes in Samba/USB in 37E9. One of your clients is still set to use SMBV1.
I'm guessing he was previously using a firmware from before this one:
Code:
374.43_37E1j9527  (21-November-2018) ARM SDK, MIPS,ARM KRACK
* CHANGED: samba: add min protocal statement for SMB1+SMB2 option
 
I'm guessing he was previously using a firmware from before this one:
Code:
374.43_37E1j9527  (21-November-2018) ARM SDK, MIPS,ARM KRACK
* CHANGED: samba: add min protocal statement for SMB1+SMB2 option

All the clients are Win 10 that don't support SMBV1 for some time now.

I have been using SMBV2 only option since it was introduced some time back
 
All the clients are Win 10 that don't support SMBV1 for some time now.

I have been using SMBV2 only option since it was introduced some time back

Learned something new... Win 10 box with OEM Win 10 still has SMBV1 enabled by default

Sorry for false alarm!
 
I'm guessing he was previously using a firmware from before this one:
Code:
374.43_37E1j9527 (21-November-2018) ARM SDK, MIPS,ARM KRACK
* CHANGED: samba: add min protocal statement for SMB1+SMB2 option
I actually added that because of a Win10 system where I wanted/enabled SMB1 and it was hit-or-miss in allowing browsing the network. Even though it should make no difference, explicilty adding the min protocol for the SMB1+SMB2 option cleared things up.
 
I’m considering using johns fork on one of my routers. I wonder if it has support for DoH DNS over HTTPS? What would be required to get that working?
 
John
is ordered mode still an issue for DoT use or should I be using round robin?

I had an issue last night being able to connect to Netflix and Hulu, but when I changed to ordered mode they seemed to start working. . dnssec testing still indicated all was well, but then I remembered something about an issue with using ordered mode.

Thanks in advance !
 
I'm having an odd problem with the OVPN server which cropped up recently. I recently upgraded 374.43_37E4j9527 on N66U.

My OVPN Server was setup and I used to connect to it from my laptop and my iPhone without an issue. After upgrading to the above firmware, my iPhone (iOS 12 running the latest OVPN client), refused to connect, kept saying Auth Error, Authentication failed. It was configured to use the "admin" login (username/password).

As a test, I setup a another user on the OVPN Server page and it works perfectly fine with this test user, but it refuses to login using the "admin" user. I've tried using "admin" as the username and also the alias username and also "root". It just won't login.

Did something change along the way that admin is no longer allowed to login over the OVPN server or am I missing a setting somewhere?
 
Not supported. Only DoT.

DoT port can get blocked by my ISP. DoH is more useful. So supposed I will have to keep using the outdated DNSCrypt for DoH :( hopefully it isn’t much less secure than stubby. Maybe stubby and Johns fork will someday embrace DoH.
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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