Crates.io | netns-exec |
lib.rs | netns-exec |
version | 0.2.2 |
source | src |
created_at | 2020-02-15 09:14:11.3321 |
updated_at | 2020-09-30 21:41:21.088411 |
description | Execute process in Linux network namespace |
homepage | |
repository | https://github.com/johnae/netns-exec |
max_upload_size | |
id | 209404 |
size | 9,012 |
This is a super simple command for executing a process within a Linux network namespace. I personally use it to run my whole desktop within a namespace where there's only a wireguard interface, but you could use it for other reasons as well.
The wireguard dev himself suggests creating all unencrypted network interfaces (like eth0
or wlan0
) together with the wireguard interface within a certain network namespace and then you move the wireguard interface out of there into the init
(eg. main) network namespace while leaving its socket in the original namespace (together with the unencrypted ones). That way, your init
network namespace will only have a wireguard interface so everything goes over that interface (and no fiddling with routes etc needed).
This is obviously really cool and what you'd probably want to do if you can... unfortunately it can be a bit difficult to make all that work, starting dhcpd, wpa_supplicant or iwd in a different network namespace. So, this instead enables me to run my desktop within a namespace into which I've moved only the wireguard interface, leaving the wlan0 etc. in the init
namespace.
If you wish to enter a named network namespace, you must ofc create the network namespace before you can run this command, when you've created it - you can run this like so:
netns-exec <namespace> cmdline here
A more concrete example would be:
netns-exec private sway
It is also possible to enter the network namespace of any process via its pid - for example, entering pid 1:s network namespace would be done like this:
netns-exec 1 bash
That would get you a bash shell in the network namespace of pid 1 (which basically means the "main" or "global" network namespace).
For this to be runnable as a normal user without sudo, you need to set the setuid
bit (and the executable should be owned by root ofc). As soon as we've switched network namespace (a privileged operation), we drop privileges.