[WireGuard] Comments on wgserver.service

Daniel Kahn Gillmor dkg at fifthhorseman.net
Wed Jul 6 17:28:25 CEST 2016

On Wed 2016-07-06 10:33:02 -0400, Jason A. Donenfeld wrote:
> Please feel free to make wgserver.service into a more robust unit file
> and send patches (git-send-email), or make a few different unit files
> show casing different types of configurations. I'm not a huge systemd
> guy, so I just sort of threw that together haphazardly. It'd be nice
> also to see this integrated into systemd-networkd and the .network
> units.

I agree with this integration.  The current wireguard configuration is
actually pretty close to a .network unit, but not exactly aligned.

Arguably, it'd be more in-scope for a .netdev unit (see systemd.nedev(5)
than a .network unit, though.

If we could coax the wireguard config format to use config sections
identical to .netdev units, it'd probably be easier to approach
systemd-networkd about integration.  if none of the standard netdev
sections (aside from the descriptive [Netdev] section and the
conditional [Match] section) seem like they should be reusable for
wireguard ([Tunnel] doesn't seem to match exactly), maybe it's worth
defining the sections as [Wireguard] (currently [Interface]) and
[WireguardPeer] (currently [Peer]).


More information about the WireGuard mailing list