From: zhengmian hu <huzhengmian@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Cannot use localhost as endpoint for wireguard-windows
Date: Mon, 7 Jun 2021 12:02:16 -0400 [thread overview]
Message-ID: <CAAntei_4-bdocSED1vNkG94oe0AL33RVA6s1w5DT2Q13NLH=7Q@mail.gmail.com> (raw)
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?
reply other threads:[~2021-06-08 10:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAAntei_4-bdocSED1vNkG94oe0AL33RVA6s1w5DT2Q13NLH=7Q@mail.gmail.com' \
--to=huzhengmian@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).