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:
| $ProcessesById = @{} | |
| foreach ($Process in (Get-WMIObject -Class Win32_Process)) { | |
| $ProcessesById[$Process.ProcessId] = $Process | |
| } | |
| $ProcessesWithoutParents = @() | |
| $ProcessesByParent = @{} | |
| foreach ($Pair in $ProcessesById.GetEnumerator()) { | |
| $Process = $Pair.Value |
| #!/bin/bash -e | |
| #### | |
| # Helper script to update the Last modified timestamp of files in a Git SCM | |
| # Projects working Copy | |
| # | |
| # When you clone a Git repository, it sets the timestamp of all the files to the | |
| # time when you cloned the repository. | |
| # | |
| # This becomes a problem when you want the cloned repository, which is part of a | |
| # Web application have a proper cacheing mechanism so that it can re-cache files |