WireGuard Archive on lore.kernel.org
 help / color / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Cc: Willem van den Akker <wvdakker@wilsoft.nl>,
	Michael Biebl <biebl@debian.org>
Subject: wg-quick invoking resolvectl instead of resolvconf on systems where that is appropriate?
Date: Tue, 10 Sep 2019 14:50:48 -0400
Message-ID: <87zhjc3rzr.fsf@fifthhorseman.net> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 1083 bytes --]

Hi Wireguard folks--

over in https://bugs.debian.org/939904, Michael Biebl (in cc) pointed
out that on GNU/Linux systems supervised by systemd, if systemd-resolved
is running, it might make more sense for wg-quick to invoke resolvectl
directly with the DNS parameter instead of depending on resolvectl's
resolvconf-like symlink shim.

Jason, is that something that you'd be ok with, or is wg-quick wedded to
resolvconf, even if resolvectl is available and there is no resolvconf?
(and if you're ok with it, but if both exist, do you have a preference
for which one should be used?)

Is anyone interested in hacking on src/tools/wg-quick/linux.bash to
enable this?  I think the command should be pretty simple -- the main
things to get right are detection of subsystem availability and conflict
resolution.

I guess my preference would be something like:

 * if resolvectl exists, try to use it.  if it succeeds, done.  (it
   might fail if systemd-resolved is not running, for example)

 * otherwise, try using resolvconf.

but of course this is Jason's call to make.

       --dkg

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

             reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-10 18:50 Daniel Kahn Gillmor [this message]
2019-09-10 18:52 ` Jason A. Donenfeld
2019-09-10 21:12   ` Daniel Kahn Gillmor
2019-09-10 21:22   ` Michael Biebl
2019-09-11 18:40     ` Roy Marples

Reply instructions:

You may reply publically 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=87zhjc3rzr.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=biebl@debian.org \
    --cc=wireguard@lists.zx2c4.com \
    --cc=wvdakker@wilsoft.nl \
    /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

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
		wireguard@lists.zx2c4.com
	public-inbox-index wireguard

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/com.zx2c4.lists.wireguard


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git