From: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: RFC: wg syncpeers wg0 wireguard.conf
Date: Fri, 14 Jun 2019 15:48:49 -0500 [thread overview]
Message-ID: <C6E72DE9-0952-4341-8BC4-BF3B69CABAFC@lonnie.abelbeck.com> (raw)
In-Reply-To: <CAHmME9qpp5pkP3RAENJfWjdaL61T7J1C5dDLCM+OM-U_DxRz_Q@mail.gmail.com>
> On Jun 14, 2019, at 1:09 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> I'm leaning toward Steven's suggestion of nixing addconf and making
> setconf behave like syncconf.
But wouldn't the current 'setconf' (overwrite existing) always be faster than a combo 'setconf/syncconf' (sync with existing) ?
I have this nagging feeling that both 'setconf' and 'syncconf' should exist, if not for efficiencies but for unforeseen reasons related to the different functionalities: Start 'setconf' and Reload 'syncconf'.
Lonnie
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-06-14 20:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 19:59 Lonnie Abelbeck
2019-06-10 12:34 ` Rene 'Renne' Bartsch, B.Sc. Informatics
2019-06-11 17:28 ` Jason A. Donenfeld
2019-06-11 21:06 ` Lonnie Abelbeck
2019-06-11 21:41 ` Kalin KOZHUHAROV
2019-06-12 0:22 ` Steven Honson
2019-06-12 0:25 ` Marc Fawzi
2019-06-14 18:01 ` Jason A. Donenfeld
2019-06-16 19:43 ` Marc Fawzi
2019-06-13 23:15 ` Lonnie Abelbeck
2019-06-14 18:09 ` Jason A. Donenfeld
2019-06-14 20:48 ` Lonnie Abelbeck [this message]
2019-06-14 21:14 ` Ivan Labáth
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=C6E72DE9-0952-4341-8BC4-BF3B69CABAFC@lonnie.abelbeck.com \
--to=lists@lonnie.abelbeck.com \
--cc=Jason@zx2c4.com \
--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).