Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Bzzzz <lazyvirus@gmx.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: openresolv dependency
Date: Mon, 22 May 2017 04:11:07 +0200	[thread overview]
Message-ID: <20170522041107.7f5a8be8@msi.defcon1> (raw)
In-Reply-To: <CAHmME9q-vbp4H3z8YdxFgd-Q55-+nwzork9D7wt3nnuT9UQhAA@mail.gmail.com>

On Mon, 22 May 2017 03:40:36 +0200
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:

Whoops, back in the loop:
=20
> Anyway, here's the solution I'm considering at the moment:
> https://github.com/jlund/streisand/pull/702

> My Gentoo system is more click-o-matic than Ubuntu dysfunctionality. =20

Gentoo is good (they also hate shitstemd;)
ubuntu is=E2=80=A6 ubuntu - using testing packages I wouldn't consider in a=
ny
configuration (I use Debian).

> Anyway, here's the solution I'm considering at the moment:
> https://github.com/jlund/streisand/pull/702 =20

This sounds fair, the only pending question being the last one:
"Building on that last point, I'm still uncertain exactly how Ubuntu's
use of dnsmasq interacts with --enable-updates/disable-updates and
resolvconf in general."
that I can't answer.
All I know is Debian waits for ~30s and jump to another resolver if
there's one into /etc/resolv.conf - but it doesn't keep track about
that (or not very long) and do the same for almost each DNS request.

My guess is you're trying to do too much for end users; just advertise
behaviors and let people fix their own configuration.
After all, this ML is here for that and WG is about VPN, not DNS.

Jean-Yves

  reply	other threads:[~2017-05-22  1:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-21 23:13 Bert Vermeulen
2017-05-21 23:23 ` Bzzzz
2017-05-22  0:41 ` Jason A. Donenfeld
2017-05-22  1:02   ` Bzzzz
2017-05-22  1:08     ` Jason A. Donenfeld
2017-05-22  1:34       ` Bzzzz
2017-05-22  1:40         ` Jason A. Donenfeld
2017-05-22  2:11           ` Bzzzz [this message]
2017-05-30 21:18       ` Jörg Thalheim
2017-05-22 11:02 ` Jason A. Donenfeld
2017-05-22 11:09   ` Bert Vermeulen

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=20170522041107.7f5a8be8@msi.defcon1 \
    --to=lazyvirus@gmx.com \
    --cc=Jason@zx2c4.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).