From: Andre Naujoks <nautsch2@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: wireguard windows socket binds to device
Date: Tue, 25 May 2021 12:34:35 +0200 [thread overview]
Message-ID: <bd20cfa0-9cc4-83fb-ec53-e2e84923c485@gmail.com> (raw)
Hi all.
I am currently trying to create a wireguard tunnel over another VPN
under windows.
The setup would be a wirguard tunnel through an openvpn connection.
However the wireguard implementation on windows forcibly binds itself to
the network device with the default route (which is fortunately visible
in the wireguard log).
The wireguard peer however resides inside the other VPN and is thus not
reached by the windows client.
Is there a reason why the routing of the host machine is forcibly
bypassed by binding to a specific network device or is this simply a bug
in the windows implementation?
Best regards and thanks in advance
Andre
next reply other threads:[~2021-05-26 11:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 10:34 Andre Naujoks [this message]
2021-05-26 14:37 ` Jason A. Donenfeld
2021-05-27 9:22 ` Andre Naujoks
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=bd20cfa0-9cc4-83fb-ec53-e2e84923c485@gmail.com \
--to=nautsch2@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).