From: Markus Woschank <markus.woschank@gmail.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Roaming Mischief
Date: Sat, 18 Nov 2017 16:01:10 +0100 [thread overview]
Message-ID: <CAKUy5ayySemw3Yct425deiLmqSLNLDTS-2Q2GAYp9y8aJabOhg@mail.gmail.com> (raw)
In-Reply-To: <593d6d3a-550e-a14d-4c1d-f7ee8e731d87@gmail.com>
@matthias
On 15 November 2017 at 23:03, Aaron Jones <aaronmdjones@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 15/11/17 18:38, Markus Woschank wrote:
>> I don't see the point in allowing other IPs to connect if an
>> endpoint IP has been specified - more confusing then helpful IMO.
>
> Endpoint is also used so that this machine can initiate sessions with
> the peer. WireGuard is not a client-server architecture; by removing the
> endpoint, you are preventing this peer from initiating. This is only
> useful if you're using it *as* a server, in which case roaming is
> usually what you want, but not always.
>
> - --
> Aaron Jones
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJaDLm9AAoJEIrwc3SIqzASbN4P/iPQ3lMU48ehqDG7g3bOyxzV
> qPGdipvtjslsykZaEPV5ZaL+olg1IvV3fG0eXuYny1pU55TMS+eJzQcc2Y1C6ovv
> Qdm0C82GQahuy8GaPH5KTMMxTpw5M1rP/ffpW5tujzegLnoCY/zov3gs0ejsahU4
> fEABmagk/d6k8ct2bJvFoKLvVr1PQel0gMv1D2LY1wdZBus6P6xbM7uVH346CJU7
> Y5Gx/qo2e++PNtPJLNuXEWqaB/GvuCNsnYyZwec1J9h2ZHEhaaJOl+tQvFf/dHCk
> BMj/OEopN8+7u00N8LTQdsUiG6Pb6klIZyKN3fuLNhTmIaox+Gwi7mgEzOOYmGgn
> ft8YiwFumBbU+E9P0DCwScOC+6jPKPFsYUfXtWqAjKGPsJRfeBaRk//v9weqqt6p
> jNpyfOCk5GxtG26U9gYqBldAMdl3OdlEYeN7ve1FXpoT4CbhuDfm7XzPFkMzirON
> EjXyqLaqhRW7Jd1yAnp585FLuQ/tXw284hQFSimVSZ+WuWwnm21IL/7JfRMIPXUa
> B3wbNIAmpFwBZKdO8mcgZjakt7pVheT7aVbIJpWOuWpFvJvCltI/jQvY1O9V+ZcU
> sRAF6bK2m+4eupFe6Wex3s692sLnaX942gCWZvzZIx01ZRCITqYsdyabdwVxtb3X
> z3FPheigDitxgt15oMKP
> =61HN
> -----END PGP SIGNATURE-----
next prev parent reply other threads:[~2017-11-18 14:56 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
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 [this message]
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=CAKUy5ayySemw3Yct425deiLmqSLNLDTS-2Q2GAYp9y8aJabOhg@mail.gmail.com \
--to=markus.woschank@gmail.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).