Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Roaming Mischief
Date: Tue, 14 Nov 2017 07:53:23 -0600	[thread overview]
Message-ID: <5E8A8905-15B2-43DB-BC28-415D0A13216B@lonnie.abelbeck.com> (raw)
In-Reply-To: <CAKXLc7efXWWg16XZtAEVCskG8hWWJj0ge+FDax-X5onR2AWU2Q@mail.gmail.com>


On Nov 14, 2017, at 4:30 AM, Kalin KOZHUHAROV <me.kalin@gmail.com> =
wrote:

> On Tue, Nov 14, 2017 at 10:59 AM, Jason A. Donenfeld <Jason@zx2c4.com> =
wrote:
>> The other approach would be to add an optional exclamation
>> mark to the end of an endpoint specification
>> (Endpoint=3Dmy.server.whatever.zx2c4.com:51820!), that would prevent
>> servers from roaming; the client would still roam in the eyes of the
>> server, but the server, would no longer roam in the eyes of the
>> client. In other words, an option -- gasp, a nob! -- to disable
>> roaming on a per-by-peer one-sided basis. As you know, I don't really
>> like nobs. And I'd hate to add this, and then for people to use it,
>> and then loose some nice aspects of roaming, if it's not really even
>> required.
>>=20
> I have been wondering along those lines of roaming...
> There are certain use cases that require no roaming at all, e.g. a
> small set of servers that don't change IP.
> Anyway, a somewhat limited "roaming" can be achieved via DNS/hosts, if
> one trusts that system.
>=20
> While seamless roaming is a feature you use often I guess, my personal
> preference is to have it optional and explicitly specified, e.g. I
> have a few mobile devices (laptop, tablet), that only talk to 1 (or
> few at most) fixed IP (or DNS at least) "servers" (yes I know WG is
> P2P) and via those to the rest of the fixed hosts. So in this scenario
> (somewhat hard to achieve by {ip,nf}tables), I'd rather spec who is
> talking to whom, who can roam, etc.
>=20
> As for the syntax, and I hate to suggest that, adding a new option
> (breaking compatibility) like "AllowRoaming=3Dyes|1" with default
> AllowRoaming=3Dno 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.

Lonnie

  reply	other threads:[~2017-11-14 13:49 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 [this message]
2017-11-14 14:08     ` Kalin KOZHUHAROV
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=5E8A8905-15B2-43DB-BC28-415D0A13216B@lonnie.abelbeck.com \
    --to=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).