3 ms·
This is the most painful aspect of WSL2: if your org forces you to use a VPN your WSL2 is almost totally isolated from the network. Interestingly we have the sa
by bafe 3y ago
This is the most painful aspect of WSL2: if your org forces you to use a VPN your WSL2 is almost totally isolated from the network. Interestingly we have the same problem with our VPN and docker
- CJefferson 3y agoIf you haven't looked at it, look at the wsl-vpnkit (I mentioend above). Your org might not like it of course, but I found it fixed all my VPN-related issues (it's just another linux install you run as part of WSL2, which somehow connects everything together and by magic lets me get on the internet fine).
- bafe 3y agoI do use it and it works. Luckily I also got a full Linux PC for when I work from home, therefore I only need WSl the few times I am going to the office. The main issue now is the VPN messing up with routing and making containers inside WSL inaccessible from outside. Unfortunately wsl-vpnkit couldn't help there...
- hackandthink 3y agoPodman user mode networking may help. --user-mode-networking https://docs.podman.io/en/latest/markdown/podman-machine-init.1.html https://docs.podman.io/en/latest/markdown/podman-machine-ini...