From: Vincent Wiemann <vincent.wiemann@ironai.com>
To: wireguard@lists.zx2c4.com
Subject: Re: DNS name resolution should not be done during configuration parsing.
Date: Tue, 19 Feb 2019 16:45:58 +0100 [thread overview]
Message-ID: <ce051517-9325-824c-3299-ba08138e7912@ironai.com> (raw)
In-Reply-To: <dda16c02-171c-6b44-8258-fda8d65d0543@urlichs.de>
Hi Matthias,
On 19.02.2019 08:22, Matthias Urlichs wrote:
> We don't even need call-outs. We already have a netlink interface which
> a userspace client can use to monitor WG. Teach that client to
> re-resolve the name and to update the peer.
>
that's not a good design choice. A kernel VPN module should not depend
on a user space daemon for doing regular checks or a daemon running at
all. We want to be able to set it up using e.g. systemd-networkd and
don't have to care about it afterwards. Thus WireGuard should be able to
resolve the hostnames.
On 17.02.2019 19:26, Vincent Wiemann wrote:
> One could build up on
> https://www.kernel.org/doc/Documentation/networking/dns_resolver.txt ,
> but it's a lot of work and shouldn't be a goal before WireGuard becomes
> an upstream kernel module.
I'm pretty sure that's the way to go long-term.
Regards,
Vincent Wiemann
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-02-21 7:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 22:28 Eryk Wieliczko
2019-02-17 3:03 ` David Kerr
2019-02-17 4:08 ` Jeffrey Walton
2019-02-17 12:40 ` Eryk Wieliczko
2019-02-17 13:07 ` Jeffrey Walton
2019-02-17 13:15 ` Eryk Wieliczko
2019-02-19 3:01 ` zrm
2019-02-19 7:22 ` Matthias Urlichs
2019-02-19 14:26 ` Lonnie Abelbeck
2019-02-19 15:45 ` Vincent Wiemann [this message]
2019-02-21 7:59 ` Matthias Urlichs
2019-02-22 1:29 ` Vincent Wiemann
2019-02-19 14:58 ` David Kerr
2019-02-17 12:47 ` Eryk Wieliczko
2019-02-17 18:26 ` Vincent Wiemann
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=ce051517-9325-824c-3299-ba08138e7912@ironai.com \
--to=vincent.wiemann@ironai.com \
--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).