Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Mike O'Connor" <mike@pineview.net>
Cc: Joshua Sjoding <joshua.sjoding@scjalliance.com>,
	 WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard for Windows tunnel deactivation after prolonged resolution failure during startup
Date: Fri, 29 Jan 2021 01:54:33 +0100	[thread overview]
Message-ID: <CAHmME9r_KsWNUWGF=bpqwO_bREtJRW49dso+N2WtbfGpa_P96g@mail.gmail.com> (raw)
In-Reply-To: <af71a4b2-989a-da04-2fa6-9467ec58997f@pineview.net>

On Fri, Jan 29, 2021 at 1:39 AM Mike O'Connor <mike@pineview.net> 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/nf-wininet-internetgetconnectedstate
> This to indicate if there is route-able service. It seem this is
> deprecated for windows 10.
> https://docs.microsoft.com/en-us/windows/win32/api/wininet/nf-wininet-internetcheckconnectiona
> There is reference to a win10 version, in the notes.

Yes, these functions are already used in the existing algorithm. That
doesn't answer any of the questions raised, however.

  reply	other threads:[~2021-01-29  0:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28 22:54 Joshua Sjoding
2021-01-29  0:23 ` Jason A. Donenfeld
2021-01-29  0:39   ` Mike O'Connor
2021-01-29  0:54     ` Jason A. Donenfeld [this message]
2021-01-29  1:02     ` Joshua Sjoding
2021-01-29 20:14       ` Jason A. Donenfeld

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHmME9r_KsWNUWGF=bpqwO_bREtJRW49dso+N2WtbfGpa_P96g@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=joshua.sjoding@scjalliance.com \
    --cc=mike@pineview.net \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).