wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
* WireGuard responses a Handshake Initiation packet with another Handshake Initiation instead of Handshake Response
@ 2021-06-03  6:43 Arınç ÜNAL
  0 siblings, 0 replies; 3+ messages in thread
From: Arınç ÜNAL @ 2021-06-03  6:43 UTC (permalink / raw)
  To: wireguard

[-- 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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-06-03 19:40 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [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
2021-06-03  6:43 Arınç ÜNAL

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