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

Cisco Anyconnect blocks DNS access from WSL2 #11075

Open
1 of 2 tasks
jstroehmann opened this issue Jan 24, 2024 · 4 comments
Open
1 of 2 tasks

Cisco Anyconnect blocks DNS access from WSL2 #11075

jstroehmann opened this issue Jan 24, 2024 · 4 comments
Labels

Comments

@jstroehmann
Copy link

Windows Version

Microsoft Windows [Version 10.0.19045.3930]

WSL Version

2.0.9.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.133.1-1

Distro Version

22.04

Other Software

No response

Repro Steps

When I am connected to the VPN:

$ host archive.ubuntu.com
;; communications error to 172.18.96.1#53: timed out
;; communications error to 172.18.96.1#53: timed out
;; no servers could be reached

Expected Behavior

When I am disconnected from the VPN:

$ host archive.ubuntu.com
archive.ubuntu.com has address 185.125.190.36
archive.ubuntu.com has address 91.189.91.82
archive.ubuntu.com has address 91.189.91.81
archive.ubuntu.com has address 91.189.91.83
archive.ubuntu.com has address 185.125.190.39
archive.ubuntu.com has IPv6 address 2620:2d:4002:1::101
archive.ubuntu.com has IPv6 address 2620:2d:4002:1::103
archive.ubuntu.com has IPv6 address 2620:2d:4000:1::16
archive.ubuntu.com has IPv6 address 2620:2d:4002:1::102
archive.ubuntu.com has IPv6 address 2620:2d:4000:1::19

Actual Behavior

When I am connected to the VPN:

$ host archive.ubuntu.com
;; communications error to 172.18.96.1#53: timed out
;; communications error to 172.18.96.1#53: timed out
;; no servers could be reached

Diagnostic Logs

No response

Copy link

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@j-potts
Copy link

j-potts commented Jan 26, 2024

I'd recommend using https://github.com/sakai135/wsl-vpnkit

...and setting it up using the systemd method.

@smax413
Copy link

smax413 commented Jan 31, 2024

SSH using VPN hangs with 'set_sock_tos: set socket 3 IP_TOS 0x10'

On a Windows 11 server I was able to ssh without VPN successfully.
Once my VPN was enabled (Cisco AnyConnect) I was unable to ssh, or access anything on the network.
The ssh -vvv @ hangs at: 'set_sock_tos: set socket 3 IP_TOS 0x10'

After much grief, the fix was to reinstall the Microsoft Windows 11 default VPN router, versus use our Cisco AnyConnect client.

Note: I had Windows 10 and had no issues when using Cisco AnyConnect VPN and ssh.

@CatalinFetoiu
Copy link
Collaborator

hello, thanks for reporting the issue and sorry for the delay following up

I recommend using networkingMode=mirrored and dnsTunneling=true in your wslconfig file, those will improve compatibility with VPNs

if you need to use the default networkingMode=nat, there is known issue and workaround provided by Cisco here

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

No branches or pull requests

5 participants