4 ms·
This is the exact reason I didn't try running weird VPN configs like this. The reliable way is to run Linux inside a VirtualBox and have it connected to VPN on
by sally1620 6y ago
This is the exact reason I didn't try running weird VPN configs like this. The reliable way is to run Linux inside a VirtualBox and have it connected to VPN on its own.
Currently, I run Linux on a Xen domU and configure VPN client inside the guest.
PS: I don't want all my traffic to go through VPN. Especially things like Netflix or Youtube where VPNs are blocked (and VPN BW is lower anyway).
- adriancr 6y agoYou can set up a docker vpn client as well
- sally1620 6y agoI tried docker. "Always Require VPN" didn't work with docker.
- adriancr 6y agoI do it like this, can provide scripts if you're interested. One docker image with openvpn: 1. at startup erases all routes except to VPN gateway and 8.8.8.8. 2. before and after connect it only has routes through VPN (no default ones - if vpn goes down, network goes down until re-established) Start it like: # ... --name vpn ... Another docker image with what I want VPNed gets started with the network of the first # ... --net container:vpn ... I keep a browser within the second docker image (firefox) and use my main machine to show it. Note: you want to pass '--no-remote' to it and likely split /dev/shm It can't really leak since it doesn't have routes to do anything other then through VPN.
- garethrowlands 6y agoWSL2 _is_ Linux inside a VM that's a peer of Windows. Having it connect to VPN on its own is _exactly_ what you have to do.
- sally1620 6y agoIt is a VM with a lot of hacks. For most tasks it is good but for complicated situations it will get you. I used to run Linux VM inside HyperV before WSL2 released, and it worked like a charm. WSL2 just adds a lot of hacks to integrate Windows & Linux experience.