Difference between revisions of "Containers/Networking"
m (added to Containers cat.) |
m (append Category Networking) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | [[Category: Containers]] | |
| + | [[Category: Networking]] | ||
There are several approaches of how to virtualize networking for containers. Those are desribed below. | There are several approaches of how to virtualize networking for containers. Those are desribed below. | ||
Latest revision as of 16:21, 24 January 2010
There are several approaches of how to virtualize networking for containers. Those are desribed below.
Contents
Layer 3 virtualized network interface[edit]
This one is employed by OpenVZ's venet. See venet.
Layer 2 virtualized network interface[edit]
This one is employed by OpenVZ's veth. See veth.
Layer 3 isolated network (bind filtering)[edit]
This one is implemented in Linux-VServer. Basically, when a container calls bind() with INADDR_ANY, kernel actually binds the socket to some specific IP address(es). Some more details (not much) can be found at http://linux-vserver.org/Paper#Network_Separation
