-
Notifications
You must be signed in to change notification settings - Fork 822
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
Unable to use VPN routes from within WSL 2 #7315
Comments
Probably duplicate of #7254 |
I have the same issue. When I connect to any connect I can't ping anything, if I disconnect from any connect I can ping or use netutils. I have remove and install WSL without success. |
Try to run the following commands inside your WSL
It helped me. I have had same issues while trying to fetch packages from NPM |
Thanks, I did that I VI to that file and change the servername to my local
ISP and that works thanks,
|
@ecalcutin @iroperto1 This is not my initial issue. My problem describes that only the VPN network itself is unusable from within WSL2, other outes are. This is not a DNS issue either, hence changing the This might actually be related: #4915 |
Actually I solved it. While digging a bit into other issues (e.g. #4201) I changed the VPN connection type from PPTP to SSL. Now everything works! |
How do you do change the connection type? |
Windows Build Number
10.0.19043.1165
WSL Version
Kernel Version
5.10.16.3
Distro Version
Ubuntu 18.04
Other Software
No response
Repro Steps
ping
corporate IP address or trying tossh
into it.Expected Behavior
Expecting 0% packet loss for
ping
and a workingssh
connection to corporate VPN servers from within WSL 2.Actual Behavior
Experiencing 95-100% packet loss for
ping
and no connection via ssh. (While same commands withincmd.exe
(and other software from within Windows that connect to corporate IP addresses) work flawlessly.)Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: