Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Aaron Jones <aaronmdjones@gmail.com>
To: Markus Woschank <markus.woschank@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Roaming Mischief
Date: Fri, 17 Nov 2017 21:29:21 +0000	[thread overview]
Message-ID: <630c9955-ae3a-bf10-02ae-e5aa7eee6e64@gmail.com> (raw)
In-Reply-To: <CAKUy5ayo2jWAaA-D2UmtO6q4YUe-KP4u1+3VF32-kvbHbjZLsA@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 17/11/17 18:46, Markus Woschank wrote:
> Am I missing something here?

My example is most useful when both endpoints are roaming and either
endpoint needs to be able to initiate sessions. It's not a very
common scenario I'll give you that, but the current full roaming
support does enable it seamlessly (when you also enable keep-alives).

- -- 
Aaron Jones

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJaD1SvAAoJEIrwc3SIqzASeGEP/jM0ibvZPNF3LDXnRTVlsSQW
CCG4cAFmTkemV3MHoOjTIyzmpXHVSEJVqoJCPPqjeMkQp7tENJyUuuHt4JMu0ZSb
RW/mUr6DHtl1QvIeT0u/zb88NX36NyR0KalUE6R3yA5LHlUjqx1OVVpq+sEQMT9p
iRUAusn2psJGQAyu+QW9faU+4HQdbv2d8khLdZqC/0g+YxG24/B+3xVJYtv4Ou9Z
1M8MRWggiSyEOx/LoifxVYRlW0d8mgJV75e921bV9NkGFLATQ6tFvbaJn9ZP98iP
uGBP0XIT2NUb6HuekxJaTud7wsoTNiX1g57UdQtrgH0rTIjBzqlRG3atBgxCJ682
dpN1vvuAaiQrXoieHTek/d9pMAa8xwhc2uNQ36pi3xHrEFveqMIhQv95Qh0cwcpL
PoqciZyVDNrFdDkDajdhKMOhcH6qs2uWP8vYPkxZRaN5INU1kMZbIuBsBefr/yzl
4FqKuYRBHrKHZmrltLo0ek5B0Ib9oACE1HnTy4SyvonVOQwy6bKEQLw5D3/P+u1T
cX5bk0PWyVDLrc9zegxsl68tNjw9QYyxSV3rjleTUZatXu4CYGA9EgtkAICQ8TU0
Y0Gy325nAoKP/jXZWxUlXx75uU86ul12HoqrNgVYBcAYokDTz8U9qReBUCCGhqAP
neeE8d6rJBN9ZRWsBQzz
=BDlR
-----END PGP SIGNATURE-----

  reply	other threads:[~2017-11-17 21:24 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 [this message]
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=630c9955-ae3a-bf10-02ae-e5aa7eee6e64@gmail.com \
    --to=aaronmdjones@gmail.com \
    --cc=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).