From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: vtol@gmx.net, wireguard <wireguard@lists.zx2c4.com>
Subject: Re: WG via systemd (dis)advantage?
Date: Wed, 02 May 2018 18:52:32 +0200 [thread overview]
Message-ID: <8736za0zlb.fsf@toke.dk> (raw)
In-Reply-To: <b4e58a27-df47-b47b-0191-80483db929a6@gmx.net>
=D1=BD=D2=89=E1=B6=AC=E1=B8=B3=E2=84=A0 <vtol@gmx.net> writes:
> Debian kernel 4.15.11
> WG 0.0.20180420-1
>
> Out of curiosity having WG configured/manged via systemd, which is=20
> working thus far as having the interface up and listening (also after=20
> rebooting the server).
>
> Now I was looking to manipulate the network interface with some=20
> post-up/post-down which though does not seems applicable with systemd,=20
> like it would be when managed through networking.service.
You can't do one-line up/down scripts, but you could create a separate
service file and have it depend on the wg interface...
> Hence, wondering whether I miss something about systemd or whether it is=
=20
> rather a bit of a disadvantage to configure/manage WG through systemd as=
=20
> opposed to networking.service?
> What is the benefit of systemd vs. networking.service WG management?
If you're using systemd-networkd to configure the rest of your
networking, having wireguard configured the same way can be useful; and
systemd-networkd can manage dependencies between interfaces as well (to
a certain extent).
However, as you note, things like running arbitrary scripts is a bit
more of a hassle...
-Toke
next prev parent reply other threads:[~2018-05-02 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 16:48 WG via systemd (dis)advantage? ѽ҉ᶬḳ℠
2018-05-02 16:52 ` Toke Høiland-Jørgensen [this message]
2018-05-04 9:51 ` ѽ҉ᶬḳ℠
Reply instructions:
You may reply publicly 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=8736za0zlb.fsf@toke.dk \
--to=toke@toke.dk \
--cc=vtol@gmx.net \
--cc=wireguard@lists.zx2c4.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.