Re: [PATCH] Adding support for reloading configuration via systemd

["Jason A. Donenfeld" <Jason@zx2c4.com>]

Hi Tore,

On Sat, Jul 25, 2020 at 2:16 PM Tore Anderson <tore@fud.no> wrote:
> I have no idea why my solution keeps being ignored (even after two
> gentle reminders), but perhaps third time's the charm?
>
> In any case, to quote myself from
> https://lists.zx2c4.com/pipermail/wireguard/2020-June/005585.html :
>
> «For what it is worth, I posted a patch that does exactly this back in
> March:
>
> https://lists.zx2c4.com/pipermail/wireguard/2020-March/005222.html
>
> Reviews or user tests would be greatly appreciated.
>
> You can also pull from https://github.com/toreanderson/wireguard-tools
> if you prefer. The commit in question is here:
>
> https://github.com/toreanderson/wireguard-tools/commit/8305a267ec4259206c0de7f1d3f9cfb8522a3223

But it doesn't sync Address=, DNS=, or any routing particulars. That
seems like a problem if it's to become a bona fide "reload" subcommand
of wg-quick, since it's not doing what it should be. On the other
hand, adding it to the systemd unit seems far enough away from core
code that we can kind of say, "eh, this sort of works," which might be
good enough. If even _that_ causes problems for users too, we'd have
to talk about removing it from the systemd unit. But hopefully it
stays under the radar and people don't have overly high expectations.

Jason