mirror of
https://git.proxmox.com/git/mirror_iproute2
synced 2025-10-05 16:49:09 +00:00
aab2702d33
lintian says: W: iproute: manpage-has-bad-whatis-entry usr/share/man/man7/tc-hfsc.7.gz W: iproute: manpage-has-bad-whatis-entry usr/share/man/man8/ip-address.8.gz W: iproute: manpage-has-bad-whatis-entry usr/share/man/man8/ip-addrlabel.8.gz W: iproute: manpage-has-bad-whatis-entry usr/share/man/man8/ip-link.8.gz W: iproute: manpage-has-bad-whatis-entry usr/share/man/man8/ip-maddress.8.gz W: iproute: manpage-has-bad-whatis-entry usr/share/man/man8/ip-monitor.8.gz W: iproute: manpage-has-bad-whatis-entry usr/share/man/man8/ip-mroute.8.gz W: iproute: manpage-has-bad-whatis-entry usr/share/man/man8/ip-neighbour.8.gz W: iproute: manpage-has-bad-whatis-entry usr/share/man/man8/ip-netns.8.gz W: iproute: manpage-has-bad-whatis-entry usr/share/man/man8/ip-ntable.8.gz W: iproute: manpage-has-bad-whatis-entry usr/share/man/man8/ip-route.8.gz W: iproute: manpage-has-bad-whatis-entry usr/share/man/man8/ip-rule.8.gz W: iproute: manpage-has-bad-whatis-entry usr/share/man/man8/ip-tunnel.8.gz W: iproute: manpage-has-bad-whatis-entry usr/share/man/man8/ip-xfrm.8.gz
69 lines
1.8 KiB
Groff
69 lines
1.8 KiB
Groff
.TH IP\-NETNS 8 "20 Dec 2011" "iproute2" "Linux"
|
|
.SH NAME
|
|
ip-netns \- process network namespace management
|
|
.SH SYNOPSIS
|
|
.sp
|
|
.ad l
|
|
.in +8
|
|
.ti -8
|
|
.B ip
|
|
.RI "[ " OPTIONS " ]"
|
|
.B netns
|
|
.RI " { " COMMAND " | "
|
|
.BR help " }"
|
|
.sp
|
|
.ti -8
|
|
.BR "ip netns" " { " list " } "
|
|
|
|
.ti -8
|
|
.BR "ip netns" " { " add " | " delete " } "
|
|
.I NETNSNAME
|
|
|
|
.ti -8
|
|
.BR "ip netns exec "
|
|
.I NETNSNAME command ...
|
|
|
|
.SH DESCRIPTION
|
|
A network namespace is logically another copy of the network stack,
|
|
with it's own routes, firewall rules, and network devices.
|
|
|
|
By convention a named network namespace is an object at
|
|
.BR "/var/run/netns/" NAME
|
|
that can be opened. The file descriptor resulting from opening
|
|
.BR "/var/run/netns/" NAME
|
|
refers to the specified network namespace. Holding that file
|
|
descriptor open keeps the network namespace alive. The file
|
|
descriptor can be used with the
|
|
.B setns(2)
|
|
system call to change the network namespace associated with a task.
|
|
|
|
The convention for network namespace aware applications is to look
|
|
for global network configuration files first in
|
|
.BR "/etc/netns/" NAME "/"
|
|
then in
|
|
.BR "/etc/".
|
|
For example, if you want a different version of
|
|
.BR /etc/resolv.conf
|
|
for a network namespace used to isolate your vpn you would name it
|
|
.BR /etc/netns/myvpn/resolv.conf.
|
|
|
|
.B ip netns exec
|
|
automates handling of this configuration, file convention for network
|
|
namespace unaware applications, by creating a mount namespace and
|
|
bind mounting all of the per network namespace configure files into
|
|
their traditional location in /etc.
|
|
|
|
.SS ip netns list - show all of the named network namespaces
|
|
.SS ip netns add NAME - create a new named network namespace
|
|
.SS ip netns delete NAME - delete the name of a network namespace
|
|
.SS ip netns exec NAME cmd ... - Run cmd in the named network namespace
|
|
|
|
.SH EXAMPLES
|
|
|
|
.SH SEE ALSO
|
|
.br
|
|
.BR ip (8)
|
|
|
|
.SH AUTHOR
|
|
Original Manpage by Eric W. Biederman
|