* Apparent Windows routing bug when switching between VPNs
@ 2020-09-19 20:21 Jeremy Howard
0 siblings, 0 replies; only message in thread
From: Jeremy Howard @ 2020-09-19 20:21 UTC (permalink / 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:
Let me know if there's any other info I could provide.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, back to index
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-19 20:21 Apparent Windows routing bug when switching between VPNs Jeremy Howard
WireGuard Archive on lore.kernel.org
Archives are clonable:
git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
Example config snippet for mirrors
Newsgroup available over NNTP:
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git