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 20:54:41 +0100 [thread overview]
Message-ID: <CAHmME9rOLXhyCYVtR8m0TchxzeF_Azs_NL70um0n=y1YZNNe2g@mail.gmail.com> (raw)
In-Reply-To: <CACnYWRdj9ziO7dPvHscpiUNrQoBaENGHHOoyevrWFqU07vKpWg@mail.gmail.com>
On Mon, Nov 23, 2020 at 8:53 PM Ruben Di Battista
<rubendibattista@gmail.com> wrote:
>
> Ehi Jason!
>
> Thanks for the detailed answer. I just checked on the new 0.3 and the
> problem still persists. I'm not a network engineer, but I think it
> might be useful if you can provide more details in the Github issue
> (or the one I link in the second comment) that could help speed up the
> process...
If I can figure out more details, I'll post them. Right now I have
mostly speculation and haven't started dissecting WSL2's networking
quirks. I have subscribed to that issue though.
prev parent reply other threads:[~2020-11-23 19:56 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
2020-11-23 19:53 ` Ruben Di Battista
2020-11-23 19:54 ` Jason A. Donenfeld [this message]
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='CAHmME9rOLXhyCYVtR8m0TchxzeF_Azs_NL70um0n=y1YZNNe2g@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).