1 .\" Copyright (c) 2017 by Michael Kerrisk <mtk.manpages@gmail.com>
3 .\" %%%LICENSE_START(VERBATIM)
4 .\" Permission is granted to make and distribute verbatim copies of this
5 .\" manual provided the copyright notice and this permission notice are
6 .\" preserved on all copies.
8 .\" Permission is granted to copy and distribute modified versions of this
9 .\" manual under the conditions for verbatim copying, provided that the
10 .\" entire resulting derived work is distributed under the terms of a
11 .\" permission notice identical to this one.
13 .\" Since the Linux kernel and libraries are constantly changing, this
14 .\" manual page may be incorrect or out-of-date. The author(s) assume no
15 .\" responsibility for errors or omissions, or for damages resulting from
16 .\" the use of the information contained herein. The author(s) may not
17 .\" have taken the same level of care in the production of this manual,
18 .\" which is licensed free of charge, as they might when working
21 .\" Formatted or processed versions of this manual, if unaccompanied by
22 .\" the source, must acknowledge the copyright and authors of this work.
26 .TH NETWORK_NAMESPACES 7 2018-02-02 "Linux" "Linux Programmer's Manual"
28 network_namespaces \- overview of Linux network namespaces
30 Network namespaces provide isolation of the system resources associated
31 with networking: network devices, IPv4 and IPv6 protocol stacks,
32 IP routing tables, firewall rules, the
34 directory (which is a symbolic link to
38 directory, various files under
40 port numbers (sockets), and so on.
42 network namespaces isolate the UNIX domain abstract socket namespace (see
45 A physical network device can live in exactly one
47 When a network namespace is freed
48 (i.e., when the last process in the namespace terminates),
49 its physical network devices are moved back to the
50 initial network namespace (not to the parent of the process).
54 device pair provides a pipe-like abstraction
55 that can be used to create tunnels between network namespaces,
56 and can be used to create a bridge to a physical network device
58 When a namespace is freed, the
60 devices that it contains are destroyed.
62 Use of network namespaces requires a kernel that is configured with the
74 .BR user_namespaces (7),