Endpoints are not in sync (latest handshake)

Mats Loman mats.loman at rte.se
Thu Aug 18 08:40:21 UTC 2022


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=
  endpoint: 192.168.201.24:17395
  allowed ips: 192.168.26.197/32, 192.168.201.38/32
  latest handshake: 8 hours, 42 minutes, 30 seconds ago
  transfer: 260.73 GiB received, 313.35 GiB sent

And:

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

peer: PauftxCvmti7CDDZ9yj6EKZ+r9zQj6gjb9hvP1whzwQ=
  endpoint: 192.168.201.23:17395
  allowed ips: 192.168.26.200/32, 192.168.201.249/32
  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


More information about the WireGuard mailing list