From: Tore Anderson <tore@fud.no>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
"Tomcsanyi, Domonkos" <domi@tomcsanyi.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH] Adding support for reloading configuration via systemd
Date: Sat, 25 Jul 2020 14:16:23 +0200 [thread overview]
Message-ID: <84986996953761e9d645b7ef583d3ffca689dfc5.camel@fud.no> (raw)
In-Reply-To: <CAHmME9qsfmK6_d4bDF1Oj4585_56Vtm+wCT+i-2PO=tXN3Jsfw@mail.gmail.com>
* Jason A. Donenfeld
> This actually doesn't seem too bad to me. Are there cleaner solutions
> that I'm not thinking of that I should consider before applying this
> patch?
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
There is one bugfix in GitHub compared to the patch I posted to the
list in March - using $REAL_INTERFACE instead of $INTERFACE in wg-
quick/openbsd.bash. I can post the updated patch to the list as well if
you want, just let me know.»
Tore
next prev parent reply other threads:[~2020-07-25 12:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <VI1PR02MB52169D6F055314DCD03746EDE6760@VI1PR02MB5216.eurprd02.prod.outlook.com>
2020-07-23 14:10 ` Tomcsanyi, Domonkos
2020-07-24 9:14 ` Jason A. Donenfeld
2020-07-24 9:25 ` Garrit Franke
2020-07-24 9:27 ` Garrit Franke
2020-07-24 9:29 ` Jason A. Donenfeld
2020-07-24 13:09 ` Tomcsányi, Domonkos
2020-07-24 14:26 ` Jason A. Donenfeld
2020-07-24 14:46 ` Dominique Martinet
2020-07-24 14:49 ` Jason A. Donenfeld
2020-07-24 9:54 ` Matthias Urlichs
2020-07-24 10:52 ` Stefan Tatschner
2020-07-24 11:00 ` Matthias Urlichs
2020-07-25 12:16 ` Tore Anderson [this message]
2020-07-27 15:51 ` Jason A. Donenfeld
2020-07-27 20:04 ` Tore Anderson
2020-07-28 9:03 ` Jason A. Donenfeld
2020-07-28 9:54 ` Tore Anderson
2020-07-28 11:55 ` Jason A. Donenfeld
2020-07-28 12:17 ` Tore Anderson
2020-07-28 12:17 ` Jason A. Donenfeld
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=84986996953761e9d645b7ef583d3ffca689dfc5.camel@fud.no \
--to=tore@fud.no \
--cc=Jason@zx2c4.com \
--cc=domi@tomcsanyi.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 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).