Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Mats Loman <>
To: "" <>
Subject: Endpoints are not in sync (latest handshake)
Date: Thu, 18 Aug 2022 08:40:21 +0000	[thread overview]
Message-ID: <VE1P189MB0989ABC50A06400CFC34F398E56D9@VE1P189MB0989.EURP189.PROD.OUTLOOK.COM> (raw)

I have two wireguard endpoints that has different opinions about when the last handshake was made:

interface: wg0
  public key: PauftxCvmti7CDDZ9yj6EKZ+r9zQj6gjb9hvP1whzwQ=
  private key: (hidden)
  listening port: 17395

peer: s5dnr91F06+AQ/3o5urOM5Dc1f0gzHOsGjwD+AEmwDA=
  allowed ips:,
  latest handshake: 8 hours, 42 minutes, 30 seconds ago
  transfer: 260.73 GiB received, 313.35 GiB sent


interface: wg0
  public key: s5dnr91F06+AQ/3o5urOM5Dc1f0gzHOsGjwD+AEmwDA=
  private key: (hidden)
  listening port: 17395

peer: PauftxCvmti7CDDZ9yj6EKZ+r9zQj6gjb9hvP1whzwQ=
  allowed ips:,
  latest handshake: 2 minutes, 15 seconds ago
  transfer: 282.13 GiB received, 276.13 GiB sent

It is not possible  to send data through the tunnel  in both directions only in one direction.

It is pretty easy to repeat this situation:
Send UDP packets through the tunnel at a speed that wireguard cannot keep up with. I expect packet loss in this case but not that the tunnel is "partially closed".

Any ideas?

Best regards,
Mats Loman

             reply	other threads:[~2022-08-23 13:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18  8:40 Mats Loman [this message]
2022-08-24  5:32 ` Mats Loman

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=VE1P189MB0989ABC50A06400CFC34F398E56D9@VE1P189MB0989.EURP189.PROD.OUTLOOK.COM \ \ \

* 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).