From: Aaron Jones <aaronmdjones@gmail.com>
To: Ryan Whelan <rcwhelan@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Dead peer detection
Date: Sun, 27 May 2018 06:02:32 +0000 [thread overview]
Message-ID: <119b596d-fd43-01bf-32d0-9edb2928bcb1@gmail.com> (raw)
In-Reply-To: <CAM3m09TdGPdAa6ksXPsYK48agkjbtaHSnSUPTiJ1-S6LDqwtRw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 25/05/18 14:50, Ryan Whelan wrote:
> I thought this conversation had been had in the past, but I can
> not find it so forgive me if I'm rehashing something thats been
> discussed already.
>
> How do you guys detect dead peers? Actively via a ping or
> passively via the 'latest handshake' (once it gets past a certain
> age, you assume the peer is offline). Are their other options?
If no traffic is being exchanged, handshakes won't take place either,
so you can't rely on just looking at that.
If you try to communicate with the peer, and the latest handshake is
more than 3 minutes ago, it should be safe to assume the peer is gone;
as handshakes occur (when there's traffic) every 2 minutes.
Note that persistent keep-alive packets count as traffic.
Regards,
Aaron Jones
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJbCknhAAoJEIrwc3SIqzAS2qUP/jzYcbNa8yJzys3nZwnYByJY
x5MBR8EDZjdaUAdEaw+KEkOL78VoHG+NvQWQ62uLAdlv26S9EslfUSmDsI5XK8I/
0b13WWJjnFORI7iSRpgDjVdnpMVkHxfVLIXHfBV6aFziJaysjzVyGBPGx/oHeuu4
Rq7Qf+AppyTddibZurbRUqFBnQ7Li1oBV+sJe8rA+mJYxCG5C5G/8pYj30zL6MAi
3gX2bllPCTTgQPjQvmMtFeQMnwH0hVqyh6b7xPx3Nivfdf8CthGp6cW63W07ilAE
/mWaYKwGQyrYxhWHBytZETVfsfYOrea/LQZpUzjO+C6fF3HjU4fkpoKXkZZ41C4M
UAgXyPF2MTdtQwQvJ3z4aT7j/8ho5itEY+2HRskq8XP4H7v+N1oFnAsG7cfyfU9l
uvKekPPDW7ZcadOMyb33iV7CzLKgTPHCayUYOsU1lATUSAQBNyTEM6GqASbssB3D
O5P2dPjMbRuMVPrvpryKRiB7LSxydFDAoUQ6V8HA3By42Jpr1NOvT28JCulBmpBq
tiS4kpRNWQd72iB/v+oJ9CjJPstc+36TDdzir7i8Q03uAWi6aI2gdwRXNoQAfWbK
hQfsFh3Y/OktSGuwHUlwBHdfcig4rZRJUyxZPWteMILUgwcW5+ywkgJfuyEoLffy
NMmLf/J+Orv5fwCOh0uQ
=IZNK
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2018-05-27 6:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 14:50 Dead peer detection Ryan Whelan
2018-05-25 16:05 ` Matthias Urlichs
2018-05-27 6:02 ` Aaron Jones [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=119b596d-fd43-01bf-32d0-9edb2928bcb1@gmail.com \
--to=aaronmdjones@gmail.com \
--cc=rcwhelan@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).