Cisco anyconnect ubuntu windows#

I tested the Anyconnect interface metric, to find the exact value where WSL stops working, and the minimum working value is 270.Д«elow, Ethernet 2 is the Anyconnect adapter. When Anyconnect metric is increased, vEthernet traffic is routed in a way that Anyconnect can grab and re-route it through the VPN and get the responses back to WSL2. My working theory is that Anyconnect is intercepting WSL2 traffic, so it doesn't properly go through vEthernet, and responses don't make it back. Anyconnect is probably stepping on something in vEthernet. My sense is that the VPN is more invasive than just becoming the lowest metric interface, and I agree with your idea that the real problem is in vEthernet(WSL) or more likely vEthernet(Default Switch).

Cisco anyconnect ubuntu windows#

Traceroute from WSL2 and tracert from windows side both report going through the corportate network before hitting the internet.

This probably would work but as I said you're basically just disabling the VPN and I don't want that.ДЇrom my observations, changing the Anyconnect adapter metric does not allow anything to bypass the Anyconnect VPN. I have been researching why WSL 2 seems to have issues with VPNs and I haven't found an answer that works yet. Maybe I'm not understanding something or missing something but it just doesn't seem like anyone should do this if they really want to use their VPN. Which means all network traffic is no longer using it and that means it is the same as just disconnecting your VPN. Increasing the metric value on your VPN's connection is basically telling your operating system to ignore your VPN connection. When Anењњonnect finishes connecting, a Powershell window pops up for a couple seconds and WSL can reach the I'm confused at how this is a good idea to do. : 123.45.67.89 Start the task only if the computer is on AC Power : Cisco Anењњonnect Secure Mobility Client Virtual Miniport Adapter for Windows ењ†4 To get addresses, use ipconfig /all from CMD or Powershell prompt, and check the details of the VPN adapter: Description. Next, manually add the corportate DNS Server as the first nameserver in /etc/nf. The path to this file is from the shell prompt of your WSL2 instance. The list of nameservers must be manually built to include some sane default DNS Name Servers and the DNS from the VPN.ДЇirst, disable automatically generating /etc/nf.ДЄdd the following configuration, or create the file if it doesn't exist. When the VPN is active, the autogenerated /etc/nf does not work. Ping to IP Addresses succeed, but still no DNS Resolution. When the VPN connection is active, network traffic out of WSL2 is not passed to the internet.Д¬hanging the Interface Metric 1 -> 6000 for Anењњonnect VPN Adapter resolves the connection issue, but this has to be done after each time the VPN connects.Д«y default, the Interface Metrics for Anењњonnect are:Д¬hanging the Interface Metrics for Anењњonnect to: This problem is tracked in multiple microsoft/WSL issues including, but not limited to: The workaround breaks down into two problems: Internet connection and DNS routing are broken from WSL2 instances, when some VPNs are active.