OpenVZ on Funtoo Linux - Revision history

Cyball at 02:02, 15 January 2013

2013-01-15T02:02:07Z

2013-01-13T22:38:43Z

‎venet networking

2013-01-13T22:38:21Z

‎Using The Bridge

2013-01-13T22:37:34Z

‎Network - After

2013-01-13T13:37:49Z

‎Networking

2012-08-08T04:24:48Z

‎venet networking

2012-06-16T16:58:08Z

‎Funtoo Linux OpenVZ Templates

2012-06-16T16:57:38Z

‎Configuration

2012-06-16T16:56:52Z

‎venet networking

2012-06-16T16:55:11Z

‎Resource Limits

← Older revision		Revision as of 02:02, 15 January 2013
Line 108:		Line 108:

	If you want to bridge the wlan0 device, you'll need the additional wpa_supplicant flag '''''-b br0''.'''		If you want to bridge the wlan0 device, you'll need the additional wpa_supplicant flag '''''-b br0''.'''
		+	In most cases for wlan0 it is much better to use a route:
		+	<console>
		+	# ##i##iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -o wlan0 -j SNAT your_host_ip_address
		+	</console>

	Now, time to create a new /etc/conf.d/netif.eth0, but this time we won't associate an IP address with it. Config file looks like this, a single line:		Now, time to create a new /etc/conf.d/netif.eth0, but this time we won't associate an IP address with it. Config file looks like this, a single line:

@@ Line 159: / Line 159: @@
 "venet" is OpenVZ's other form of host networking. It can be easier to configure than veth, but does not allow the use of broadcast or multicast, so DHCP is not possible on the VE side. For this reason, an IP address must be statically assigned to the VE, as follows:
-<pre>
+<console>
-# vzctl set 100 --ipadd 10.0.1.201 --save
+# ##i##vzctl set 100 --ipadd 10.0.1.201 --save
-# vzctl set 100 --nameserver 8.8.4.4 --save #google public DNS server
+# ##i##vzctl set 100 --nameserver 8.8.4.4 --save #google public DNS server
-# vzctl set 100 --hostname foobar --save
+# ##i##vzctl set 100 --hostname foobar --save
-</pre>
+</console>
 With venet configuration, some additional steps are required in case of PPPoE Internet connection. We will use iptables to get network working in all VE's.

@@ Line 136: / Line 136: @@
 To add a veth "eth0" interface to your VE, type the following:
-<pre>
+<console>
-ninja1 ~ # vzctl stop 100
+# ##i##vzctl stop 100
-ninja1 ~ # vzctl set 100 --netif_add eth0,,,,br0 --save
+# ##i##vzctl set 100 --netif_add eth0,,,,br0 --save
-ninja1 ~ # vzctl start 100
+# ##i##vzctl start 100
-</pre>
+</console>
 Once the VE is started, the network interface inside the VE will be called "eth0", and the network interface on the host system will be named "veth100.0". Because we specified "br0" after the 4 commas, vzctl will automatically add our new "veth100.0" interface to bridge br0 for us. We can see this by typing "brctl show" after we have started the VE by typing "vzctl start 100".
-<pre>
+<console>
-# brctl show
+# ##i##brctl show
 bridge name     bridge id               STP enabled     interfaces
 br0             8000.0026b92c72f5       no              eth0
                                                          veth100.0
-</pre>
+</console>
 ==== VE Configuration ====

@@ Line 117: / Line 117: @@
 Now, we need to create a necessary symlink in /etc/init.d and get our bridge added to the default runlevel:
-<pre>
+<console>
-# cd /etc/init.d
+# ##i##cd /etc/init.d
-# ln -s netif.tmpl netif.br0
+# ##i##ln -s netif.tmpl netif.br0
-# rc-update add netif.br0 default
+# ##i##rc-update add netif.br0 default
-</pre>
+</console>
 Now, let's enable our new network interfaces:
-<pre>
+<console>
-# /etc/init.d/netif.eth0 stop
+# ##i##/etc/init.d/netif.eth0 stop
-# rc
+# ##i##rc
-</pre>
+</console>
 The result of these changes is that you now have initscripts to create a "br0" interface (with static IP), with "eth0" as its slave (with no IP). Networking should still work as before, but now you are ready to provide bridged connectivity to your virtual containers since you can add their "veth" interfaces to "br0" and they will be bridged to your existing network.

@@ Line 106: / Line 106: @@
 slaves="netif.eth0"
 </pre>
 Now, time to create a new /etc/conf.d/netif.eth0, but this time we won't associate an IP address with it. Config file looks like this, a single line:

@@ Line 174: / Line 174: @@
 Add an iptables rule, save and start the firewall:
 <console># ##i##iptables -t nat -A POSTROUTING -o ppp0 (or your desired interface) -j MASQUERADE
-# ##i##iptables-save
+# ##i##/etc/init.d/iptables save
 # ##i##rc-update add iptables default
 # ##i##rc</console>

@@ Line 37: / Line 37: @@
 The Funtoo Linux stage directory also contains Funtoo Linux OpenVZ templates in the openvz/ directory. These can be used as follows:
-<pre>
+<console>
-# cd /vz/template/cache
+# ##i##cd /vz/template/cache
-# wget http://ftp.osuosl.org/pub/funtoo/funtoo-current/openvz/x86-64bit/funtoo-openvz-core2_64-funtoo-current-2011-12-31.tar.xz
+# ##i##wget http://ftp.osuosl.org/pub/funtoo/funtoo-current/openvz/x86-64bit/funtoo-openvz-core2_64-funtoo-current-2011-12-31.tar.xz
-ninja1 private # vzctl create 100 --ostemplate funtoo-openvz-core2_64-funtoo-current-2011-12-31
+# ##i##vzctl create 100 --ostemplate funtoo-openvz-core2_64-funtoo-current-2011-12-31
 Creating container private area (funto-openvz-core2-2010.11.06)
 Performing postcreate actions
 Container private area was created
-</pre>
+</console>
 If you are not using Funtoo Linux, you may need to convert the .xz template to a .gz template for this to work.

@@ Line 27: / Line 27: @@
 After booting into an OpenVZ-enabled kernel, OpenVZ can be enabled as follows:
-<pre>
+<console>
-# emerge vzctl
+# ##i##emerge vzctl
-# rc-update add vz default
+# ##i##rc-update add vz default
-# rc
+# ##i##rc
-</pre>
+</console>
 == Funtoo Linux OpenVZ Templates ==

@@ Line 162: / Line 162: @@
 # vzctl set 100 --hostname foobar --save
 </pre>
-With veneth configuration some additional steps required in case of PPPoE connection. We will use iptables to get network working in all VE's.
-<console># echo 1 > /proc/sys/net/ipv4/ip_forward</console>
+With venet configuration, some additional steps are required in case of PPPoE Internet connection. We will use iptables to get network working in all VE's.
 or, alternatively set it in /etc/sysctl.conf to have ip forward at boot
 <console># echo "net.ipv4.ip_forward = 1" >> /etc/sysctl.conf
-# sysctl -p</console>
+<console># ##i##echo "net.ipv4.ip_forward = 1" >> /etc/sysctl.conf
 Add an iptables rule, save and start the firewall:
-<console># iptables -t nat -A POSTROUTING -o ppp0 (or your desired interface) -j MASQUERADE
+<console># ##i##iptables -t nat -A POSTROUTING -o ppp0 (or your desired interface) -j MASQUERADE
-# iptables-save
+# ##i##iptables-save
-# rc-update add iptables default
+# ##i##rc-update add iptables default
-# rc</console>
+# ##i##rc</console>
 All VE's now have a network connection from HN.

@@ Line 52: / Line 52: @@
 If you do not need to have any resource limits in place for the VE, then on a Funtoo Linux host, they can be enabled as follows:
-<pre>
+<console>
-ninja1 ~ # vzctl set 100 --applyconfig unlimited --save
+ninja1 ~ # ##i##vzctl set 100 --applyconfig unlimited --save
-</pre>
+</console>
 == Starting the Container ==