Linux Network Namespace and five of its use cases
<blockquote>
<p>The <a href="https://man7.org/linux/man-pages/man7/network_namespaces.7.html" rel="noopener ugc nofollow" target="_blank">Network namespace</a> isolates the system’s <strong>physical</strong> network from the <strong>virtual</strong> network <strong>namespace</strong> within a single system. Each network namespace has its own interfaces, routing tables, forwarding rules, etc. Processes can be launched and dedicated to one network namespace. Linux network network namespace is widely used in OpenStack, docker, podman, cri-o, more..</p>
</blockquote>
<p>A physical network device can live in exactly one network<br />
namespace. When a network namespace is freed (i.e., when the<br />
last process in the namespace terminates), its physical network<br />
devices are moved back to the initial network namespace (not to<br />
the parent of the process).</p>
<p>A virtual network (<code><strong>veth</strong></code>) device pair provides a pipe-like<br />
abstraction that can be used to create tunnels between network<br />
namespaces, and can be used to create a bridge to a physical<br />
network device in another namespace. When a namespace is freed,<br />
the <code><strong>veth</strong></code> devices that it contains are destroyed.</p>
<p><a href="https://ramesh-sahoo.medium.com/linux-network-namespace-and-five-use-cases-using-various-methods-f45b1ec5db8f"><strong>Click Here</strong></a></p>