Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Aaron Jones <me@aaronmdjones.net>
To: wireguard@lists.zx2c4.com
Cc: Gert Mertes <gmertes@outlook.be>
Subject: Re: Keepalive packets transmitted by default
Date: Wed, 13 Oct 2021 02:08:40 +0000	[thread overview]
Message-ID: <21958b52-894e-cb79-d831-159d7fda04e6@aaronmdjones.net> (raw)
In-Reply-To: <DM5PR1201MB0012B195C77099DA856C713CC5B69@DM5PR1201MB0012.namprd12.prod.outlook.com>


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

On 12/10/2021 13:52, Gert Mertes wrote:
> Hi,
>
> My Windows client (0.4.11) will still sporadically send (and receive)
> keepalive packets over an idle tunnel, even though PersistentKeepalive
> is not set in the config of any peer in the tunnel. Explicitly setting
> it to 0 also has the same result. I’m wondering if (i) the above is
> expected behaviour and (ii) is it possible to completely disable
> keepalive packets?
>
> Thanks,
> Gert

This is the expected behaviour, and it is not possible to disable it.

It's occurring because there is a unidirectional data transfer happening
(e.g. UDP), and the other side is responding with the keepalive because
it hasn't already done so recently (like it would with e.g. a TCP ACK)
and has nothing to send.

The reasons are described in sections 6.2 and 6.5 of the WireGuard
whitepaper.



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

      reply	other threads:[~2021-10-13  2:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12 13:52 Gert Mertes
2021-10-13  2:08 ` 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=21958b52-894e-cb79-d831-159d7fda04e6@aaronmdjones.net \
    --to=me@aaronmdjones.net \
    --cc=gmertes@outlook.be \
    --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).