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 Ubuntu 22.04.2 LTS Lost internet access when VPNing with Citrix Secure Access #10104

Open
sugita01 opened this issue May 15, 2023 · 10 comments

Comments

@sugita01
Copy link

I have WSL 2 (Ubuntu 22.04.2 LTS) running on Win10 Enterprise ver 22H2.
When I start the Ubuntu 20.04 instance my WSL instance still have internet connectivity.
However, once I connect to my work VPN using Citrix Secure Access, i lost internet connectivity inside my Ubuntu WSL instance.
When I try ping www.afr.com.au, it results in:
ping :www.afr.com.au: Temporary failure in name resolution

I do get an IP address of 172.31.176.8. My cat /etc/resolv.conf is as below:

nameserver 8.8.8.8
nameserver 192.168.152.221
nameserver 192.168.152.231
nameserver 172.19.96.1
search companya.com.au.local

My vEthernet(WSL) is 172.31.176.1
when i tried to traceroute www.yahoo.com, it returns:
www.yahoo.com: Temporary failure in name resolution. Cannot handle 'host' cmdline arg 'www.yahoo.com' on position 1 (argc 1)

My /etc/wsl.conf is:

[network]
generateResolvConf = false

In my windows 10 cmd, when i try to run nslookup (whilst connected to vpn) it returns:
image

I also tried to turn off firewall in Windows Defender firewall settings, only for vEthernet WSL:
image

Below is the result of Get-NetIPInterface:
image

@zyition
Copy link

zyition commented May 22, 2023

You can try https://github.com/sakai135/wsl-vpnkit, it's a perfetc solution for me

@sugita01
Copy link
Author

I already tried that sakai135 script. Unfortunately, I still encountering the same error and my WSL box still unable to ping google.
My WSL box cant even ping the ip address of the windows host IP address. When trying to ping the Windows Host ip address, it just freeze and did not return anything. i have press Ctrl+C to break and exit it.

@zyition
Copy link

zyition commented May 23, 2023

did you try 2.x? Both version 3.x and 4.x don't work for me, but 2.x works well 🤣

@sugita01
Copy link
Author

no i didnt try version 2.x.
how do i get and try specific version?

@zyition
Copy link

zyition commented May 24, 2023

You can download specific versions by tag, for example: https://github.com/sakai135/wsl-vpnkit/releases/tag/v0.2.5. And read the documentation here https://github.com/sakai135/wsl-vpnkit/tree/v0.2.x

@sugita01
Copy link
Author

yup - tried version 0.2.5 and still same issue as well.

@dylangovender
Copy link

@sugita01 are you sure you installed V0.2.5 correctly?

I was in a very similar situation to yours. WSL2 had no network connectivity when the host machine was connected to Citrix Secure Access.

I tried the latest versions of the script but it did not help. I was about to give up but tried out 0.2.5 and it seems to be working.

Thanks for the tip, @zyition!

@terlar
Copy link

terlar commented May 20, 2024

I have connection working with the latest wsl-vpnkit 0.4.1. However trying to use anything else, e.g.

[wsl2]
networkingMode=mirrored
firewall=true
dnsTunneling=true
autoProxy=true

Doesn't work unless I also use wsl-vpnkit. Would be nice if it was possible to get to work without wsl-vpnkit. Any ideas what I could do to debug so we could once and for all figure out the root of the connectivity issue with Citrix Secure Access + WSL?

@TheGP
Copy link

TheGP commented Aug 23, 2024

@terlar where did you put those settings you wrote?

@zyition
Copy link

zyition commented Aug 26, 2024

@terlar where did you put those settings you wrote?

you can refer to this doc https://learn.microsoft.com/en-us/windows/wsl/wsl-config#wslconfig

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

5 participants