Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: Dead peer detection
Date: Fri, 25 May 2018 18:05:28 +0200	[thread overview]
Message-ID: <2805c563-cf43-c1a8-665a-6c49033894e4@urlichs.de> (raw)
In-Reply-To: <CAM3m09TdGPdAa6ksXPsYK48agkjbtaHSnSUPTiJ1-S6LDqwtRw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 387 bytes --]

Hi,
> 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?
You can't passively determine that a peer is offline, only that it isn't.
It might just not have anything to send at the moment.

So, yes, ping it.

-- 
-- Matthias Urlichs



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-05-25 16:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25 14:50 Ryan Whelan
2018-05-25 16:05 ` Matthias Urlichs [this message]
2018-05-27  6:02 ` Aaron Jones

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=2805c563-cf43-c1a8-665a-6c49033894e4@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).