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

WSL 2 Internet connection doesn't work until I connect to VPN #5784

Closed
N-Molham opened this issue Aug 19, 2020 · 6 comments
Closed

WSL 2 Internet connection doesn't work until I connect to VPN #5784

N-Molham opened this issue Aug 19, 2020 · 6 comments

Comments

@N-Molham
Copy link

Environment

Windows build number: `10.0.19041.0`
Your Distribution version: `Ubuntu 20.04`
Whether the issue is on WSL 2 and/or WSL 1: WSL2

To make internet connection working on WSL2 machine, I have to connect to VPN (Wire Guard) first, otherwise it doesn't work

This wasn't the case, it was working fine (with TunSafe VPN client) installed without any issue, I believe this issue surfaced after the latest windows update a couple of days ago. I am not sure what causing this problem, windows update is the only thing changes without me doing anything.

Steps to reproduce

  1. Connect to VPN, I use TunSafe
  2. In WSL2 I have to edit /etc/resolv.conf and change the nameserver from 172.20.144.1 to something like 1.1.1.1 or 8.8.8.8
  3. If I changed the nameserver back or disconnect from the VPN, internet connection stops

WSL logs: I tried to follow the steps but I didn't get the last option/tab which I can collect the logs

Expected behavior

I should have internet connection on my WSL2 machine

Actual behavior

As described, I have to connect to VPN server and change nameserver to make it work

More data

Network adapters

image

Wi-Fi Adapter sharing settings, I already tried turning this on/off states

image

WSL Adapter

image

Default Switch adapter

image

Hope this helps to solve the problem that I am having as I need WSL for my web development work

@wushangwei
Copy link

I once had the opposite problem: WSL2 lost internet connection when connected to WIreGuard VPN.

I solved the problem by editing the "AllowedIPs“ field of WireGuard conf:
`[Interface]
PrivateKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Address = 10.88.88.2/24
DNS = 1.1.1.1

[Peer]
PublicKey = yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy
PresharedKey = zzzzzzzzzzzzzzzzzzzzzzzzzzzzz
AllowedIPs = ::/128, 0.0.0.0/1, 128.0.0.0/1
Endpoint = xxx.xxx.xxx.xxx:xxxxx`

Hope it will help you.

@N-Molham
Copy link
Author

Thanks @wushangwei it worked

@rajnathsah
Copy link

Run below from powershell in admin mode for cisco any connect vpn.

Get-NetAdapter | Where-Object {$_.InterfaceDescription -Match "Cisco AnyConnect"} | Set-NetIPInterface -InterfaceMetric 4000
Get-NetIPInterface -InterfaceAlias "vEthernet (WSL)" | Set-NetIPInterface -InterfaceMetric 1

@jrgilman
Copy link

I once had the opposite problem: WSL2 lost internet connection when connected to WIreGuard VPN.

I solved the problem by editing the "AllowedIPs“ field of WireGuard conf:
`[Interface]
PrivateKey = xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Address = 10.88.88.2/24
DNS = 1.1.1.1

[Peer]
PublicKey = yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy
PresharedKey = zzzzzzzzzzzzzzzzzzzzzzzzzzzzz
AllowedIPs = ::/128, 0.0.0.0/1, 128.0.0.0/1
Endpoint = xxx.xxx.xxx.xxx:xxxxx`

Hope it will help you.

This worked for us just now! Awesome :) No idea why though, 0.0.0.0/0 should be identical to 0.0.0.0/1 and 128.0.0.0/1???

@juanmirocks
Copy link

If you are using WireGuard VPN, this might help: #5784 (comment)

@mys2kor
Copy link

mys2kor commented Apr 24, 2024

Run below from powershell in admin mode for cisco any connect vpn.

Get-NetAdapter | Where-Object {$_.InterfaceDescription -Match "Cisco AnyConnect"} | Set-NetIPInterface -InterfaceMetric 4000 Get-NetIPInterface -InterfaceAlias "vEthernet (WSL)" | Set-NetIPInterface -InterfaceMetric 1

Hi, I am having the same issue (WSL 2 Internet connection doesn't work until I connect to VPN) but I use cisco any connect vpn. I tried running the commands you mentioned but I get error. I am running Windows 11. Further details of my issue can be found here.
image

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

No branches or pull requests

6 participants