From: Christopher Ng <facboy@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Wireguard over VPN broken on windows
Date: Sun, 21 Jun 2020 11:17:44 +0100 [thread overview]
Message-ID: <CAN5wt5r_qoLFrZM6T2CJ6UhQpcqFTqf5AHUugpe0rN5LuL3YLQ@mail.gmail.com> (raw)
I raised an issue on github which was closed, and issues seem to have
been disabled on github now so I can't respond there.
59e556f on wireguard-go breaks Wireguard working over OpenVPN on
windows. It only ever worked in my private builds as there was no
public release of wireguard-windows that included 66ad537 (which
fixed a routing problem in wireguard-windows). Now with
wireguard-windows 0.1.1 Wireguard over an OpenVPN tunnel no longer
works again. I have triaged it with my own private builds of
wireguard-windows and 59e556f is where it starts breaking.
next reply other threads:[~2020-06-22 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 10:17 Christopher Ng [this message]
2020-06-22 8:23 ` Jason A. Donenfeld
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=CAN5wt5r_qoLFrZM6T2CJ6UhQpcqFTqf5AHUugpe0rN5LuL3YLQ@mail.gmail.com \
--to=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).