From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Iain Douglas <wireguard@1n6.org.uk>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Understanding Protocol / State Machine
Date: Wed, 2 Jan 2019 19:20:28 +0100 [thread overview]
Message-ID: <CAHmME9oHGSXyhaRHPWM4B9=haKBFrNV5K7NwDWJPiW0jKfgi9A@mail.gmail.com> (raw)
In-Reply-To: <478b9a56-d09e-5908-f253-a32985898072@1n6.org.uk>
On Wed, Jan 2, 2019 at 7:03 PM Iain Douglas <wireguard@1n6.org.uk> wrote:
> 1. Handshake < 119 seconds ago the link takes ~ 15 seconds to recover
> 2. Handshake between 120 and 179 seconds ago - 1st packet is lost then
> link recovers
> 3. Handshake >=180 second ago - link just works as normal.
For 1, it's hitting the timeout of detecting the dead peer before
reestablishing the handshake, since it still believes it has a valid
session.
For 2, it's the same as 1, except that when sending packets when your
current session is older than two minutes, it will start trying to
create a new one. The way to think of this that sessions live
optimally for only 2 minutes and maximally for 3.
For 3, the current session is unusable and already cleared from
memory, since it expired after 3 minutes, and so a new session is
established before the packet is sent.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-01-02 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 18:18 Understanding Protocol / State Machine Iain Douglas
2019-01-02 18:20 ` Jason A. Donenfeld [this message]
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='CAHmME9oHGSXyhaRHPWM4B9=haKBFrNV5K7NwDWJPiW0jKfgi9A@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=wireguard@1n6.org.uk \
--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).