From: "Arınç ÜNAL" <arinc.unal@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: WireGuard responses a Handshake Initiation packet with another Handshake Initiation instead of Handshake Response
Date: Thu, 3 Jun 2021 09:43:04 +0300 [thread overview]
Message-ID: <CA+O7g7c-XunYp0J+XWMQDEyCb=3vahgX2JaPEM-CYThvt6Ltig@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
I tried wg syncconf wg0 <(wg-quick strip wg0) without success.
Only restarting wireguard by systemctl restart wg-quick@wg0 makes it
respond with a Handshake Response packet.
This happens really rarely and especially on OpenWrt 19.07 as a client.
Other clients can handshake properly while the server fails to
complete the handshake for the OpenWrt device.
Packet Captures on boths sides are in the attachments.
Server:
5.9.0-0.bpo.5-amd64 #1 SMP Debian 5.9.15-1~bpo10+1 (2020-12-31) x86_64 GNU/Linux
wireguard-tools v1.0.20210223 - https://git.zx2c4.com/wireguard-tools/
wireguard-dkms/buster-backports,now 1.0.20210219-1~bpo10+1
Client:
4.14.221 #0 SMP Mon Feb 15 15:22:37 2021 armv7l GNU/Linux
wireguard-tools v1.0.20191226 - https://git.zx2c4.com/wireguard-tools/
kmod-wireguard 4.14.221+1.0.20200611-2
Arınç Ü.
[-- Attachment #2: server.pcapng --]
[-- Type: application/octet-stream, Size: 9796 bytes --]
[-- Attachment #3: client.pcapng --]
[-- Type: application/octet-stream, Size: 5888 bytes --]
next reply other threads:[~2021-06-03 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 6:43 Arınç ÜNAL [this message]
[not found] <CA+O7g7c-XunYp0J+XWMQDEyCb=3vahgX2JaPEM-CYThvt6Ltig@53c70r.de>
2021-06-03 19:30 ` WireGuard responses a Handshake Initiation packet with another Handshake Initiation instead of Handshake Response Silvan Nagl
2021-06-03 19:40 ` Silvan Nagl
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='CA+O7g7c-XunYp0J+XWMQDEyCb=3vahgX2JaPEM-CYThvt6Ltig@mail.gmail.com' \
--to=arinc.unal@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).