2 ms·
Regarding WebRTC-type leaks probably the best answer on Linux is to have a separate network namespace with only wg0 inside of it and then run your browser in th
by madars 5y ago
Regarding WebRTC-type leaks probably the best answer on Linux is to have a separate network namespace with only wg0 inside of it and then run your browser in the network namespace. Then the browser does not get to "see" the real egress interface/its IP and thus can't leak it even if it wanted to. Or, if you want this to apply for everything, move physical interface in its own namespace so all apps from the default namespace only see the WireGuard interface. See https://www.wireguard.com/netns/ https://www.wireguard.com/netns/
- thayne 5y agoI actually did something similar to this for slightly different use case. I needed to connect to two different VPNs simultaneously that had overlapping cidr ranges. So I created a network namespace for one of them, and used that for any connections that needed that VPN, and used the root network namespace for the other VPN. I did have to create two separate browser profiles though, since both firefox and chrome won't let you run multiple instances of the same profile simultaneously.