From: "Jörg Thalheim" <joerg@higgsboson.tk>
To: wireguard@lists.zx2c4.com
Subject: Re: openresolv dependency
Date: Tue, 30 May 2017 22:18:57 +0100 [thread overview]
Message-ID: <71eafdde-eadd-e1e6-c5be-fddf8feedba8@higgsboson.tk> (raw)
In-Reply-To: <CAHmME9pntk1UvFscCWsryW8eSCqzL66of0_F=H4KE0bmpZwA+Q@mail.gmail.com>
On 2017-05-22 02:08, Jason A. Donenfeld wrote:
>
>
> On Mon, May 22, 2017 at 3:02 AM, Bzzzz <lazyvirus@gmx.com <mailto:lazyvirus@gmx.com>> wrote:
>
> On Mon, 22 May 2017 02:41:13 +0200
> "Jason A. Donenfeld" <Jason@zx2c4.com <mailto:Jason@zx2c4.com>> wrote:
>
> > https://github.com/EggieCode/wireguard-ppa/issues/19 <https://github.com/EggieCode/wireguard-ppa/issues/19>
>
> Following your comment, you could flip the resolvconf dependency from
> a mandatory one to a a recommand or even a suggest, with a few comment
> lines into the /usr/share/doc/README.Debian file.
>
>
> The problem is that I would like to be able to use the -x and -m switches of resolvconf, which only openresolv has. However, it appears that openresolv does not work very well out of the box on Ubuntu.
>
> So, I'm not quite sure what I can recommend to Ubuntu users as a reliable way of setting a per-interface DNS override. Or even what command I could put in wg-quick to encapsulate that kind of logic.
>
> Any ideas?
>
If I recall correctly ubuntu 16.10+ switched to systemd-resolved, which has a saner way of per-interface DNS server
(I would even say the first true DNS server per-interface resolver implementation at all on linux).
next prev parent reply other threads:[~2017-05-30 21:06 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
2017-05-30 21:18 ` Jörg Thalheim [this message]
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=71eafdde-eadd-e1e6-c5be-fddf8feedba8@higgsboson.tk \
--to=joerg@higgsboson.tk \
--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).