Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Joshua Sjoding <joshua.sjoding@scjalliance.com>
Cc: 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 21:14:02 +0100	[thread overview]
Message-ID: <CAHmME9ozVtp6UCpksn9_nfb30nGMWqT2b2dYTHGqMi+jLg6oMQ@mail.gmail.com> (raw)
In-Reply-To: <CALaUSusBmLSAE3rYavFtEW5Bp+KoRVLfKFXga7Po+46KSGPbhg@mail.gmail.com>

Hey Joshua,

Ahhh that's a good point -- users sometimes must manually connect. And
in this case, you're expecting for WireGuard to resolve those hosts
and turn on the second a connection is available.

I suppose it should be possible to detect when we're started at boot
(not sure how yet) and retry indefinitely in that case. That's a
little tricky to program because I'd still like the user to be able to
terminate the service. But not impossible. I'll think on it. And I've
added it to the TODO:
https://docs.google.com/document/d/1-jlULsy1uDun-b4ow3RvnNQJU5K_pAv87sqDAfK66Kk/edit

In case you're curious, the code in question is here at the moment:
https://git.zx2c4.com/wireguard-windows/tree/conf/dnsresolver_windows.go

Jason

      reply	other threads:[~2021-01-29 20:14 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
2021-01-29  1:02     ` Joshua Sjoding
2021-01-29 20:14       ` Jason A. Donenfeld [this message]

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=CAHmME9ozVtp6UCpksn9_nfb30nGMWqT2b2dYTHGqMi+jLg6oMQ@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=joshua.sjoding@scjalliance.com \
    --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).