From: Bruno Wolff III <bruno@wolff.to>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Roaming Mischief
Date: Tue, 14 Nov 2017 07:25:51 -0600 [thread overview]
Message-ID: <20171114132551.GB13027@wolff.to> (raw)
In-Reply-To: <CAHmME9pW_0o8C+ovxgN3_-6csAa2sjF4hXo=24bhsi0jo=AP0Q@mail.gmail.com>
On Tue, Nov 14, 2017 at 10:59:03 +0100,
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>(Endpoint=my.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.
If you know your other end point is at a fixed address you can use
iptables (or the equivalent) to enforce this. I don't think it needs
to be in WireGuard.
next prev parent reply other threads:[~2017-11-14 13:22 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
2017-11-14 13:25 ` Bruno Wolff III [this message]
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=20171114132551.GB13027@wolff.to \
--to=bruno@wolff.to \
--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).