wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
* wg-quick invoking resolvectl instead of resolvconf on systems where that is appropriate?
@ 2019-09-10 18:50 Daniel Kahn Gillmor
  2019-09-10 18:52 ` Jason A. Donenfeld
  0 siblings, 1 reply; 6+ messages in thread
From: Daniel Kahn Gillmor @ 2019-09-10 18:50 UTC (permalink / raw)
  To: WireGuard mailing list; +Cc: Willem van den Akker, Michael Biebl


[-- 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

^ permalink raw reply	[flat|nested] 6+ messages in thread
* wg-quick invoking resolvectl instead of resolvconf on systems where that is appropriate?
@ 2019-10-31 23:19 Arjen Runsink
  0 siblings, 0 replies; 6+ messages in thread
From: Arjen Runsink @ 2019-10-31 23:19 UTC (permalink / raw)
  To: wireguard, roy

In response to messages:

https://lists.zx2c4.com/pipermail/wireguard/2019-September/004524.html
https://lists.zx2c4.com/pipermail/wireguard/2019-September/004533.html

The resolvconf implementation on distro's using systemd is not a 
complete replacement of the original resolvconf.

On my preferred distribution (Solus) it even results in some 
strangeness where instead of setting the dns, resolvconf produces the 
status and halts the execution of wg-quick.

My solution is to detect the presence of systemd during build and use a 
modified version of linux.bash that I call linux-systemd.bash which 
uses resolvectl and a changed Makefile to go with it. It is a bit of a 
hack, but if interested, I will gladly send the patch.

Regards, Arjen






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

^ permalink raw reply	[flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-11-27  9:04 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-10 18:50 wg-quick invoking resolvectl instead of resolvconf on systems where that is appropriate? Daniel Kahn Gillmor
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
2019-10-31 23:19 Arjen Runsink

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).