WG via systemd (dis)advantage?

ѽ҉ᶬḳ℠ vtol at gmx.net
Wed May 2 18:48:32 CEST 2018

Debian kernel 4.15.11
WG 0.0.20180420-1

Out of curiosity having WG configured/manged via systemd, which is 
working thus far as having the interface up and listening (also after 
rebooting the server).

Now I was looking to manipulate the network interface with some 
post-up/post-down which though does not seems applicable with systemd, 
like it would be when managed through networking.service.

Hence, wondering whether I miss something about systemd or whether it is 
rather a bit of a disadvantage to configure/manage WG through systemd as 
opposed to networking.service?
What is the benefit of systemd vs. networking.service WG management?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4174 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.zx2c4.com/pipermail/wireguard/attachments/20180502/6ca08cf1/attachment.p7s>

More information about the WireGuard mailing list