From: Kalin KOZHUHAROV <me.kalin@gmail.com>
To: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Roaming Mischief
Date: Tue, 14 Nov 2017 15:08:04 +0100 [thread overview]
Message-ID: <CAKXLc7cVKvRONzK67TV+7skeEtLmgbqmoNrBP6go2anp-y6USw@mail.gmail.com> (raw)
In-Reply-To: <5E8A8905-15B2-43DB-BC28-415D0A13216B@lonnie.abelbeck.com>
On Tue, Nov 14, 2017 at 2:53 PM, Lonnie Abelbeck
<lists@lonnie.abelbeck.com> wrote:
>
> On Nov 14, 2017, at 4:30 AM, Kalin KOZHUHAROV <me.kalin@gmail.com> wrote:
>> As for the syntax, and I hate to suggest that, adding a new option
>> (breaking compatibility) like "AllowRoaming=yes|1" with default
>> AllowRoaming=no is what I would like, instead of somewhat vague "!" at
>> the end.
>
> Kalin, I don't care for the somewhat vague "!" notation either ... reads NOT to me.
>
> But, I would not break compatibility, I suggest adding a "paranoid option" EndpointFixed ...
> --
> EndpointFixed - Optional, defaults to 0|no, endpoint roaming is enabled by default,. Set EndpointFixed to 1|yes to disable endpoint roaming. Ignored if Endpoint is not defined.
> --
>
> As a side-benefit, the documentation of this option provides some quick-reference documentation to the operation of WireGuard.
>
Yep! +1
Kalin.
next prev parent reply other threads:[~2017-11-14 14:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 9:59 Jason A. Donenfeld
2017-11-14 10:30 ` Kalin KOZHUHAROV
2017-11-14 13:53 ` Lonnie Abelbeck
2017-11-14 14:08 ` Kalin KOZHUHAROV [this message]
2017-11-14 13:25 ` Bruno Wolff III
2017-11-14 13:50 ` Kalin KOZHUHAROV
2017-11-15 18:38 ` Markus Woschank
2017-11-15 22:03 ` Aaron Jones
2017-11-17 17:23 ` Markus Woschank
2017-11-17 17:36 ` Aaron Jones
2017-11-17 18:38 ` Markus Woschank
2017-11-17 18:46 ` Markus Woschank
2017-11-17 21:29 ` Aaron Jones
2017-11-17 22:06 ` Markus Woschank
2017-11-17 22:11 ` Markus Woschank
2017-11-18 9:38 ` Matthias Urlichs
2017-11-18 15:01 ` Markus Woschank
2017-11-18 15:11 ` Markus Woschank
2017-11-16 17:45 ` Stephen Major
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=CAKXLc7cVKvRONzK67TV+7skeEtLmgbqmoNrBP6go2anp-y6USw@mail.gmail.com \
--to=me.kalin@gmail.com \
--cc=lists@lonnie.abelbeck.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).