Proxy installed the first time a couple of days ago I tried the script and manually
Hi David,
your dnscrypt proxy 2 documentation says "IPV6 is disabled". Does that mean the script will deactivate ipv6 completely? Actually it would be nice to use ipv6 as well - is it possible to configure it as well?
I will reanimate my 1900ACS today and give it a try Thanks!
Is your isp set up for both ipv4 and ipv6? The .toml file is set up for ipv4 only. However, it can be adjusted for ipv6 if needed.
In LuCi gui, what is the dns forward set to? It should be set as 127.0.0.1#5300
Please run this command via ssh.
dnscrypt-proxy -config /etc/config/dnscrypt-proxy.toml -check
Then this command
dnscrypt-proxy -resolve google.com
this command returns the provider dns in the dns tab. redirection to 127.0.0.1 # 5300 is also disabled in the wan tab
I see spaces in this line -- 127.0.0.1 # 5300
No spaces.
Also, please copy the output of the commands, so I can see.
Best Regards,
Summary
root@OpenWrt:~# dnscrypt-proxy -resolve google.com
Resolving [google.com]
Domain exists: yes, 4 name servers found
Canonical name: google.com.
IP addresses: 2a00:1450:4011:809::1008, 173.194.44.0, 173.194.44.1, 173.194.44.3, 173.194.44.6, 173.194.44.9, 173.194.44.2, 173.194.44.7, 173.194.44.4, 173.194.44.14, 173.194.44.8, 173.194.44.5
TXT records: docusign=05958488-4752-4ef2-95eb-aa7ba8a3bd0e v=spf1 include:_spf.google.com ~all facebook-domain-verification=22rm551cu4k0ab0bxsw536tlds4h95
Resolver IP: 77.37.251.6 (broadband-77-37-251-6.ip.moscow.rt.ru.)
Okay, so the dnscrypt-proxy is working correctly.
Next, from a client on the LAN (doesn't matter if linux or windows). Please run the following command.
nslookup google.com
Summary
C: \ WINDOWS \ system32> nslookup google.com
╤hёthyo: OpenWrt.lan
Address: fd67: f43a: 4054 :: 1
Not credible answer:
: Google.com
Addresses: 74.125.131.100
74.125.131.101
74.125.131.102
74.125.131.113
74.125.131.138
74.125.131.139
Looks as though the client is requesting lookups via ipv6. The .toml file in the configuration is only set up for ipv4. Since my isp is IPv4 only, I never tested with IPv6.
Try editing the following line in your dnscrypt-proxy.toml. Set the following line to true.
Use servers reachable over IPv6 -- Do not enable if you don't have IPv6 connectivity
ipv6_servers = true
Also, the listen_addresses line, in the dnscrypt-proxy.toml, should probably be changed to listen on IPv6 as well.
thanks, I'll try
It seems to start working, but then again the provider returns
I tried to install it on Windows 10 and it seems to work without problems
i will try this as well soon and give you feedback. Thanks a lot david. I do have ipv4 and ipv6 (Dual Stack) so it would be nice to keep ipv6
New firmware has been uploaded to the server and is ready for download.
Kernel version = 4.14.75
WiFi driver = 10.3.8.0-20181008
Build = r8289
Upgrade 88W8997 firmware to = 8.4.0.51
Various other patches/updates as well.
Looks like the OpenWrt branding is clearly back in LuCi.
There is nothing under Statistics/graphs. The usual graphs are missing. The thermal, processor, etc are missing.
Thanks for letting me know. I'll take a look at the logs and see why they may have failed to build.
Ok. Thanks.
BTW -- If you know the package names, you can get them off LEDE snapshots and install them that way.
Could be placebo but WiFi on my iPhone X appears to be a bit faster (~100mbps).
Wifi is so inconsistent unless you live in a Faraday cage or something. To really know one has to be kind of scientific about it taking many samples over many days from the same distance with the same device over several builds to get somewhat of an idea. It still amazes me how many people give up because of a couple of speed tests right after installing LEDE for the first time, and then go back to stock FW.
Dealing with collectd / statistic as graphs I'm thinking this issue may be LuCi related because I'm not able to find anything in the build logs that indicated an issue compiling.
If someone has some spare time to install one of the daily builds, and install LuCi with collectd modules and see if it works or not would be helpful. If it isn't working then this issue needs to be reported.