“If you build it, they will come.”Yes, that's what I was wondering. (Not that I'm objecting to having the option 42 anyway)
“If you build it, they will come.”Yes, that's what I was wondering. (Not that I'm objecting to having the option 42 anyway)
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.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.
Confirmed it works for me. May want to interlope and advise the non-forkers how to set it up.Google DNS now supports DoT.....the stubby resolvers file has been updated
stubby-update-resolvers.sh
Works for me too (have them set now).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.
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
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 !
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
Getting this error in the log...change Samba from SMBV2 to SMBV1+SMBV2 and it goes away!
Did not notice this until 37E9 release
I'm guessing he was previously using a firmware from before this one:There were no changes in Samba/USB in 37E9. One of your clients is still set to use SMBV1.
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
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 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
Not supported. Only DoT.I wonder if it has support for DoH DNS over HTTPS? What would be required to get that working?
Not supported. Only DoT.
What do you mean by "alias username"? Was the system account changed from admin to something else?I've tried using "admin" as the username and also the alias username...
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!