search

mullvad / mullvadvpn-app

The Mullvad VPN client app for desktop and mobile
https://mullvad.net/
GNU General Public License v3.0
5.15k stars 346 forks source link

Split tunneling breaks WSL networking #3624

Open jorik392 opened 2 years ago

jorik392 commented 2 years ago

Issue report

Operating system: Windows 10

App version: 2022.1

Issue description

Enabling split tunneling at all causes WSL version 1 network connectivity to stop working. If I split tunnel exclude any application even if it is unrelated to WSL this happens. Is there a way to make WSL work here?

dlon commented 2 years ago

Thanks for reporting this. I can reproduce this issue, but fixing it is not high priority right now. Is there a particular reason why you're using WSL1 rather than WSL2?

jorik392 commented 2 years ago

Hi @dlon, there are many reasons I use WSL1, some of the major reasons are faster access/performance for files within Windows, better compatibility and integration with Windows network/firewall and programs/services, much less resource heavy.

I really hope you can give some priority to this because currently it is a pain/almost impossible to use split tunneling.

LinuxOnTheDesktop commented 2 years ago

@dlon

I can reproduce this issue, but fixing it is not high priority right now.

Yet, this issue might be connected to #2877 (which looks serious!) and also to #3713.

daygumon commented 2 years ago

Operating System: Windows 10 Pro Version 21H2 Build 19044.1949

Mullvad App Version: 2022.4

WSL1

I just ran into this same issue. I have split tunneling enabled for a single unrelated application. For some reason, when I was reinstalling WSL2 Ubuntu, it was reinstalled as WSL1 Ubuntu.

Fortunately, in my case, I was originally using WSL2, so I just wsl --set-version Ubuntu 2 and now it's working again.

0xb01u commented 1 year ago

I just recently ran into this issue too, and wanted to add my own perspective to it.

@dlon

Is there a particular reason why you're using WSL1 rather than WSL2?

Yes. I had used WSL2 in the past, but there is a very obscure issue in Windows 10 where it will frequently BSOD if WSL2 is enabled and the Power saver power plan is being used. I like to keep the Power saver power plan active at all times as a personal preference, so I'd rather use WSL1.

(I don't recall exactly what the BSOD error name was since it's been many months now since I rolled back to WSL1 to enjoy a BSOD-free experience. Maybe the issue has already been fixed, but I haven't really needed to use WSL2 ever since, so I haven't checked.)

This split tunneling issue is not a deal breaker. But it is true that it greatly hinders the WSL1 users' use/experience of the split tunneling feature.