Someone could power the laptop up but wait hours before they connect
it to their hotspot. For scenarios like that the current algorithm
seems insufficient.
My preference would be to listen for network changes while in a failed
state, then re-run the existing algorithm whenever a network
connect/di
On Fri, Jan 29, 2021 at 1:39 AM Mike O'Connor wrote:
>
> Hi Jason
>
> I'm not a windows users so can not test, but it seems to me that
> Microsoft have API's to indicate the network status.
>
> This to indicate if there is a connection
> https://docs.microsoft.com/en-us/windows/win32/api/wininet/n
Hi Jason
I'm not a windows users so can not test, but it seems to me that
Microsoft have API's to indicate the network status.
This to indicate if there is a connection
https://docs.microsoft.com/en-us/windows/win32/api/wininet/nf-wininet-internetgetconnectedstate
This to indicate if there is
Hi Joshua,
Thanks for the bug report. Windows is usually all about heuristics.
Here's the current algorithm:
- If the system has booted within the last 4 minutes, it retries 40
times. Otherwise it retries 10 times.
- If the resolution fails with a temporary error, or if it fails with
a permanent
Hi,
I am trying to update Wireguard to latest version on windows but could
not build because of missing dependencies i686-w64-mingw32-windres.
I can't go back to older commit such as 0.3.4 (a5102ca - version:
bump) because of go mod has reference to unknown revision
76ef01985b1c.
Please suggest ho
