From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Christopher Ng <facboy@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard over VPN broken on windows
Date: Mon, 22 Jun 2020 02:23:21 -0600 [thread overview]
Message-ID: <CAHmME9pfyKr62RrAmV81NKs938CmQbqRtcab=yJzKw9V8iMc1A@mail.gmail.com> (raw)
In-Reply-To: <CAN5wt5r_qoLFrZM6T2CJ6UhQpcqFTqf5AHUugpe0rN5LuL3YLQ@mail.gmail.com>
> 59e556f on wireguard-go breaks
59e556f fixes a regression, which never shipped in any release. There
is nothing here that "once worked and now doesn't." What you have in
mind has never worked.
We're currently using IP_UNICAST_IF on the wireguard socket, attaching
it to the default route. I'd much rather have something like Linux's
policy routing and suppress_prefixlen, but I don't know how to do that
(yet?) on Windows. If you have any ideas or want to do some research,
I'd certainly be very interested.
next prev parent reply other threads:[~2020-06-22 8:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 10:17 Christopher Ng
2020-06-22 8:23 ` Jason A. Donenfeld [this message]
2020-06-22 10:56 ` Christopher Ng
2020-06-22 13:15 ` Peter Whisker
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='CAHmME9pfyKr62RrAmV81NKs938CmQbqRtcab=yJzKw9V8iMc1A@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=facboy@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).