From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Baptiste Jonglez <baptiste@bitsofnetworks.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [RFC] Handling multiple endpoints for a single peer
Date: Sun, 15 Jan 2017 11:06:33 +0100 [thread overview]
Message-ID: <CAHmME9rEwaPR5p8v5JpKAbZ_ihsKaXivn8cOJ0_iWPz5zNHUDA@mail.gmail.com> (raw)
In-Reply-To: <20170109094706.GA1315@lud.polynome.dn42>
On Mon, Jan 9, 2017 at 10:47 AM, Baptiste Jonglez
<baptiste@bitsofnetworks.org> wrote:
> This is not what I proposed. Endpoints do not need to be ordered, and you
Sorry, I read too fast evidently. That's a nice suggestion, indeed, of
sending multiple handshakes and seeing which one arrives first. If the
same exact handshake packet is sent to multiple IP, only the first one
to arrive will actually be replied to, due to the anti-replay attack
prevention rejecting the ones that arrive later. This, then, makes
implementation quite simple. Wonderful. So then, as you wrote, the
symmetric session would use the IP from the handshake for the
duration.
I'm still struggling to come up with a satisfactory solution for how
to manage "learned" new IPs from the roaming, to prevent the list from
getting too large. Fixed size LRU cycling perhaps?
next prev parent reply other threads:[~2017-01-15 9:56 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 [this message]
2017-01-16 15:01 ` Dan Lüdtke
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=CAHmME9rEwaPR5p8v5JpKAbZ_ihsKaXivn8cOJ0_iWPz5zNHUDA@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=baptiste@bitsofnetworks.org \
--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).