From: "Jeremy Howard" <forum@jhoward.fastmail.fm>
To: wireguard@lists.zx2c4.com
Subject: Apparent Windows routing bug when switching between VPNs
Date: Sat, 19 Sep 2020 13:21:34 -0700 [thread overview]
Message-ID: <82dd10dc-ee1d-45a7-a82c-1739e1048e5e@www.fastmail.com> (raw)
I just started using wireguard, after using openvpn for quite a while. I've seen a semi-regular bug when using wireguard from Windows 10. I find if I switch from one vpn to another, by deactivating one and activating another, and then I switch back to the first one, I often find that I can no longer connect to servers in that 1st vpn. I get the handshake, but can't actually connect to anything after that - perhaps some issue with the Windows routing table?
Oddly, to fix it, I find that I have to edit the config in wireguard windows - e.g by changing the order of the lines in the text
Then I find I can connect again. Even rebooting doesn't fix it - only editing the config (e.g by changing the order of the lines) works.
It seems to happen with different servers in different locations, but here's a server conf dump if it helps:
https://0x0.st/ilqo.txt
Let me know if there's any other info I could provide.
reply other threads:[~2020-09-20 22:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=82dd10dc-ee1d-45a7-a82c-1739e1048e5e@www.fastmail.com \
--to=forum@jhoward.fastmail.fm \
--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).