* Re: WireGuard responses a Handshake Initiation packet with another Handshake Initiation instead of Handshake Response
[not found] <CA+O7g7c-XunYp0J+XWMQDEyCb=3vahgX2JaPEM-CYThvt6Ltig@53c70r.de>
@ 2021-06-03 19:30 ` Silvan Nagl
2021-06-03 19:40 ` Silvan Nagl
0 siblings, 1 reply; 3+ messages in thread
From: Silvan Nagl @ 2021-06-03 19:30 UTC (permalink / raw)
To: wireguard; +Cc: Arınç ÜNAL
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
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ç Ü.
[-- Attachment #2: server.pcap --]
[-- Type: application/vnd.tcpdump.pcap, Size: 1054 bytes --]
[-- Attachment #3: client.pcap --]
[-- Type: application/vnd.tcpdump.pcap, Size: 1260 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: WireGuard responses a Handshake Initiation packet with another Handshake Initiation instead of Handshake Response
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
0 siblings, 0 replies; 3+ messages in thread
From: Silvan Nagl @ 2021-06-03 19:40 UTC (permalink / raw)
To: wireguard
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ç Ü.
^ permalink raw reply [flat|nested] 3+ messages in thread
* 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).