From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Jörg Thalheim" <joerg@higgsboson.tk>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] Dual stack?
Date: Sat, 31 Dec 2016 03:28:45 +0100 [thread overview]
Message-ID: <CAHmME9rxXHe+G+5oFF2LYGw=dnptdrrGmTEDwjtxBmev3_gNsw@mail.gmail.com> (raw)
In-Reply-To: <e636afa1-7826-47b6-c442-af33d955760e@higgsboson.tk>
On Thu, Dec 29, 2016 at 10:22 AM, J=C3=B6rg Thalheim <joerg@higgsboson.tk> =
wrote:
> On the other hand switching between dual-stack/ipv4 only networks/ipv6 on=
ly networks
> is problematic at the moment with the tools we have for roaming clients,
> because wireguard only supports one endpoint of one address family at the=
time.
> This might be partially fixable in future by observing the availability o=
f default routes
> in userspace (switch address family if it become unavailable). However th=
e optimal
> solution would be something like the happy eyeballs protocol (https://too=
ls.ietf.org/html/rfc6555),
> which is implemented in modern browser -
> only because somebody got a v6/v4 default route does not mean it is also =
route able.
> I don't know how the latter one would fit into the stateless concept of w=
ireguard.
> I currently help myself by using an dedicated routing protocoll.
Any suggestions on what the right behavior would be to support changes
in a dual stack environment?
next prev parent reply other threads:[~2016-12-31 2:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 11:39 [WireGuard] Demo Server: " Dan Lüdtke
2016-11-16 14:18 ` Jason A. Donenfeld
2016-11-16 14:38 ` Dan Lüdtke
2016-11-16 14:45 ` Dan Lüdtke
2016-11-16 14:49 ` Jason A. Donenfeld
2016-11-16 14:54 ` Dan Lüdtke
2016-11-16 15:09 ` Jason A. Donenfeld
2016-12-28 13:19 ` Maykel Moya
2016-12-29 9:22 ` [WireGuard] " Jörg Thalheim
2016-12-31 2:28 ` Jason A. Donenfeld [this message]
2016-12-31 2:27 ` [WireGuard] Demo Server: " 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='CAHmME9rxXHe+G+5oFF2LYGw=dnptdrrGmTEDwjtxBmev3_gNsw@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).