Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WSL2 Issues with VPNs (Viscosity) #4728

Closed
Einlanzerous opened this issue Dec 3, 2019 · 1 comment
Closed

WSL2 Issues with VPNs (Viscosity) #4728

Einlanzerous opened this issue Dec 3, 2019 · 1 comment

Comments

@Einlanzerous
Copy link

  • Your Windows build number: 2004 (BUILD 19033.1)

  • What you're doing and what's happening: Using Ubuntu with VSCode, everything works as intended. Connect to a work VPN via Viscosity, everything in Windows works as expected (can access sites both on work network and off), Ubuntu cannot reach any internet locations. Checking Network Connections shows that the vEthernet adapter is unplugged. Cannot resolve this without restarting the machine.

  • What's wrong / what should be happening instead: Expect WSL2 instance to be able to reach VPN network resources as before (builds 19030 worked, as did 19025)

Not a lot of information to post, as there isn't really an error, the network connection just thinks it isn't connected anymore. Submitted to feedback hub as well, but figured I'd post here in-case others had seen problems with this.

@Einlanzerous
Copy link
Author

Of note- if you connect to the VPN before starting Ubuntu- everything works as intended. It's only an issue if you connect WHILE Ubuntu is running (or has been run, I haven't seemed to have luck trying to trick it by running wsl -t ubuntu before connecting the VPN).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants