From: "Dan Lüdtke" <mail@danrl.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [RFC] Handling multiple endpoints for a single peer
Date: Mon, 16 Jan 2017 16:01:55 +0100 [thread overview]
Message-ID: <B39E551B-33E0-45BA-91C1-68E3D438B816@danrl.com> (raw)
In-Reply-To: <CAHmME9pZLDieAabMhjDQHxpj_TDd5OLjNEUpQrraFvXA0g7gmA@mail.gmail.com>
Hi,
> On 8 Jan 2017, at 23:49, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>=20
> (send an encrypted out of band non-IP packet
> directly to a peer, for things like autoconfig) could play a nice role
> in this.
This is highly interesting! I should undust my gcc probably.
> One thing that comes to mind is how to detect when the local LAN peer
> comes back online there. Should wireguard just be trying to initiate a
> new handshake _always_, and eventually it will succeed and promote the
> cryptokey routing table entry to "active"?
Something like RetryTimeout=3DX comes to mind. And immediately raises =
the question how it is different from PersistentKeepalive? The latter =
one is misused to achieve exactly this sometimes.
The concrete problem Samuel described is one that could be solved by =
scoped addressing. This may be too theoretical for the actual scenario =
and circumstances.
Cheers,
Dan=
next prev parent reply other threads:[~2017-01-16 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 22:41 Baptiste Jonglez
2017-01-08 22:49 ` Jason A. Donenfeld
2017-01-09 2:37 ` Samuel Holland
2017-01-09 9:26 ` Baptiste Jonglez
2017-01-15 10:12 ` Jason A. Donenfeld
2017-01-09 7:00 ` Dave Taht
2017-01-09 9:47 ` Baptiste Jonglez
2017-01-15 10:06 ` Jason A. Donenfeld
2017-01-16 15:01 ` Dan Lüdtke [this message]
2017-01-09 8:46 ` Ameretat Reith
2017-01-15 10:17 ` 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=B39E551B-33E0-45BA-91C1-68E3D438B816@danrl.com \
--to=mail@danrl.com \
--cc=Jason@zx2c4.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).