WireGuard Archive on lore.kernel.org
 help / color / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Willem van den Akker <wvdakker@wilsoft.nl>,
	Michael Biebl <biebl@debian.org>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wg-quick invoking resolvectl instead of resolvconf on systems where that is appropriate?
Date: Tue, 10 Sep 2019 17:12:01 -0400
Message-ID: <87o8zr500u.fsf@fifthhorseman.net> (raw)
In-Reply-To: <CAHmME9rkuwVHo1Egq9r0vtOdR5yJ0xes3_WEWb3ncVnPhXwbmQ@mail.gmail.com>

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

On Tue 2019-09-10 14:52:32 -0400, Jason A. Donenfeld wrote:
> The standard interface for modifying DNS on Linux is resolvconf. It is for
> this reason that systemd added the compatibility layer. Debian should
> install the proper symlink. WireGuard upstream will support the standard
> mechanism of resolvconf.

OK, that answers that :)

I suspect there are more GNU/Linux systems in the world right now that
have resolvectl installed than have all versions of resolvconf installed
put together, but if you'd rather that wg-quick depends on the
interpretation of the resolvconf interface on the given system, that
works for me.

I'm sure you understand that debian can't ship the resolvconf symlink
directly in the systemd package because it would conflict with the
resolvconf and openresolv packages; but i'll follow up over in
https://bugs.debian.org/939904 to see if we can figure out a way to ship
a separate binary package from the same source that automatically
enables this support.

thanks for the prompt followup,


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

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

WireGuard mailing list

  reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-10 18:50 Daniel Kahn Gillmor
2019-09-10 18:52 ` Jason A. Donenfeld
2019-09-10 21:12   ` Daniel Kahn Gillmor [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o8zr500u.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=Jason@zx2c4.com \
    --cc=biebl@debian.org \
    --cc=wireguard@lists.zx2c4.com \
    --cc=wvdakker@wilsoft.nl \


* 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 zx2c4-wireguard@archiver.kernel.org
	public-inbox-index wireguard

Newsgroup available over NNTP:

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