From: Silvan Nagl <mail@53c70r.de>
To: wireguard@lists.zx2c4.com
Subject: Re: WireGuard responses a Handshake Initiation packet with another Handshake Initiation instead of Handshake Response
Date: Thu, 3 Jun 2021 21:40:42 +0200 [thread overview]
Message-ID: <c6c6f40b-25e8-8430-ff3b-3baa51414147@53c70r.de> (raw)
In-Reply-To: <852812b5-9210-5c70-7cef-d673967d568a@53c70r.de>
actually it was reproducible on my 4w old setup.
after updating both it ain't reproducible anymore.
openwrt: Quintus Build@2021.05.23 / LuCI openwrt-21.02 branch
git-21.136.64332-53c572a
fedora_server: 5.12.8-300.fc34.x86_64
On 03.06.2021 21:30, Silvan Nagl wrote:
> Reproducible:
>
> Client_a <-> Gateway_a <-> Internet <-> Server_b
>
> When Gateway_a changes its WAN-IP Client_a loses connection.
> Capture files show the state after the IP change.
>
> On 6/3/21 8:43 AM, Arınç ÜNAL wrote:
>> 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ç Ü.
next prev parent reply other threads:[~2021-06-03 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+O7g7c-XunYp0J+XWMQDEyCb=3vahgX2JaPEM-CYThvt6Ltig@53c70r.de>
2021-06-03 19:30 ` Silvan Nagl
2021-06-03 19:40 ` Silvan Nagl [this message]
2021-06-03 6:43 Arınç ÜNAL
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=c6c6f40b-25e8-8430-ff3b-3baa51414147@53c70r.de \
--to=mail@53c70r.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).