mirror of https://github.com/mkerrisk/man-pages
network_namespaces.7: Reorganize text
No content changes... Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
2685b303e3
commit
f051ce24ac
|
@ -37,8 +37,14 @@ IP routing tables, firewalls, the
|
|||
directory, the
|
||||
.I /sys/class/net
|
||||
directory, port numbers (sockets), and so on.
|
||||
.PP
|
||||
A physical network device can live in exactly one
|
||||
network namespace.
|
||||
When a network namespace is freed
|
||||
(i.e., when the last process in the namespace terminates),
|
||||
its physical network devices are moved back to the
|
||||
initial network namespace (not to the parent of the process).
|
||||
.PP
|
||||
A virtual network
|
||||
.RB ( veth (4))
|
||||
device pair provides a pipe-like abstraction
|
||||
|
@ -46,11 +52,6 @@ that can be used to create tunnels between network namespaces,
|
|||
and can be used to create a bridge to a physical network device
|
||||
in another namespace.
|
||||
.PP
|
||||
When a network namespace is freed
|
||||
(i.e., when the last process in the namespace terminates),
|
||||
its physical network devices are moved back to the
|
||||
initial network namespace (not to the parent of the process).
|
||||
.PP
|
||||
Use of network namespaces requires a kernel that is configured with the
|
||||
.B CONFIG_NET_NS
|
||||
option.
|
||||
|
|
Loading…
Reference in New Issue