From: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
To: Matthias Urlichs <matthias@urlichs.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: DNS name resolution should not be done during configuration parsing.
Date: Tue, 19 Feb 2019 08:26:29 -0600 [thread overview]
Message-ID: <9ECFB5A1-9B31-4697-817A-887BF82D0E2A@lonnie.abelbeck.com> (raw)
In-Reply-To: <dda16c02-171c-6b44-8258-fda8d65d0543@urlichs.de>
> On Feb 19, 2019, at 1:22 AM, Matthias Urlichs <matthias@urlichs.de> 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.
> --
> -- Matthias Urlichs
Agreed. For example Jason's "reresolve-dns.sh" script. [1]
The missing piece is to keep "wg setconf" (et al.) from failing given a DNS failure on any peer.
Per this trivial patch.
https://raw.githubusercontent.com/astlinux-project/astlinux/master/package/wireguard/wireguard-0001-ignore-endpoint-dns-failure.patch
Peers without DNS endpoints (or successful DNS) would be allowed to start promptly as expected, and any failed DNS endpoints would be filled in later via a userspace WG monitor (ex. reresolve-dns.sh).
Lonnie
[1] https://git.zx2c4.com/WireGuard/tree/contrib/examples/reresolve-dns
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-02-19 14:26 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 [this message]
2019-02-19 15:45 ` Vincent Wiemann
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=9ECFB5A1-9B31-4697-817A-887BF82D0E2A@lonnie.abelbeck.com \
--to=lists@lonnie.abelbeck.com \
--cc=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).