Changes

Jump to: navigation, search

Virtual Ethernet device

365 bytes removed, 09:24, 24 March 2012
no routing needed with multicast MACs
=== Virtual Ethernet devices can be joined in one bridge ===
Bridging a [[CT]] interface to a [[CT0]] interface is the magic that allows the [[CT]] to be an independent host on the network with its own IP address, gateway, etc. [[CT0]] does not need any configuration for forwarding packets to the [[CT]] or performing proxy arp for the [[CT]]or event the routing.
To manually configure a bridge and add devices to it, perform steps 1 - 4 from Simple configuration chapter for several containers and/or veth devices using FE:FF:FF:FF:FF:FF as a [[CT0]] veth side MAC address and then follow these steps.
[host-node]# ifconfig vzbr0 0
</pre>
 
==== Add routes in [[CT0]] ====
<pre>
[host-node]# ip route add 192.168.101.1 dev vzbr0
...
[host-node]# ip route add 192.168.101.n dev vzbr0
[host-node]# ip route add 192.168.102.1 dev vzbr0
...
...
[host-node]# ip route add 192.168.XXX.N dev vzbr0
</pre>
 
All routes to containers will be through this bridge and containers can communicate with each other even without these routes.
=== Automating the bridge ===
4
edits

Navigation menu