From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Roaming between IPv4 and IPv6?
Date: Tue, 6 Mar 2018 23:14:07 +0100 [thread overview]
Message-ID: <CAHmME9ogYdW3AUUC6qQRkmq2ndEqk0MHxt0sVF=BKvdNQKZO3A@mail.gmail.com> (raw)
In-Reply-To: <87y3j4luw4.fsf@toke.dk>
On Tue, Mar 6, 2018 at 11:08 PM, Toke H=C3=B8iland-J=C3=B8rgensen <toke@tok=
e.dk> wrote:
> I think the idea of configuring both v4 and v6 on startup and caching
> them is a reasonable idea. Maybe even configure all available addresses
> when doing the initial DNS lookup? Or is that awkward to do?
You mean taking one v4 and one v6? That's probably possible. Since
getaddrinfo has complicated ordering logic, this probably be best
expressed as something like "endpoint" and "secondary endpoint" when
told by userspace, with them then being swapped when the FIB complains
about trying to route to one of them.
next prev parent reply other threads:[~2018-03-06 22:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 21:53 Toke Høiland-Jørgensen
2018-03-06 21:57 ` Jason A. Donenfeld
2018-03-06 22:08 ` Toke Høiland-Jørgensen
2018-03-06 22:14 ` Jason A. Donenfeld [this message]
2018-03-07 0:31 ` Kalin KOZHUHAROV
2018-03-07 8:56 ` Toke Høiland-Jørgensen
2018-03-06 22:59 ` Matthias Urlichs
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='CAHmME9ogYdW3AUUC6qQRkmq2ndEqk0MHxt0sVF=BKvdNQKZO3A@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=toke@toke.dk \
--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).