Internet connection and DNS routing are broken from WSL2 instances, when some VPNs are active.
The root cause seems to be that WSL2 and the VPN use the same IP address block, and the VPN routing clobbers WSL2's network routing.
This problem is tracked in multiple microsoft/WSL issues including, but not limited to:
WSL 2 uses a Hyper-V Virtual Network adapter. Network connectivity works without any issue when a VPN is not in use. However when a Cisco AnyConnect VPN session is established Firewall Rules and Routes are added which breaks connectivity within the WSL 2 VM. This issue is tracked WSL/issues/4277
Below outline steps to automatically configure the Interface metric on VPN connect and update DNS settings (/etc/resolv.conf) on connect/disconnect.
| #Requires -Version 3.0 | |
| # Configure a Windows host for remote management with Ansible | |
| # ----------------------------------------------------------- | |
| # | |
| # This script checks the current WinRM (PS Remoting) configuration and makes | |
| # the necessary changes to allow Ansible to connect, authenticate and | |
| # execute PowerShell commands. | |
| # | |
| # All events are logged to the Windows EventLog, useful for unattended runs. |