From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Ruben Di Battista <rubendibattista@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WSL2 and Wireguard
Date: Mon, 23 Nov 2020 17:50:51 +0100 [thread overview]
Message-ID: <CAHmME9qyVb7kuj+VYAaQRqZ-i_Mptr6_2BGGoz+wf5Ke4WXUMw@mail.gmail.com> (raw)
In-Reply-To: <CACnYWReJC+Ff8G+uWLW6i=rsR1w=O-6aDFBG-yd__ZuuRh83CA@mail.gmail.com>
Hi Ruben,
On Mon, Nov 23, 2020 at 5:43 PM Ruben Di Battista
<rubendibattista@gmail.com> wrote:
>
> Hello,
>
> I'm experiencing a problem with Wireguard and WSL2. If I activate my
> tunnel and then I ping a machine on the VPN IP range from WSL2, I
> don't get any response.
>
> However, if after activating Wireguard, I ping from cmd or PowerShell,
> I successfully get the ping back and I'm able then also to ping from
> WSL2.
>
> I'm not sure if this is related to Wireguard or WSL2, In any case I
> reported the bug here: https://github.com/microsoft/WSL/issues/5810
>
> Is it a problem of my machine, a problem from WSL2 or Windows Wireguard?
That's pretty weird. I've seen a few related bugs like that, where it
seems like WSL will drop packets that don't meet some unusual stateful
criteria. I don't know if they're trying to do some kind of connection
tracking, or if the routing logic is partially broken for NdisMediumIP
devices.
I assume you're experiencing this using the latest WireGuard 0.3 [1]?
To answer your direct question, though, I think this might be a WSL
problem rather than a WireGuard problem. If that Github issue doesn't
get any attention after some time, I can try to reverse engineer the
hyper-v networking drivers to see what's going on, but as always with
that kind of thing, no guarantees on its success.
Jason
[1] https://lists.zx2c4.com/pipermail/wireguard/2020-November/006075.html
next prev parent reply other threads:[~2020-11-23 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 16:01 Ruben Di Battista
2020-11-23 16:50 ` Jason A. Donenfeld [this message]
2020-11-23 19:53 ` Ruben Di Battista
2020-11-23 19:54 ` Jason A. Donenfeld
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=CAHmME9qyVb7kuj+VYAaQRqZ-i_Mptr6_2BGGoz+wf5Ke4WXUMw@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=rubendibattista@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).