Comments on: Playing with Linux namespaces https://billauer.se/blog/2015/07/linux-namespaces-unshare/ Anything I found worthy to write down. Thu, 26 Mar 2026 13:15:15 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: eli https://billauer.se/blog/2015/07/linux-namespaces-unshare/comment-page-1/#comment-1188 eli Sun, 12 Jun 2016 13:26:54 +0000 https://billauer.se/blog/?p=4723#comment-1188 Thanks, Rami. I suppose it's a matter of different versions of unshare. Thanks, Rami. I suppose it’s a matter of different versions of unshare.

]]> By: Rami Rosen https://billauer.se/blog/2015/07/linux-namespaces-unshare/comment-page-1/#comment-1187 Rami Rosen Sun, 12 Jun 2016 12:54:19 +0000 https://billauer.se/blog/?p=4723#comment-1187 Hi Eli, Every newly created network namespace has its loopback device. >The loopback interface is absent unless enabled as shown >above. In fedora 23 and older releases, at least, there is no need for "ifconfig lo up", see the following sequence: unshare -n bash $ifconfig lo: flags=8 mtu 65536 loop txqueuelen 1 (Local Loopback) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Rami Rosen Hi Eli,
Every newly created network namespace has its loopback device.

>The loopback interface is absent unless enabled as shown >above.

In fedora 23 and older releases, at least, there is no need
for “ifconfig lo up”, see the following sequence:

unshare -n bash

$ifconfig

lo: flags=8 mtu 65536
loop txqueuelen 1 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Rami Rosen

]]>