Support static (named) network namespaces
phantomcraft opened this issue · 3 comments
phantomcraft commented
It would be a good idea the support for named namespaces (that created by $ ip netns add <some_ns>).
Two or more programs could use the same network stack.
Obviously this require root privileges.
stevenengler commented
I'm re-opening this since I think it would be useful, although I don't have any plans to work on it at the moment.
I think in general it would be useful as a way of providing the same "proxy bypass" protection for rootless docker/podman containers. You could create and run a no-network container, then start socksns with the namespace path so that the container could make external requests only through the socks port.
Allowing a namespace path should also allow named namespaces.