In my last article on WSL 2 VPN issues, I detailed the most common networking problems that occur when using WSL 2 and a VPN at the same time. I have since created a Windows service that will automatically correct any conflicting routes that exist between WSL and your VPN.
If you would simply like to use the service, you can download wslroutesvc.exe and run .\wslroutesvc.exe install from PowerShell as an administrator.
If you are interested in how this service functions, read on.
Windows Subsystem for Linux (WSL) provides huge benefits to developers. It opens a whole world of Linux applications, improves your Docker performance, and lets you bash to your heart’s content. The Premier Developer blog at Microsoft has a glowing post about WSL with more of the details if you are so inclined.
Unfortunately, all of this functionality does not come without its troubles. Since switching to WSL 2, I have been unable to initiate any network connections within WSL when connected to my VPN. This is not a rare problem, but none of the existing issues on the WSL GitHub page worked for me.
This post details all of the solutions I tried and the one that finally worked.