Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: Roaming Mischief
Date: Sat, 18 Nov 2017 10:38:55 +0100	[thread overview]
Message-ID: <4cd6a9b8-b317-3fdb-d758-08a546bc5acf@urlichs.de> (raw)
In-Reply-To: <CAKUy5ayo2jWAaA-D2UmtO6q4YUe-KP4u1+3VF32-kvbHbjZLsA@mail.gmail.com>

On 17.11.2017 19:46, Markus Woschank wrote:
> After some more thoughts, in the scenario that you are describing,
> where does persisting the state on the roaming peer help?
> The roaming peer has the fixed peer's address in his configuration
> (his IP does not change), and the remote side did not suspend.
> Am I missing something here?

Simple example: a mobile IP phone. Rebooting your telephony server
causes you to drop the connection to the client until _it_ next issues a
call. However, if you persist the phone's address, you don't lose
incoming service.

-- 
-- Matthias Urlichs

  parent reply	other threads:[~2017-11-18  9:35 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 [this message]
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=4cd6a9b8-b317-3fdb-d758-08a546bc5acf@urlichs.de \
    --to=matthias@urlichs.de \
    --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).