[lkml]   [2006]   [Jun]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[RFC] [patch 0/6] [Network namespace] introduction
The following patches create a private "network namespace" for use
within containers. This is intended for use with system containers
like vserver, but might also be useful for restricting individual
applications' access to the network stack.

These patches isolate traffic inside the network namespace. The
network ressources, the incoming and the outgoing packets are
identified to be related to a namespace.

It hides network resource not contained in the current namespace, but
still allows administration of the network with normal commands like

It applies to the kernel version 2.6.17-rc6-mm1

It provides the following:
- when an application unshares its network namespace, it looses its
view of all network devices by default. The administrator can
choose to make any devices to become visible again. The container
then gains a view to the device but without the ip address
configured on it. It is up to the container administrator to use
ifconfig or ip command to setup a new ip address. This ip address
is only visible inside the container.

- the loopback is isolated inside the container and it is not
possible to communicate between containers via the

- several containers can have an application bind to the same
address:port without conflicting.

What is for ?
- security : an application can be bounded inside a container
without interacting with the network used by another container

- consolidation : several instance of the same application can be
ran in different container because the network namespace allows
to bind to the same addr:port

What could be done ?
- because the network ressources are related to a namespace, it is
easy to identify them. That facilitate the implementation of the
network migration

How to use ?
- do unshare with the CLONE_NEWNET flag as root
- do echo eth0 > /sys/kernel/debug/net_ns/dev
- use ifconfig or ip command to set a new ip address

What is missing ?
The routes are not yet isolated, that implies:

- binding to another container's address is allowed

- an outgoing packet which has an unset source address can
potentially get another container's address

- an incoming packet can be routed to the wrong container if there
are several containers listening to the same addr:port

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-06-09 23:09    [W:0.237 / U:0.308 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site