supports dnscrypt-proxy 2.0 is anyone considering supporting the new release in LEDE? I know about the dnscrypt-proxy 1.9.x pkg.
The new reference 2.0 server appears to be written in Go which is likely a problem. And it appears that dnscrypt-proxy 2.0 is required to use the 126.96.36.199 service if you want end-to-end encryption given the new method of identifying dnscrypt capable DNS servers.
But there is bug in the init script.
cache setting is always true.
Because it is already set to true in the config.
And the init script only sets cache to true if not 0.
And because off that it never gets set to false.
Thanks for the note. I fixed the cache logic -- I didn't notice that the default was set to true in the example config.
I prefer to minimize the changes to the config file -- if user choice matches example config default, then just leave the file alone and only modify it on changes. Your method would future proof the init, of course.
After looking at any place config files can be generated it's of course obvious where the "empty cloaking rules file in root directory" came from. This should be fixed as well.
i agree the posted instructions is very easy to follow provided you know which binary file is right for your router. the binary file is huge though but fortunately there is an option to compress its file size before transferring the binary file to the router. it's relatively easier to install and configure, compared to unbound, but perhaps it could be just a matter of personal preference.
From what I read. DNSCrypt v2 offers the best performance when using DoH (DNS-Over-HTTPS). There is also... well DNSCrypt servers so that's also a plus. The implementation with dnsmasq is well documented and tested. No need for unbound, caching is provided by both DNSCrypt and dnsmasq.
The drawback is the package size. Even after the compression, 2 MB is quite a lot for a single package. The whole kernel partition in 18.06 is about 4 MB.
The "minimum" should stand for all the basic services required to provide a satisfactory operation. I think 16 MB of Flash and 128 MB of RAM is more then enough for most use-cases. I would even consider 64 MB of RAM as "minimum".
If people want to install additional software and put more services on their routers, then they should get the "recommended" device. At that level I could agree with 32 MB of Flash and 256 MB of RAM.