I used amtm (option 2) to update the dnscrypt v2.0.3 configuration (option 3) and found that I had to manually run:
Code:
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).
Code:
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.