diff options
| author |   Jason A. Donenfeld <Jason@zx2c4.com> | 2022-01-17 13:55:53 +0100 |
|---|---|---|
| committer | Jason A. Donenfeld <Jason@zx2c4.com> | 2022-01-17 13:59:48 +0100 |
| commit | b75cc38c60e36e1117bb40fd4ac78c44f1aae1f6 (patch) | |
| tree | 5c3e197966b91ab8fcaf6f3c765f80938493906e /ui/tunnelstatusimageprovider.go | |
| parent | global: bump date (diff) | |
| download | wireguard-windows-b75cc38c60e36e1117bb40fd4ac78c44f1aae1f6.tar.xz wireguard-windows-b75cc38c60e36e1117bb40fd4ac78c44f1aae1f6.zip | |
conf: do not examine connectivity state at boot
It turns out that checking for internet connectivity is not really a
reliable way of knowing whether the WSAHOST_NOT_FOUND is legitimate or
not. So just give up on that approach, assume WSAHOST_NOT_FOUND is
always illegitimate at boot, and loop for a long time. This might induce
annoyances for admins who want to kill legitimate WSAHOST_NOT_FOUND
services that keep trying again, but they'll just have to wait for two
minutes.
Reported-by: Simon Rozman <simon@rozman.si>
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Diffstat (limited to 'ui/tunnelstatusimageprovider.go')
0 files changed, 0 insertions, 0 deletions