DNScrypt dnscrypt installer for asuswrt

[DonnyJohnny]

the new installer is damn cool... with so much option and uninstaller included.
Thanks.

 

[john9527]

Morning John

Flashed your new build this morning, tried the script.

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.

Sigh.....one last try....there's a 380.69_2d version for download. Picked up one more commit above 2.26.27. To go any further requires backporting some more new function calls introduced up to 2.6.39 and is way beyond anything I could tackle.

 

[Jack Yaz]

Just had dnscrypt-proxy v2 stop working with nothing in the log, had to restart it from the manager. Memory flushing is off.

I may make a cronjob to run any keep an eye on it.

 

[miroco]

Hi Guys,

I'm seeing a weird behaviour in my system log. Despite choosing the same timezone for dnscrypt-proxy as for my router, it's 1 h off. Maybe it's a DST issue. But in which case the problem should manifest itself during the period when DST is active. I'm in Sweden and use Stockholm. I also tried Oslo, Berlin and Paris, all within the CET timezone and with the same result. I did reboot the router after each change in the dnscrypt-proxy setting. Any ideas?

Feb 20 14:55:28 kernel: usbcore: registered new interface driver usbfs
Feb 20 14:55:28 kernel: usbcore: registered new interface driver hub
Feb 20 14:55:28 kernel: usbcore: registered new device driver usb
Feb 20 14:55:28 syslog: module ledtrig-usbdev not found in modules.dep
Feb 20 13:55:28 dnscrypt-proxy[616]: [bn-fr0] OK (crypto v1) - rtt: 37ms
Feb 20 14:55:28 syslog: module leds-usb not found in modules.dep
Feb 20 13:55:28 dnscrypt-proxy[616]: [bn-nl0] OK (crypto v1) - rtt: 26ms
Feb 20 13:55:28 dnscrypt-proxy[616]: [cpunks-ru] TIMEOUT
Feb 20 14:55:28 kernel: SCSI subsystem initialized
Feb 20 14:55:28 kernel: csw_retry 100
Feb 20 14:55:28 kernel: Initializing USB Mass Storage driver...
Feb 20 14:55:28 kernel: usbcore: registered new interface driver usb-storage
Feb 20 14:55:28 kernel: USB Mass Storage support registered.
Feb 20 14:55:29 kernel: Tuxera FAT 12/16/32 driver version 3015.1.29.5_1 [Flags: R/W MODULE].

 

[M@rco]

Hi Guys,

I'm seeing a weird behaviour in my system log. Despite choosing the same timezone for dnscrypt-proxy as for my router, it's 1 h off. Maybe it's a DST issue. But in which case the problem should manifest itself during the period when DST is active. I'm in Sweden and use Stockholm. I also tried Oslo, Berlin and Paris, all within the CET timezone and with the same result. I did reboot the router after each change in the dnscrypt-proxy setting. Any ideas?

Feb 20 14:55:28 kernel: usbcore: registered new interface driver usbfs
Feb 20 14:55:28 kernel: usbcore: registered new interface driver hub
Feb 20 14:55:28 kernel: usbcore: registered new device driver usb
Feb 20 14:55:28 syslog: module ledtrig-usbdev not found in modules.dep
Feb 20 13:55:28 dnscrypt-proxy[616]: [bn-fr0] OK (crypto v1) - rtt: 37ms
Feb 20 14:55:28 syslog: module leds-usb not found in modules.dep
Feb 20 13:55:28 dnscrypt-proxy[616]: [bn-nl0] OK (crypto v1) - rtt: 26ms
Feb 20 13:55:28 dnscrypt-proxy[616]: [cpunks-ru] TIMEOUT
Feb 20 14:55:28 kernel: SCSI subsystem initialized
Feb 20 14:55:28 kernel: csw_retry 100
Feb 20 14:55:28 kernel: Initializing USB Mass Storage driver...
Feb 20 14:55:28 kernel: usbcore: registered new interface driver usb-storage
Feb 20 14:55:28 kernel: USB Mass Storage support registered.
Feb 20 14:55:29 kernel: Tuxera FAT 12/16/32 driver version 3015.1.29.5_1 [Flags: R/W MODULE].

I can confirm this. Hadn't noticed it before, as I never had issues. It has changed somehow, as it wasn't off by an hour in previous versions. I'm in the same timezone btw, using 425 Europe, Amsterdam. Funny part is that in early stages while dnscrypt-proxy v2 was still in beta, most people had issues with their time stamps, except those who where in CET. Apparently it's our turn now. @bigeyes0x0, has there been a change in the installer script or should I open an issue with Frank?

Feb 20 13:28:02 custom_script: Running /jffs/scripts/dnsmasq.postconf (args: /etc/dnsmasq.conf)
Feb 20 12:28:02 dnscrypt-proxy[749]: Now listening to 127.0.0.1:65053 [UDP]
Feb 20 12:28:02 dnscrypt-proxy[749]: Now listening to 127.0.0.1:65053 [TCP]
Feb 20 12:28:02 dnscrypt-proxy[749]: [cisco] OK (crypto v1) - rtt: 12ms
Feb 20 12:28:02 dnscrypt-proxy[749]: Server with the lowest initial latency: cisco (rtt: 12ms)
Feb 20 12:28:02 dnscrypt-proxy[749]: dnscrypt-proxy is ready - live servers: 1
Feb 20 13:28:03 WAN_Connection: WAN was restored.

 

[bigeyes0x0]

@all Script updated to 2.0.2. I haven't tested it but it should work as long as the original binary works.

Regarding time issue, nothing changed on my side. It's not a problem on Frank's side as well. Might be a problem with my zoneinfo.zip from Go package. Maybe you guys can check this for me by downloading the zoneinfo package according to your location from http://pkg.entware.net/binaries/armv7/Packages.html . Extracting your zoneinfo file according to your location the replace this file /jffs/dnscrypt/localtime then reboot to see how it goes.

 

[DonnyJohnny]

Omg.. didn’t notice since when... my timezone is correct. Gmt+8...
Likely after upgrading to 384.4 alpha 1.
Dirty upgrade.
Currently on 2.0.2

 

[skeal]

Omg.. didn’t notice since when... my timezone is correct. Gmt+8...
Likely after upgrading to 384.4 alpha 1.
Dirty upgrade.
Currently on 2.0.2

If I restart with this command after the boot the time stamp is perfectly accurate:

/jffs/dnscrypt/manager dnscrypt-start

Why can't this work at boot?

 

[DonnyJohnny]

If I restart with this command after the boot the time stamp is perfectly accurate:

/jffs/dnscrypt/manager dnscrypt-start

Why can't this work at boot?

Hmm.. likely ntp not updated at boot time... maybe if that is the case, maybe can put the command at post-mount to reload it?

 

[skeal]

Hmm.. likely ntp not updated at boot time... maybe if that is the case, maybe can put the command at post-mount to reload it?

That is a great freaking idea man!

 

[M@rco]

If I restart with this command after the boot the time stamp is perfectly accurate:

/jffs/dnscrypt/manager dnscrypt-start

Why can't this work at boot?

@skeal, you're absolutely right!

Feb 21 17:30:50 dnscrypt-proxy[612]: Stopped.
Feb 21 18:30:51 dnscrypt-proxy[14274]: Source [https://download.dnscrypt.info/resolvers-list/v2/public-resolvers.md] loaded
Feb 21 18:30:51 dnscrypt-proxy[14274]: dnscrypt-proxy 2.0.0
Feb 21 18:30:51 dnscrypt-proxy[14280]: Source [https://download.dnscrypt.info/resolvers-list/v2/public-resolvers.md] loaded
Feb 21 18:30:51 dnscrypt-proxy[14280]: dnscrypt-proxy 2.0.0
Feb 21 18:30:51 dnscrypt-proxy[14291]: Source [https://download.dnscrypt.info/resolvers-list/v2/public-resolvers.md] loaded
Feb 21 18:30:51 dnscrypt-proxy[14291]: dnscrypt-proxy 2.0.0
Feb 21 18:30:51 dnscrypt-proxy[14291]: Now listening to 127.0.0.1:65053 [UDP]
Feb 21 18:30:51 dnscrypt-proxy[14291]: Now listening to 127.0.0.1:65053 [TCP]
Feb 21 18:30:51 dnscrypt-proxy[14291]: [cisco] OK (crypto v1) - rtt: 10ms
Feb 21 18:30:51 dnscrypt-proxy[14291]: Server with the lowest initial latency: cisco (rtt: 10ms)
Feb 21 18:30:51 dnscrypt-proxy[14291]: dnscrypt-proxy is ready - live servers: 1

@bigeyes0x0, this wasn't the case in earlier releases. Are you sure nothing has changed in the installer? Haven't tried your suggestion yet, but given the fact that restarting fixes it, leads me to believe that the cause lies elsewhere?

 

[skeal]

Hmm.. likely ntp not updated at boot time... maybe if that is the case, maybe can put the command at post-mount to reload it?

Ok so your advice worked as planned. The script runs again with the right time stamp. I'm sure we can get this right. You guys are awesome at ironing out these issues. Keep up the great work!
Note: I am running version 2.02

 

[M@rco]

Note: I am running version 2.02

I'm on 2.0.0, used the second to last installer prior to 2.0.2. Haven't had time to update yet.

 

[Jack Yaz]

For anyone interested, I create the below script to run on a minute-ly cronjob to make sure dnscrypt-proxy is ticking along nicely.

File name CheckDNSCrypt.sh

#!/bin/sh

if [ -z $(pidof dnscrypt-proxy) ] ; then
    sh /jffs/dnscrypt/manager dnscrypt-start
    logger -st "DNSCryptCheck" "DNSCrypt has been restarted"
fi

sed -i "/cmd \/jffs\/scripts\/CheckDNSCrypt.sh/d" /tmp/syslog.log-1 /tmp/syslog.log

 

[skeal]

For anyone interested, I create the below script to run on a minute-ly cronjob to make sure dnscrypt-proxy is ticking along nicely.

#!/bin/sh

if [ -z $(pidof dnscrypt-proxy) ] ; then
    sh /jffs/dnscrypt/manager dnscrypt-start
    logger -st "DNSCryptCheck" "DNSCrypt has been restarted"
fi

sed -i "/cmd \/jffs\/scripts\/CheckDNSCrypt.sh/d" /tmp/syslog.log-1 /tmp/syslog.log

The sed -i command above does not work for me but if I use this it works fine:

sed -i '/CheckDNSCrypt.sh/d' /jffs/syslog.log /tmp/syslog.log

 

[bigeyes0x0]

Can you guys with time issue, send me the result of this command:

nvram show|grep time_zone

And also tell me the timezones you selected in this script and in your router UI.

 

[Jack Yaz]

The sed -i command above does not work for me but if I use this it works fine:

sed -i '/CheckDNSCrypt.sh/d' /jffs/syslog.log /tmp/syslog.log

Oh, maybe cron logs differently for you, im on 380.69_2

 

[skeal]

Can you guys with time issue, send me the result of this command:

nvram show|grep time_zone

And also tell me the timezones you selected in this script and in your router UI.

This is what I got @bigeyes0x0 from the above command:

 nvram show|grep time_zone
time_zone_dst=0
size: 65730 bytes (65342 left)
time_zone_x=GMT6
time_zone_dstoff=M3.2.0/2, M10.2.0/2
time_zone=CST6_2

My timezone is america/regina which is number 190 in the list. This zone is -6

 

[miroco]

These are my results.

473) Europe/Stockholm

admin@RT-AC68U:/tmp/home/root# nvram show|grep time_zone
size: 51424 bytes (14112 left)
time_zone_dst=1
time_zone_x=MET-1DST,M3.2.0/2,M10.2.0/2
time_zone_dstoff=M3.2.0/2,M10.2.0/2
time_zone=MET-1DST

 

[bigeyes0x0]

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.