DNScrypt dnscrypt installer for asuswrt

[Jack Yaz]

Just uploaded the fix for time. The problem is the script is run by the router with TZ variable set under 384 branch (dunno about 382, but likely same).

Also added monitoring watchdog for dnscrypt-proxy, so if it dies, it will be restarted. Basically the same thing as @Jack Yaz's crond job.

Looks good (browsed GitHub). Any chance of a configurable run as root or noroot? I run dnscrypt-proxy listening on an IP alias so that I can use DNSFilter to push things to router (for AB-Solution, which then goes to dnscrypt), or direct to dnscrypt (thus bypassing AB-Solution). I found the noroot option failed to bind on the alias, so I cut the noroot bit out of manager.

 

[skeal]

I can confirm that the time issue is fixed. Thank you again @bigeyes0x0 you are awesome!!

 

[bigeyes0x0]

Looks good (browsed GitHub). Any chance of a configurable run as root or noroot? I run dnscrypt-proxy listening on an IP alias so that I can use DNSFilter to push things to router (for AB-Solution, which then goes to dnscrypt), or direct to dnscrypt (thus bypassing AB-Solution). I found the noroot option failed to bind on the alias, so I cut the noroot bit out of manager.

It's a weird use case. I'll consider it but don't hold your breath on it.

 

[DonnyJohnny]

Hijack thread...
Just a note that dnscrypt-proxy 2.0.3 is out with Android binary..
https://github.com/jedisct1/dnscrypt-proxy/releases/tag/2.0.3
For anyone interested.. don’t ask how to use as I have not tested it... haha

 

[M@rco]

Just uploaded the fix for time. The problem is the script is run by the router with TZ variable set under 384 branch (dunno about 382, but likely same).

Didn't have time to reply to your request earlier @bigeyes0x0, but just ran the current installer and can confirm the timezone issue has been fixed. Thanks!

 

[bigeyes0x0]

Update to 2.0.3 and using a new timezone data package that would make any entware running package having the correct timestamp as well. There's also a new check for configuration file in various places to make sure that dnscrypt-proxy toml config is functional.

 

[Jack Yaz]

It's a weird use case. I'll consider it but don't hold your breath on it.

No worries, I'm happy to remember to tweak manager each time there's an update

 

[skeal]

Update to 2.0.3 and using a new timezone data package that would make any entware running package having the correct timestamp as well. There's also a new check for configuration file in various places to make sure that dnscrypt-proxy toml config is functional.

Once again sir you are awesome!! Really nice polish to a sweet script! Keep up the excellent work bud!

 

[noworries]

I used amtm (option 2) to update the dnscrypt v2.0.3 configuration (option 3) and found that I had to manually run:

sh /jffs/scripts/wan-start

for the configuration changes to take effect.

Also, dsncrypt is reporting log time stamps as several hours ahead of the correct 07:33. (I have updated the timezone in dnscrypt (option 4)). Time zone in router administration is correct and router's ntp is set to the default (pool.ntp.org).

Feb 25 07:33:41 adminusername: AB-Solution created br0:pixelserv 192.168.x.y via wan-start
Feb 25 15:33:41 dnscrypt-proxy[26945]: Stopped.
Feb 25 07:33:41 adminusername: Start dnscrypt-proxy
Feb 25 15:33:43 dnscrypt-proxy[27338]: Source [https://download.dnscrypt.info/resolvers-list/v2/public-resolvers.md] loaded
Feb 25 15:33:43 dnscrypt-proxy[27338]: dnscrypt-proxy 2.0.3
Feb 25 15:33:43 dnscrypt-proxy[27338]: Now listening to 127.0.0.1:65053 [UDP]
Feb 25 15:33:43 dnscrypt-proxy[27338]: Now listening to 127.0.0.1:65053 [TCP]
Feb 25 15:33:43 dnscrypt-proxy[27338]: [serverxx] OK (crypto v1) - rtt: 59ms
Feb 25 15:33:43 dnscrypt-proxy[27338]: Server with the lowest initial latency: serverxx (rtt: 59ms)
Feb 25 15:33:43 dnscrypt-proxy[27338]: dnscrypt-proxy is ready - live servers: 1
Feb 25 07:34:11 kernel: [BLOCKED - INBOUND] IN=eth0 OUT= MAC=00:....

Thanks

RT-AC88U, Merlin 384.3, amtm, Absolution, Skynet, Pixelserve, dnscrypt.

 

[DonnyJohnny]

I used amtm (option 2) to update the dnscrypt v2.0.3 configuration (option 3) and found that I had to manually run:

sh /jffs/scripts/wan-start

for the configuration changes to take effect.

Also, dsncrypt is reporting log time stamps as several hours ahead of the correct 07:33. (I have updated the timezone in dnscrypt (option 4)). Time zone in router administration is correct and router's ntp is set to the default (pool.ntp.org).

Feb 25 07:33:41 adminusername: AB-Solution created br0:pixelserv 192.168.x.y via wan-start
Feb 25 15:33:41 dnscrypt-proxy[26945]: Stopped.
Feb 25 07:33:41 adminusername: Start dnscrypt-proxy
Feb 25 15:33:43 dnscrypt-proxy[27338]: Source [https://download.dnscrypt.info/resolvers-list/v2/public-resolvers.md] loaded
Feb 25 15:33:43 dnscrypt-proxy[27338]: dnscrypt-proxy 2.0.3
Feb 25 15:33:43 dnscrypt-proxy[27338]: Now listening to 127.0.0.1:65053 [UDP]
Feb 25 15:33:43 dnscrypt-proxy[27338]: Now listening to 127.0.0.1:65053 [TCP]
Feb 25 15:33:43 dnscrypt-proxy[27338]: [serverxx] OK (crypto v1) - rtt: 59ms
Feb 25 15:33:43 dnscrypt-proxy[27338]: Server with the lowest initial latency: serverxx (rtt: 59ms)
Feb 25 15:33:43 dnscrypt-proxy[27338]: dnscrypt-proxy is ready - live servers: 1
Feb 25 07:34:11 kernel: [BLOCKED - INBOUND] IN=eth0 OUT= MAC=00:....

Thanks

RT-AC88U, Merlin 384.3, amtm, Absolution, Skynet, Pixelserve, dnscrypt.

Install the timezone and select your country, provided in the installer...
I also suggest you reboot router for the first time after installing the timezone.

 

[noworries]

Reboot synced the TZ. I still need to manually run wan-start to apply configuration changes, by design?

 

[mikecpt]

Morning John

Flashed your new build this morning, tried the script.

admin@RT-N66U-F830:/jffs/dnscrypt# ./dnscrypt-proxy -config /jffs/dnscrypt/dnscrypt-proxy.toml
[2018-02-17 12:20:54] [NOTICE] Source [https://download.dnscrypt.info/resolvers-list/v2/public-resolvers.md] loaded
[2018-02-17 12:20:54] [NOTICE] dnscrypt-proxy 2.0.0
[2018-02-17 12:20:54] [FATAL] listen udp 127.0.0.1:65053: errno -9

I then did a factory reset so I had nothing else installed (usually had AB solution etc) but again same result.

Have tried changing to my routers IP instead of 127.0.0.1 in config file, but same result

I then set it to port 53, which it told me was in use so couldn't be used.

I'm facing the same issue using a AC66U model with v 2.0.3 any ideas?

 

[Andy1932]

Sorry if this is completely user error, but I'm really struggling with this script.

First, my ultimate goal is to use this script to have all traffic run through the OpenDNS family server.(Option 7 in this script, I think.) Once setup, I should be able to install lonelycoder's adblocking script.

I'm not sure what I'm doing wrong, but after installing and rebooting, my 86u becomes non-responsive and I have to do a full reset. The last time I tried was basically a vanilla setup and it still didn't work.
I have DNS Filtering turned off and "Connect to DNS Server automatically set to on.

 

[Andy1932]

Sorry if this is completely user error, but I'm really struggling with this script.

First, my ultimate goal is to use this script to have all traffic run through the OpenDNS family server.(Option 7 in this script, I think.) Once setup, I should be able to install lonelycoder's adblocking script.

I'm not sure what I'm doing wrong, but after installing and rebooting, my 86u becomes non-responsive and I have to do a full reset. The last time I tried was basically a vanilla setup and it still didn't work.
I have DNS Filtering turned off and "Connect to DNS Server automatically set to on.

Just tried again. I can connect to my router, but not the internet. Getting this in the log:

Feb 13 19:01:11 ntp: start NTP update
Feb 13 19:01:13 admin: OpenDNS: Received error
Feb 13 19:01:31 ntp: start NTP update
Feb 13 19:01:39 admin: OpenDNS: Received error
Feb 13 19:01:51 ntp: start NTP update
Feb 13 19:02:05 admin: OpenDNS: Received error
Feb 13 19:02:11 ntp: start NTP update
Feb 13 19:02:31 ntp: start NTP update
Feb 13 19:02:51 ntp: start NTP update
Feb 13 19:03:11 ntp: start NTP update
Feb 13 19:03:31 ntp: start NTP update
Feb 13 19:03:51 ntp: start NTP update
Feb 13 19:04:12 ntp: start NTP update
Feb 13 19:04:32 ntp: start NTP update
Feb 13 19:04:52 ntp: start NTP update
Feb 13 19:05:12 ntp: start NTP update

 

[skeal]

Just tried again. I can connect to my router, but not the internet. Getting this in the log:

Feb 13 19:01:11 ntp: start NTP update
Feb 13 19:01:13 admin: OpenDNS: Received error
Feb 13 19:01:31 ntp: start NTP update
Feb 13 19:01:39 admin: OpenDNS: Received error
Feb 13 19:01:51 ntp: start NTP update
Feb 13 19:02:05 admin: OpenDNS: Received error
Feb 13 19:02:11 ntp: start NTP update
Feb 13 19:02:31 ntp: start NTP update
Feb 13 19:02:51 ntp: start NTP update
Feb 13 19:03:11 ntp: start NTP update
Feb 13 19:03:31 ntp: start NTP update
Feb 13 19:03:51 ntp: start NTP update
Feb 13 19:04:12 ntp: start NTP update
Feb 13 19:04:32 ntp: start NTP update
Feb 13 19:04:52 ntp: start NTP update
Feb 13 19:05:12 ntp: start NTP update

This happens if you have no working dns. The setting connect to dns automatically may be problematic if set to yes. This setting looks to your ip provider for dns information. Don't define any dns settings in Lan tab. You can try to set your Wan dns setting to one server your routers ip. Example: 192.168.x.x DnsCrypt if installed right should over ride anything defined here but its a good place to start. Nothing will work without NTP working. Time is very important to a router.

 

[Andy1932]

This happens if you have no working dns. The setting connect to dns automatically may be problematic if set to yes. This setting looks to your ip provider for dns information. Don't define any dns settings in Lan tab. You can try to set your Wan dns setting to one server your routers ip. Example: 192.168.x.x DnsCrypt if installed right should over ride anything defined here but its a good place to start. Nothing will work without NTP working. Time is very important to a router.

Thanks. LAN DNS is empty.

Tried 192.168.1.1 and also 8.8.8.8 in the WAN DNS. Still nothing.

 

[skeal]

Thanks. LAN DNS is empty.

Tried 192.168.1.1 and also 8.8.8.8 in the WAN DNS. Still nothing.

In the setup did you choose to let this program resolve all dns queries?

 

[Andy1932]

In the setup did you choose to let this program resolve all dns queries?

Yes

 

[skeal]

Thanks. LAN DNS is empty.

Tried 192.168.1.1 and also 8.8.8.8 in the WAN DNS. Still nothing.

Have you tried other servers in dnscrypt?

 

[Andy1932]

Have you tried other servers in dnscrypt?

Trying now.


Still not working.

Going off memory:

Install dnscript
Resolve all dns queries
No ipv6
Manual setup. Selection 8 this time
p2
2 on log
8.8.8.8 for ntp

I think that’s it.