search

DNSCrypt / dnscrypt-proxy

dnscrypt-proxy 2 - A flexible DNS proxy, with support for encrypted DNS protocols.
https://dnscrypt.info
ISC License
11.5k stars 1.02k forks source link

Little Snitch blocks the network test #444

Closed gcpmusic closed 6 years ago

gcpmusic commented 6 years ago

Many thanks for the update. However I have the follow issue from my log file:

[2018-05-13 20:39:34] [NOTICE] dnscrypt-proxy 2.0.12
[2018-05-13 20:39:34] [NOTICE] Loading the set of whitelisting rules from [/Users/gc/Documents/dnscrypt-proxy/whitelist.txt]
[2018-05-13 20:39:34] [NOTICE] Loading the set of blocking rules from [/Users/gc/Documents/dnscrypt-proxy/blacklist.txt]
[2018-05-13 20:39:34] [NOTICE] Loading the set of IP blocking rules from [/Users/gc/Documents/dnscrypt-proxy/ip-blacklist.txt]
[2018-05-13 20:39:34] [NOTICE] Now listening to 127.0.0.54:53 [UDP]
[2018-05-13 20:39:34] [NOTICE] Now listening to 127.0.0.54:53 [TCP]
[2018-05-13 20:39:34] [NOTICE] Now listening to [::1]:53 [UDP]
[2018-05-13 20:39:34] [NOTICE] Now listening to [::1]:53 [TCP]
[2018-05-13 20:39:34] [NOTICE] [cloudflare] OK (DoH) - rtt: 25ms
[2018-05-13 20:39:34] [NOTICE] [cs-rome] OK (crypto v1) - rtt: 41ms
[2018-05-13 20:39:34] [NOTICE] Server with the lowest initial latency: cloudflare (rtt: 25ms)
[2018-05-13 20:39:34] [NOTICE] dnscrypt-proxy is ready - live servers: 2

so far so good from now on the follow two lines keep going for ever!

[2018-05-13 20:39:51] [ERROR] Timeout while waiting for network connectivity
[2018-05-13 20:39:51] [NOTICE] Source [public-resolvers.md] loaded

the previous version 2.0.11 was working great for me. There is any way to revert back meantime the above issue is solved?

Thank you in advance.

jedisct1 commented 6 years ago

Can you start it with the example configuration file, without any changes except perhaps the resolvers list?

gcpmusic commented 6 years ago

I reproduced exactly the some steps I did after the update and strangely now is fine :-) thank you. However still I got an error on initial startup even on the default.toml and take a while to activate: [2018-05-15 12:32:37] [NOTICE] Network not available yet -- waiting... [2018-05-15 12:33:09] [ERROR] Timeout while waiting for network connectivity [2018-05-15 12:33:09] [NOTICE] Source [public-resolvers.md] loaded [2018-05-15 12:33:09] [NOTICE] dnscrypt-proxy 2.0.12 all the rest is fine.

Start & stop many time the service to check and always the some, also on a differrent computer and setup. v. 2.0.11 was very snappy. Thank you

jedisct1 commented 6 years ago

Do you have Little Snitch or some other blocker installed?

gcpmusic commented 6 years ago

Yes I tried with LS off and is the some. There is any change since v. 2.0.11 here. Thanks

jedisct1 commented 6 years ago

Little Snitch is still intercepting network-related system calls, that don't behave as expected any more.

Try adding this to the configuration file:

netprobe_address = '9.9.9.9:9'

It can actually be any address and port. Nothing will actually be sent to that address.

gcpmusic commented 6 years ago

Sorry for the delay. Ok I added the line as suggested and DNSCrypt start it up very fast without any errors. However the [NOTICE] Source [public-resolvers.md] loaded repeat again indefinitelly! Thank you

Log: [2018-05-16 21:59:20] [NOTICE] Stopped. [2018-05-16 21:59:21] [NOTICE] Source [public-resolvers.md] loaded [2018-05-16 21:59:21] [NOTICE] dnscrypt-proxy 2.0.12 [2018-05-16 21:59:21] [NOTICE] Loading the set of whitelisting rules from [/Users/gc/Documents/dnscrypt-proxy/whitelist.txt] [2018-05-16 21:59:21] [NOTICE] Loading the set of blocking rules from [/Users/gc/Documents/dnscrypt-proxy/blacklist.txt] [2018-05-16 21:59:21] [NOTICE] Loading the set of IP blocking rules from [/Users/gc/Documents/dnscrypt-proxy/ip-blacklist.txt] [2018-05-16 21:59:21] [NOTICE] Now listening to 127.0.0.54:53 [UDP] [2018-05-16 21:59:21] [NOTICE] Now listening to 127.0.0.54:53 [TCP] [2018-05-16 21:59:22] [NOTICE] [cloudflare] OK (DoH) - rtt: 42ms [2018-05-16 21:59:22] [NOTICE] [cs-rome] OK (crypto v1) - rtt: 42ms [2018-05-16 21:59:22] [NOTICE] Server with the lowest initial latency: cloudflare (rtt: 42ms) [2018-05-16 21:59:22] [NOTICE] dnscrypt-proxy is ready - live servers: 2 [2018-05-16 21:59:39] [NOTICE] Source [public-resolvers.md] loaded [2018-05-16 21:59:39] [NOTICE] Source [public-resolvers.md] loaded [2018-05-16 21:59:40] [NOTICE] Source [public-resolvers.md] loaded etc.. forever! Please note that the some occurs on the default.toml without the log path change.

jedisct1 commented 6 years ago

The default address is 1.0.0.0:0. If this prevents Little Snitch from working transparently, you should report this as a bug to them. This is a valid address.

You can increase the log level to possibly get more messages. Or even define DEBUG=1 before starting the proxy from the command line.

gcpmusic commented 6 years ago

Issue solved :-) Added netprobe_address = '9.9.9.9:9' line and now it start just in 1 second! (see log) The problem was a DNSCrypt-Menu loaded via bitbar that was broken with 2.0.12 Work great also with 2.0.13 update. Thank you.

[2018-05-17 03:14:36] [NOTICE] Stopped. [2018-05-17 03:15:08] [NOTICE] Source [public-resolvers.md] loaded [2018-05-17 03:15:08] [NOTICE] dnscrypt-proxy 2.0.13 [2018-05-17 03:15:08] [NOTICE] Loading the set of whitelisting rules from [/Users/gc/Documents/dnscrypt-proxy/whitelist.txt] [2018-05-17 03:15:08] [NOTICE] Loading the set of blocking rules from [/Users/gc/Documents/dnscrypt-proxy/blacklist.txt] [2018-05-17 03:15:08] [NOTICE] Loading the set of IP blocking rules from [/Users/gc/Documents/dnscrypt-proxy/ip-blacklist.txt] [2018-05-17 03:15:08] [NOTICE] Now listening to 127.0.0.54:53 [UDP] [2018-05-17 03:15:08] [NOTICE] Now listening to 127.0.0.54:53 [TCP] [2018-05-17 03:15:08] [NOTICE] [cloudflare] OK (DoH) - rtt: 12ms [2018-05-17 03:15:08] [NOTICE] [cs-rome] OK (crypto v1) - rtt: 32ms [2018-05-17 03:15:08] [NOTICE] Server with the lowest initial latency: cloudflare (rtt: 12ms) [2018-05-17 03:15:08] [NOTICE] dnscrypt-proxy is ready - live servers: 2 End

rr0ss0rr commented 6 years ago

and what was the issue with DNSCrypt-Menu

gcpmusic commented 6 years ago

. . that after the last line [NOTICE] dnscrypt-proxy is ready - live servers: 2 carrion to load the [NOTICE] Source [public-resolvers.md] loaded line for ever.

For now I just disabled the menubar plugin.

dankm commented 6 years ago

This is also an issue on the BSDs. They all assume that UDP port 0 is invalid when connecting to it.

jedisct1 commented 6 years ago

@dankm Ouch, that's a more serious problem.

jedisct1 commented 6 years ago

Ok, the default netprobe address has been changed.

Thanks!

dankm commented 6 years ago

Thanks. master works now unmodified!