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.

Cisco anyconnect ubuntu