Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Luis Ressel <aranea@aixah.de>
To: Matthias Urlichs <matthias@urlichs.de>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Endpoint address dns resolution - option to prefer IPv6 or IPv4
Date: Sat, 14 Mar 2020 18:03:35 +0000	[thread overview]
Message-ID: <20200314180335.4jx67dqm25spla5q@vega> (raw)
In-Reply-To: <303a9e73-23a9-4d87-b18e-51c8bf137e1d@urlichs.de>

On Sat, Mar 14, 2020 at 06:08:35PM +0100, Matthias Urlichs wrote:
> Ideally some background process forked by `wg` or `wg-quick` should set
> the first address, monitor the peer, and use the next one if it hasn't
> been established after some configurable number of seconds (or when the
> keepalive fails). Bonus points for re-resolving the address when it expires.

Yes, trying the ips in order until a tunnel can be established is
certainly a good idea, and in fact what the relevant standards
recommend, but so far noone has bothered to implement it.

Running a daemon that periodically re-resolves the host and sets the
endpoint to its current ip, on the other hand, would interfere with
wireguard's transparent roaming support, so wg(8) isn't ever going to do
that. Of course, you can easily do this yourself if it makes sense for
your setup.

Cheers,
Luis

      reply	other threads:[~2020-03-14 18:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13 14:52 Torsten Krah
2020-03-14  7:40 ` Stefan Tatschner
2020-03-14 14:53   ` Torsten Krah
     [not found] ` <CAADpXXY7ajNwRoF1sivACxUfFj-SpWf6o6+1Uq2N0XzEp3bvTw@mail.gmail.com>
2020-03-14 14:51   ` Torsten Krah
2020-03-16  5:05     ` Roman Mamedov
2020-03-16  8:30       ` Torsten Krah
2020-03-14 16:52 ` Luis Ressel
2020-03-14 17:08   ` Matthias Urlichs
2020-03-14 18:03     ` Luis Ressel [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=20200314180335.4jx67dqm25spla5q@vega \
    --to=aranea@aixah.de \
    --cc=matthias@urlichs.de \
    --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).