From: Nico Schottelius <nico.schottelius@ungleich.ch>
To: wireguard@lists.zx2c4.com
Subject: Re: [PATCH] wg-quick: Linux and FreeBSD: Add support to search domain in wg-quick
Date: Tue, 28 Jan 2020 13:52:41 +0100 [thread overview]
Message-ID: <878slreo9y.fsf@ungleich.ch> (raw)
In-Reply-To: <CAPWNY8W4oXesE53MMDNZC092xN8nK9iyKV-pcNpvMxcH1y4LuQ@mail.gmail.com>
I second Mantas in this regard - don't bloat wg-quick, but a DNS
search path is pretty standard to be submitted by "a network".
We are not talking dhcp boot options, even though NTP servers would
probably also make sense, if you see wireguard as providing a network.
Best,
Nico
Mantas Mikulėnas <grawity@gmail.com> writes:
> That might be true, but IMHO the list of search domains doesn't fall
> under "specialized options" – it is even deployed via DHCP and similar
> mechanisms almost as commonly as the list of DNS resolvers themselves,
> so if a VPN client supports the latter then it makes sense to support
> both.
>
>
> On Tue, Jan 28, 2020 at 12:37 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>>
>> I'm not so sure that we want to fill wg-quick(8) up with every dns
>> nob... If you have specialized networking requirements, wg-quick(8) is
>> probably not for you anyway.
>> _______________________________________________
>> WireGuard mailing list
>> WireGuard@lists.zx2c4.com
>> https://lists.zx2c4.com/mailman/listinfo/wireguard
--
Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-01-28 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 18:37 [PATCH] wg-quick: Linux and FreeBSD: Add support to search domain in wg-quick Ricardo Fraile
2020-01-28 10:36 ` Jason A. Donenfeld
2020-01-28 10:49 ` Mantas Mikulėnas
2020-01-28 12:52 ` Nico Schottelius [this message]
2020-01-28 21:39 ` Lech Perczak
2020-01-29 13:46 ` Ricardo Fraile
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=878slreo9y.fsf@ungleich.ch \
--to=nico.schottelius@ungleich.ch \
--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).