From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Jörg Thalheim" <joerg@higgsboson.tk>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Multiple Endpoints
Date: Sun, 8 Jan 2017 23:19:53 +0100 [thread overview]
Message-ID: <CAHmME9o6KDKQu568VcJO1LC1Lw8guSCX5-gTud8wqSv_WA8R0w@mail.gmail.com> (raw)
In-Reply-To: <7ec50275-f586-763a-2f70-c68321ef9a17@higgsboson.tk>
On Sun, Jan 8, 2017 at 3:39 PM, J=C3=B6rg Thalheim <joerg@higgsboson.tk> wr=
ote:
>> I am also interested in multiple endpoints support, and I am preparing a
>> proposal that I will send soon.
>>
>
> Does your proposal also includes support for different address family? (s=
witch between ipv4/ipv6 and back)
So presumably what's needed is someway to specify multiple endpoints
per peer, and have the handshake retry mechanism cycle through the
list of endpoints, reordering them based on success. This doesn't seem
very difficult or complicated. I'll read some literature to see if
there have been some nice ideas on this in the past (multipath mosh
etc) and also examine whatever it is Baptiste has been cooking up.
next prev parent reply other threads:[~2017-01-08 22:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 14:43 em12345
2017-01-07 15:23 ` Jason A. Donenfeld
2017-01-07 16:45 ` em12345
2017-01-08 14:12 ` Baptiste Jonglez
2017-01-08 14:39 ` Jörg Thalheim
2017-01-08 21:22 ` Baptiste Jonglez
2017-01-08 22:19 ` Jason A. Donenfeld [this message]
2017-01-08 22:18 ` Jason A. Donenfeld
2017-01-08 22:57 ` Baptiste Jonglez
2017-01-08 23:00 ` Jason A. Donenfeld
2017-01-09 11:35 ` Varying source address and stateful firewalls (Was: Multiple Endpoints) Baptiste Jonglez
2017-01-10 4:32 ` Jason A. Donenfeld
2017-01-15 10:01 ` Multiple Endpoints Jason A. Donenfeld
2017-01-08 22: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=CAHmME9o6KDKQu568VcJO1LC1Lw8guSCX5-gTud8wqSv_WA8R0w@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=joerg@higgsboson.tk \
--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).