summaryrefslogtreecommitdiffstats
path: root/man7/network_namespaces.7
diff options
context:
space:
mode:
Diffstat (limited to 'man7/network_namespaces.7')
-rw-r--r--man7/network_namespaces.737
1 files changed, 19 insertions, 18 deletions
diff --git a/man7/network_namespaces.7 b/man7/network_namespaces.7
index 92ebc32ae..147c287cc 100644
--- a/man7/network_namespaces.7
+++ b/man7/network_namespaces.7
@@ -20,7 +20,7 @@ directory, various files under
port numbers (sockets), and so on.
In addition,
network namespaces isolate the UNIX domain abstract socket namespace (see
-.BR unix (7)).
+.MR unix 7 ).
.P
A physical network device can live in exactly one
network namespace.
@@ -31,13 +31,14 @@ initial network namespace
(not to the namespace of the parent of the process).
.P
A virtual network
-.RB ( veth (4))
+\%(\c
+.MR veth 4 )
device pair provides a pipe-like abstraction
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.
When a namespace is freed, the
-.BR veth (4)
+.MR veth 4
devices that it contains are destroyed.
.P
Use of network namespaces requires a kernel that is configured with the
@@ -45,18 +46,18 @@ Use of network namespaces requires a kernel that is configured with the
option.
.\" FIXME .SH EXAMPLES
.SH SEE ALSO
-.BR nsenter (1),
-.BR unshare (1),
-.BR clone (2),
-.BR veth (4),
-.BR proc (5),
-.BR sysfs (5),
-.BR namespaces (7),
-.BR user_namespaces (7),
-.BR brctl (8),
-.BR ip (8),
-.BR ip\-address (8),
-.BR ip\-link (8),
-.BR ip\-netns (8),
-.BR iptables (8),
-.BR ovs\-vsctl (8)
+.MR nsenter 1 ,
+.MR unshare 1 ,
+.MR clone 2 ,
+.MR veth 4 ,
+.MR proc 5 ,
+.MR sysfs 5 ,
+.MR namespaces 7 ,
+.MR user_namespaces 7 ,
+.MR brctl 8 ,
+.MR ip 8 ,
+.MR ip\-address 8 ,
+.MR ip\-link 8 ,
+.MR ip\-netns 8 ,
+.MR iptables 8 ,
+.MR ovs\-vsctl 8