You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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).
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.
The text was updated successfully, but these errors were encountered: