3 ms·
A good (the best?) way to solve that is 'the new namespace solution' described at the bottom of the page here: https://www.wireguard.com/netns/ https://www.wir
by OJFord 5y ago
A good (the best?) way to solve that is 'the new namespace solution' described at the bottom of the page here:
https://www.wireguard.com/netns/ https://www.wireguard.com/netns/
In brief, you move your physical eth/wlan device to a new namespace, and create the wg device in that namespace but then move it to the init ns.
By default (and without root) everything will use the init ns and only be able to reach the physical device via wg. If it's not active, nothing will even reach your NIC, nevermind the internet.
- kortilla 5y ago+1 to this being the safest way. No physical nic for your traffic to fallback to. The downside is this isn’t supported by any GUIs that I know of so it’s a pretty miserable workflow for WiFi.