From: Hirbod Behnam <chrome.hiri.angry@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Cannot set endpoint to localhost on windows
Date: Sat, 29 Aug 2020 20:28:10 +0430 [thread overview]
Message-ID: <CANtK_yx9zFK1Z4gm_SNC_rvveSoHEgTBrWscE5CeZaPuACUHbw@mail.gmail.com> (raw)
Hello
I'm not sure if this is already reported or not but I found a small
problem with the windows client of wireguard that does not allow users
to use "plugins" on top of wireguard.
So here is my case. I used gost to create a really simple port
forwarder from my localhost to my server with this command: gost
-L=udp://127.0.0.1:12345/1.1.1.1:12345 (that forwards packets on port
12345 to 1.1.1.1:12345 and of course my server is not 1.1.1.1 :D)
Also here is my wireguard config:
[Interface]
PrivateKey = xxxx
Address = 10.9.0.2/24
DNS = 8.8.8.8
[Peer]
PublicKey = xxxx
AllowedIPs = 0.0.0.0/8,1.0.0.0/16,1.1.0.0/24,1.1.1.0/32,1.1.1.2/31,1.1.1.4/30,1.1.1.8/29,1.1.1.16/28,1.1.1.32/27,1.1.1.64/26,1.1.1.128/25,1.1.2.0/23,1.1.4.0/22,1.1.8.0/21,1.1.16.0/20,1.1.32.0/19,1.1.64.0/18,1.1.128.0/17,1.2.0.0/15,1.4.0.0/14,1.8.0.0/13,1.16.0.0/12,1.32.0.0/11,1.64.0.0/10,1.128.0.0/9,2.0.0.0/7,4.0.0.0/6,8.0.0.0/5,16.0.0.0/4,32.0.0.0/3,64.0.0.0/2,128.0.0.0/1
Endpoint = 127.0.0.1:12345
PersistentKeepalive = 25
The allowed IPs are all ip addresses except 1.1.1.1.
When I run the client, the log fills with: [TUN] [xxx-wg0] peer(xxx) -
Failed to send data packet write udp4 0.0.0.0:58932->127.0.0.1:12345:
wsasendto: The requested address is not valid in its context.
And I cannot connect to anything. Sometimes in gost, it says that a
connection is established but I still cannot connect to anything
though wireguard.
Also it's good to know that the exact config works fine with TunSafe,
the official Ubuntu client and openvpn. (I can connect through gost)
Thanks for the project!
Hirbod
next reply other threads:[~2020-08-29 20:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 15:58 Hirbod Behnam [this message]
2020-08-30 14:53 ` Alessandro Rinaldi
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=CANtK_yx9zFK1Z4gm_SNC_rvveSoHEgTBrWscE5CeZaPuACUHbw@mail.gmail.com \
--to=chrome.hiri.angry@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).