DonnyJohnny
Very Senior Member
the new installer is damn cool... with so much option and uninstaller included.
Thanks.
Thanks.
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.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.
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].
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?
Code: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].
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.
If I restart with this command after the boot the time stamp is perfectly accurate: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
/jffs/dnscrypt/manager dnscrypt-start
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?If I restart with this command after the boot the time stamp is perfectly accurate:Why can't this work at boot?Code:/jffs/dnscrypt/manager dnscrypt-start
That is a great freaking idea man!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?
If I restart with this command after the boot the time stamp is perfectly accurate:Why can't this work at boot?Code:/jffs/dnscrypt/manager dnscrypt-start
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
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!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?
I'm on 2.0.0, used the second to last installer prior to 2.0.2. Haven't had time to update yet.Note: I am running version 2.02
#!/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:For anyone interested, I create the below script to run on a minute-ly cronjob to make sure dnscrypt-proxy is ticking along nicely.
Code:#!/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
sed -i '/CheckDNSCrypt.sh/d' /jffs/syslog.log /tmp/syslog.log
Oh, maybe cron logs differently for you, im on 380.69_2The sed -i command above does not work for me but if I use this it works fine:Code:sed -i '/CheckDNSCrypt.sh/d' /jffs/syslog.log /tmp/syslog.log
This is what I got @bigeyes0x0 from the above command: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.
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
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!