Cannot use localhost as endpoint for wireguard-windows

zhengmian hu huzhengmian at gmail.com
Mon Jun 7 16:02:16 UTC 2021


I might encounter the same problem as
https://lists.zx2c4.com/pipermail/wireguard/2020-August/005801.html
When endpoint is set as 127.0.0.1:51820, the log shows like follows:

[TUN] [xxx] peer(xxx) Received handshake response
[TUN] [xxx] peer(xxx) - Retrying handshake because we stopped hearing
back after 15 seconds.
[TUN] [xxx] peer(xxx) - Sending handshake initiation
[TUN] [xxx] peer(xxx) - Handshake did not complete after 5 seconds,
retrying (try 2)
[TUN] [xxx] peer(xxx) - Sending handshake initiation
[TUN] [xxx] peer(xxx) - Handshake did not complete after 5 seconds,
retrying (try 4)
...

In Wireshark, I can see that only the first handshake initiation
package is sent. There are no following packages even if the log shows
"Sending handshake initiation".

However, when I use another ip of the local computer for the endpoint,
e.g. 192.168.1.2, everything works fine.

Is it a known bug of wireguard-windows? Is there any existing formal
description on the scope of this bug? Is there any way to bypass this
problem?


More information about the WireGuard mailing list