From: Eicke Herbertz <wolletd@posteo.de>
To: wireguard@lists.zx2c4.com
Subject: Invalid handshake initiation after peer reboot: bug?
Date: Fri, 21 Aug 2020 22:42:43 +0200 [thread overview]
Message-ID: <e120a0a3-2170-4d2f-eaf5-878b09a0ab61@posteo.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1054 bytes --]
Hi,
we are currently rolling out some OpenWrt devices that are clients to a
WireGuard VPN. Everything was normal while they were in-house, but since
they are in the customers network, we got issues.
The first connection succeeds, but after a reboot of the client, the
server logs an Invalid handshake initiation. A restart of the servers
WireGuard interfaces makes a connection possible again.
As we strongly suspected issues in the customers network, we waited
without checking at first – and apparently, it takes two to three hours
of invalid handshakes until some, yet unknown, thing happens that
enables the connection without restarting the interface.
Clients are running:
OpenWrt 19.07.3 (r11063-85e04e9f46)
Kernel 4.14.180
WireGuard 1.0.20200506
Server is running Kernel 5.8.2 with in-tree WireGuard.
I am unable to reproduce this in my home and company networks with
identical devices. Several other devices work fine as well. I am not
sure were to look and what to look for.
Any help is appreciated!
Eicke
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2020-08-22 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 20:42 Eicke Herbertz [this message]
2020-08-22 19:11 ` Jason A. Donenfeld
2020-08-24 18:19 ` Eicke Herbertz
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=e120a0a3-2170-4d2f-eaf5-878b09a0ab61@posteo.de \
--to=wolletd@posteo.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).