Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Michael Brookes <mgsb81@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Constant stream of handshake for peer did not complete
Date: Thu, 8 Sep 2022 14:49:55 +0100	[thread overview]
Message-ID: <CABfcST-uzN3JJ0vB04s4TSfSbz18Ngn9pn+41iN_g62XWoAtUw@mail.gmail.com> (raw)

Hi

I have one wg endpoint which is CentOS 7.9.2009
(3.10.0-1160.71.1.el7.x86_64) with kmod-wireguard
9:1.0.20220627-1.el7_9.elrepo installed. Has about 300ish peers.

We have one, there could be more, cases of wireguard logging on the
other peer (typically laptops, I've seen this happen on Mac using the
app and Ubuntu)

Handshake for peer 6 ... did not complete after 5 seconds, retrying (try 4)

The handshake on the CentOS end never updates and of course the tunnel
doesn't work on the Mac/Ubuntu laptop.

To get the tunnel working again all I do is on the CentOS end remove
and add the peer, and the tunnel suddenly springs to life and traffic
flows normally.

I've since enabled debug on the CentOS end and see a constant stream of:

Handshake for peer 6 ... did not complete after 5 seconds, retrying (try 4)

Since I enabled debugging ~200 different peers have logged that.
Also see this - invalid address - a few times too for different peers:

Handshake for peer 1809 ((invalid address)) did not complete after 5
seconds, retrying (try 5)

Is this expected debug output for a setup where you have a CentOS
server with peers which are all laptops? i.e. the CentOS end is trying
to initiate the handshake and the laptop is off/wireguard app turned
off.

Is it down to some UDP traffic potentially being dropped? Some network
card tweaks needed?

Any help greatly appreciated

                 reply	other threads:[~2022-09-28 10:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CABfcST-uzN3JJ0vB04s4TSfSbz18Ngn9pn+41iN_g62XWoAtUw@mail.gmail.com \
    --to=mgsb81@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).