From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: Roaming between IPv4 and IPv6?
Date: Tue, 6 Mar 2018 23:59:39 +0100 [thread overview]
Message-ID: <db1cb140-af48-bc7b-801e-e2419f17761c@urlichs.de> (raw)
In-Reply-To: <87y3j4luw4.fsf@toke.dk>
On 06.03.2018 23:08, Toke Høiland-Jørgensen 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?
Frankly, IMHO that's a userspace problem. I don't want to see the kernel
driver burdened with complicated timeout logic, multiple address caching
and timeouts, and whatnot. Discovering which address is still reachable
when a link fails, re-checking DNS (you really should not use a resolved
address beyond its DNS timeout, esp. not when it fails to work), and all
those sundry tasks do not belong in the kernel.
--
-- Matthias Urlichs
prev parent reply other threads:[~2018-03-06 22:50 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
2018-03-07 0:31 ` Kalin KOZHUHAROV
2018-03-07 8:56 ` Toke Høiland-Jørgensen
2018-03-06 22:59 ` Matthias Urlichs [this message]
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=db1cb140-af48-bc7b-801e-e2419f17761c@urlichs.de \
--to=matthias@urlichs.de \
--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).