network_namespaces(7)

💖 network_namespaces — bestie's guide to Linux network namespaces 💖

okay so this is a page from Miscellaneous Information Manual (section 7, the "overview" girlies), and it's literally all about <cyan>network_namespaces</cyan> — the Linux kind. come sit with me, we're gonna get you fluent. 🫶

---

✨ NAME ✨

network_namespaces — an overview of Linux network namespaces 💅

---

🌸 DESCRIPTION 🌸

so. network namespaces are giving isolation, and specifically they isolate all the system resources that have anything to do with networking. like:

• network devices 🔌
• the IPv4 and IPv6 protocol stacks
• IP routing tables
• firewall rules 🔥
• the /proc/net directory (which, plot twist, is a symbolic link to /proc/pid/net)
• the /sys/class/net directory
• various files under /proc/sys/net
• port numbers (sockets) 🧦
• and so on, you get the vibe

and as if that wasn't enough, network namespaces also isolate the UNIX domain abstract socket namespace (go read unix(7) for that one, bestie).

---

🎀 physical devices, one home only

a physical network device can live in exactly one network namespace. no polyamory, no sharing, one device one namespace. periodt.

and when a network namespace gets freed — which happens when the last process in that namespace terminates — its physical network devices get moved back to the initial network namespace. and here's the important bit, don't let anyone gaslight you: they go to the initial namespace, not to the namespace of the parent of the process. that distinction is iconic and also very easy to get wrong. 👑

---

🦋 veth pairs, the tunnel girlies

a virtual network (veth(4)) device pair is basically a pipe-like abstraction. it's the blueprint for:

• creating tunnels between network namespaces 🕳️
• creating a bridge to a physical network device that's sitting in another namespace

and the tragic part: when a namespace is freed, the veth(4) devices it contains are destroyed. gone. no forwarding address. 💀

---

🌈 kernel requirements (the vibe check)

using network namespaces requires a kernel that's configured with the CONFIG_NET_NS option. no option, no namespaces, no slay. that's the rules. 😭

---

⭐ SEE ALSO ⭐

the whole friend group, go say hi:

• nsenter(1)
• unshare(1)
• clone(2)
• veth(4)
• proc(5)
• sysfs(5)
• namespaces(7)
• user_namespaces(7)
• brctl(8)
• ip(8)
• ip-address(8)
• ip-link(8)
• ip-netns(8)
• iptables(8)
• ovs-vsctl(8)

---

and that's the whole page, bestie!! 🥳 this was Linux man-pages 6.20, dated 2026-02-08 — so when you cite this in your essay you know exactly which era of the lore we're in. k bye, go ip netns something, love u 💜🧚