False detection of network connectivity #2863
Replies: 3 comments 4 replies
-
|
Seems to work fine on Windows 11: |
Beta Was this translation helpful? Give feedback.
-
|
Hi, thanks for your input. |
Beta Was this translation helpful? Give feedback.
-
|
Frank @jedisct1, some more information that may help you figure out the problem. The network cable is off. LAN settings are set manually as prescribed by ISP.
$ dnscrypt-proxy.exe
[NOTICE] dnscrypt-proxy 2.1.12
[NOTICE] Network connectivity detectedLAN settings are left blank (DHCP is used).
$ dnscrypt-proxy.exe
[NOTICE] dnscrypt-proxy 2.1.12
[NOTICE] Network not available yet -- waiting... |
Beta Was this translation helpful? Give feedback.
-
|
I have a Mac. |
Beta Was this translation helpful? Give feedback.
-
|
I'm aware of that, Frank, you mentioned it before. But LAN depend on the same parameters (IP address, subnet, gateway, etc.) across all OSes. As you see in the screenshots, DNSCrypt detects correctly that there is no network connectivity when LAN settings are blank (i.e. when OS is expected to get them automatically via DHCP), but when LAN settings are set manually, there is a fallacy. |
Beta Was this translation helpful? Give feedback.
-
|
It seems similar to the scenario: You are in a LAN, and your WLAN is down. Due to the fact that the network is unavailable:
The retry intervals are chosen carefully for being available ASAP, and not to be too short. Offline could happen at anytime. The We don't have system level notifications for online states. Besides, Windows itself also often has false probing results. Those failure log messages may be bloated, but not critical. The big deal is that the WLAN is unavailable. Of course, good ideas are always welcome. |
Beta Was this translation helpful? Give feedback.
-
|
Re: @lifenjoiner You've written a lot, but I don't see how to apply it to the problem I reported. Detecting if there's a network connectivity is not a rocket science. Back in the 1990s we did it like that on Windows: rem checkweb.bat
ping -n 1 188.184.77.250 | find "TTL=" >nul
if errorlevel 1 echo Hmm, cern.ch is not accessible, check your Internet connection.I guess DNSCrypt has a similar mechanism which is regulated by two parameters, namely ## Address and port to try initializing a connection to, just to check
## if the network is up. It can be any address and any port, even if
## there is nothing answering these on the other side. Just don't use
## a local address, as the goal is to check for Internet connectivity.Going by what it says here, when the network cable is off, DNSCrypt shouldn't assert right upon launch that there is a network connectivity, but it does. As a result, the second problem arises: DNSCrypt, believing there is a network connectivity, tries to poll all listed DNS servers again and again. Common sense suggests that the detection mechanism is I look forward to trying any code patches and report back if they helped, just give me something. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Setup
dnscrypt-proxy.tomlProblem
dnscrypt-proxy.exeNetwork connectivity detected, which is confusing, to say the leastLogs
2.1.2 log
2.1.11 log
Expectations
I expected DNSCrypt to make sure there was no network connection available (for example, it would send a request to the address specified in the
netprobe_addressoption), then it would wait for a network connection and only after that it would start trying to poll DNS resolvers.Beta Was this translation helpful? Give feedback.
All reactions