VEs and HNs in same subnets - Revision history

Tony: Added GATEWAY to ifcfg-eth0 example.

2013-11-26T13:20:10Z

Added GATEWAY to ifcfg-eth0 example.

66.91.219.97: /* Configure host bridge interfaces */

2013-03-22T03:17:16Z

‎Configure host bridge interfaces

66.91.219.97: Added examples to collect the hardware addresses of the physical ethernet interfaces.

2013-03-21T05:43:09Z

Added examples to collect the hardware addresses of the physical ethernet interfaces.

66.91.219.97: Added note to hard-code the MACADDR on the brN interfaces.

2013-03-21T05:37:55Z

Added note to hard-code the MACADDR on the brN interfaces.

Tony: /* Configure host bridge interfaces */

2012-07-15T12:01:14Z

‎Configure host bridge interfaces

Tony: Renaming of openvz-centric bridge interface names to generic interface names.

2012-07-15T11:59:18Z

Renaming of openvz-centric bridge interface names to generic interface names.

Tony: Renamed openvz-centric bridge interface names to more generic names.

2012-07-15T11:57:51Z

Renamed openvz-centric bridge interface names to more generic names.

Tony: Added note about case-sensitive Bridge TYPE and renamed openvz-centric bridge interface names to more generic names.

2012-07-15T11:56:09Z

Added note about case-sensitive Bridge TYPE and renamed openvz-centric bridge interface names to more generic names.

193.206.55.17: Bug 1723 was resolved - fixed.

2012-07-05T10:08:40Z

Bug 1723 was resolved - fixed.

82.162.8.170: /* Create the VE veth interfaces */

2012-04-09T22:46:33Z

‎Create the VE veth interfaces

@@ Line 124: / Line 124: @@
          NETMASK=yyy.yyy.yyy.yyy
          ONBOOT=yes
 .  Initialize the interfaces and restart the network service on the container.

← Older revision		Revision as of 03:17, 22 March 2013
Line 6:		Line 6:

	==Configure host bridge interfaces==		==Configure host bridge interfaces==
		+
		+	Steps 1 through 4 are done only once on the host.
		+
	1. (Optional) Verify that you can create a bridge interfaces for each physical interface on the host.		1. (Optional) Verify that you can create a bridge interfaces for each physical interface on the host.

@@ Line 13: / Line 13: @@
 If the above commands do not work you may need to install the bridge-utils package.
-.  Make note of the existing IP configuration in the hosts ifcfg-ethN files.  Then, modify the ifcfg-ethN files on the host so that they ONLY bridge to the corresponding brN interface.  /etc/sysconfig/network-scripts/ifcfg-eth0 should look like:
+.  Make note of the existing IP configuration in the hosts ifcfg-ethN files.  Also, record the hardware MAC addresses of the ethernet interfaces from the output of 'ifconfig'.
          DEVICE=eth0

@@ Line 37: / Line 37: @@
          ONBOOT=yes
          TYPE=Bridge
 Similarly, ifcfg-br1 should look like:
@@ Line 46: / Line 47: @@
          ONBOOT=yes
          TYPE=Bridge
 Note that TYPE 'Bridge' is case-sensitive.  Otherwise, the bridge interfaces will not initialize correctly during boot.
 .  On the host, do a 'service network restart' and verify the host has both IPv4 and IPv6 connectivity to its brN interfaces.

@@ Line 47: / Line 47: @@
          TYPE=Bridge
-Note that TYPE 'Bridge' is case-sensitive.
+Note that TYPE 'Bridge' is case-sensitive.  Otherwise, the bridge interfaces will not initialize correctly during boot.
 .  On the host, do a 'service network restart' and verify the host has both IPv4 and IPv6 connectivity to its brN interfaces.

@@ Line 68: / Line 68: @@
 ==Bridge the host and VE==
-.  Next we add the host vethN interfaces to the host bridged interfaces (vzbrN).
+.  Next we add the host vethN interfaces to the host bridged interfaces (brN).
 Create host:/etc/sysconfig/network-scripts/ifcfg-veth100.0
@@ Line 74: / Line 74: @@
          DEVICE=veth100.0
          ONBOOT=no
-         BRIDGE=vzbr0
+         BRIDGE=br0
 Create host:/etc/sysconfig/network-scripts/ifcfg-veth100.1

@@ Line 3: / Line 3: @@
 This describes a method of setting up networking for a host and its VEs such that the networking configuration for the VEs can be configured exactly as if the VEs were standalone hosts of their own in the same subnets or VLAN as the host.  This method makes use of the Virtual Ethernet device and bridges between the host and its containers.  This technique has the advantage of allowing IPv6 network configurations to work on both VEs and hosts as they normally would.  In particular, both hosts and VEs can use IPv6 autoconfiguration.  The network configuration of a VE can be identical to that of a non-VE system.
-In the following example the host has two physical interfaces and we are setting up the network configuration for VE 100.  The host IP configuration is moved out of the ethN interface configs and into the vzbrN interface config scripts (ifcfg-vzbr0 and ifcfg-vzbr1).  Ie. the host IP configuration will now reside on the vzbrN interfaces instead of the ethN interfaces.  The example also assumes IPv4 is configured statically, whereas IPv6 is auto-configured.
+In the following example the host has two physical interfaces and we are setting up the network configuration for VE 100.  The host IP configuration is moved out of the ethN interface configs and into the brN interface config scripts (ifcfg-br0 and ifcfg-br1).  Ie. the host IP configuration will now reside on the brN interfaces instead of the ethN interfaces.  The example also assumes IPv4 is configured statically, whereas IPv6 is auto-configured.
 ==Configure host bridge interfaces==
@@ Line 80: / Line 80: @@
          DEVICE=veth100.1
          ONBOOT=no
-         BRIDGE=vzbr1
+         BRIDGE=br1
 To make the above take effect, either start the VE,
@@ Line 88: / Line 88: @@
 Or if it's already started then manually add each VE interface to its corresponding bridge using:
-         /usr/sbin/brctl addif vzbr0 veth100.0
+         /usr/sbin/brctl addif br0 veth100.0
-         /usr/sbin/brctl addif vzbr1 veth100.1
+         /usr/sbin/brctl addif br1 veth100.1
 .  Verify each bridge includes the host interface and the veth interfaces for each VE:

@@ Line 8: / Line 8: @@
 .  (Optional) Verify that you can create a bridge interfaces for each physical interface on the host.
-         /usr/sbin/brctl addbr vzbr0
+         /usr/sbin/brctl addbr br0
-         /usr/sbin/brctl addbr vzbr1
+         /usr/sbin/brctl addbr br1
 If the above commands do not work you may need to install the bridge-utils package.
-.  Make note of the existing IP configuration in the hosts ifcfg-ethN files.  Then, modify the ifcfg-ethN files on the host so that they ONLY bridge to the corresponding vzbrN interface.  /etc/sysconfig/network-scripts/ifcfg-eth0 should look like:
+.  Make note of the existing IP configuration in the hosts ifcfg-ethN files.  Then, modify the ifcfg-ethN files on the host so that they ONLY bridge to the corresponding brN interface.  /etc/sysconfig/network-scripts/ifcfg-eth0 should look like:
          DEVICE=eth0
          BOOTPROTO=none
          ONBOOT=yes
-         BRIDGE=vzbr0
+         BRIDGE=br0
 Similarly ifcfg-eth1 will look like:
@@ Line 25: / Line 25: @@
          BOOTPROTO=none
          ONBOOT=yes
-         BRIDGE=vzbr1
+         BRIDGE=br1
 Note that the ifcfg-ethN files on the host do not contain any IP information anymore.
-.  Create ifcfg-vzbrN files and copy the IP configuration that was previously in the ifcfg-ethN files into ifcfg-vzbrN.  Here's what host:/etc/sysconfig/network-scripts/ifcfg-vzbr0 would look like assuming the IPv4 address is assigned statically and IPv6 auto-configuration (SLAAC) is used:
+.  Create ifcfg-brN files and copy the IP configuration that was previously in the ifcfg-ethN files into ifcfg-brN.  Here's what host:/etc/sysconfig/network-scripts/ifcfg-br0 would look like assuming the IPv4 address is assigned statically and IPv6 auto-configuration (SLAAC) is used:
-         DEVICE=vzbr0
+         DEVICE=br0
          BOOTPROTO=static
          IPADDR=xxx.xxx.xxx.xxx
          NETMASK=aaa.aaa.aaa.aaa
          ONBOOT=yes
-         TYPE=bridge
+         TYPE=Bridge
-Similarly, ifcfg-vzbr1 should look like:
+Similarly, ifcfg-br1 should look like:
-         DEVICE=vzbr1
+         DEVICE=br1
          BOOTPROTO=static
          IPADDR=yyy.yyy.yyy.yyy
          NETMASK=bbb.bbb.bbb.bbb
          ONBOOT=yes
-         TYPE=bridge
+         TYPE=Bridge
-.  On the host, do a 'service network restart' and verify the host has both IPv4 and IPv6 connectivity to its vzbrN interfaces.
+Note that TYPE 'Bridge' is case-sensitive.
 ==Create the VE veth interfaces==

@@ Line 146: / Line 146: @@
 and you will be good to go. The CT will now autoconfigure the network interfaces the next time it sees an RA.
-NOTE: Due to bug [http://bugzilla.openvz.org/show_bug.cgi?id=1723 1723] this setup might not work: Enabling the routing on CT0 can effectively kill all IPv6 connectivity for the CT, depending on the setup.
+NOTE: Due to bug [http://bugzilla.openvz.org/show_bug.cgi?id=1723 1723] this setup might not work: Enabling the routing on CT0 can effectively kill all IPv6 connectivity for the CT, depending on the setup. (This bug is reported to be solved since 2011-06-07, so this shouldn't be an issue anymore.)
 ==See also==

@@ Line 50: / Line 50: @@
 ==Create the VE veth interfaces==
-.  Create the VE as you normally would except do NOT specify any IP address, just the hostname.  Specifying an IP address during VE creation creates an unwanted venet interface which is not used in this configuration.
+.  Create the VE as you normally would, except do NOT specify any IP address, just the hostname.  Specifying an IP address during VE creation creates an unwanted venet interface which is not used in this configuration.
          /usr/sbin/vzctl create 100 --ostemplate name --hostname name