extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2024-12-23 06:38:53 +01:00
Code Issues Packages Projects Releases Wiki Activity

More OpenVZ documentation updates

Browse Source
This commit is contained in:
Tom Eastep 2009-07-05 09:09:58 -07:00
parent 187e250915
commit fb571210c9
1 changed files with 48 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

74
docs/OpenVZ.xml
View File

@ -18,7 +18,7 @@
<pubdate><?dbtimestamp format="Y/m/d"?></pubdate> <pubdate><?dbtimestamp format="Y/m/d"?></pubdate>
<copyright> <copyright>
<year>2008</year> <year>2009</year>
<holder>Thomas M. Eastep</holder> <holder>Thomas M. Eastep</holder>
</copyright> </copyright>
@ -42,9 +42,10 @@
<trademark><ulink <trademark><ulink
url="http://www.parallels.com">Parallels</ulink></trademark> (formerly url="http://www.parallels.com">Parallels</ulink></trademark> (formerly
<trademark>SWSoft</trademark>). Virtual servers take the form of <trademark>SWSoft</trademark>). Virtual servers take the form of
<firstterm>containers</firstterm> which are created via <firstterm>containers</firstterm> (the OpenVZ documentation calls these
<firstterm>templates</firstterm>. Templates are available for a wide <firstterm>Virtual Environments</firstterm> or <firstterm>VEs</firstterm>)
variety of distributions and architectures.</para> which are created via <firstterm>templates</firstterm>. Templates are
available for a wide variety of distributions and architectures.</para>
<para>OpenVZ requires a patched kernel. Beginning with Lenny, <para>OpenVZ requires a patched kernel. Beginning with Lenny,
<trademark>Debian</trademark> supplies OpenVZ kernels through the standard <trademark>Debian</trademark> supplies OpenVZ kernels through the standard
@ -70,10 +71,10 @@
interface interface
(<filename>/proc/sys/net/ipv4/conf/<replaceable>interface</replaceable>/proxy_arp</filename>).</para> (<filename>/proc/sys/net/ipv4/conf/<replaceable>interface</replaceable>/proxy_arp</filename>).</para>
<para>OpenVZ creates virtual interfaces in the host with very odd <para>OpenVZ creates a point-to-point virtual interface in the host with
configurations.</para> a rather odd configuration.</para>
<para>Example:</para> <para>Example (Single VE with IP address 206.124.146.178):</para>
<programlisting>gateway:~# <command>ip addr ls dev venet0</command> <programlisting>gateway:~# <command>ip addr ls dev venet0</command>
10: venet0: &lt;BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP&gt; mtu 1500 qdisc noqueue state UNKNOWN 10: venet0: &lt;BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP&gt; mtu 1500 qdisc noqueue state UNKNOWN
@ -85,8 +86,8 @@ gateway:~# </programlisting>
<para>The interface has no IP configuration yet it has a route to <para>The interface has no IP configuration yet it has a route to
206.124.146.178!</para> 206.124.146.178!</para>
<para>From within the container with IP address 206.124.146.178, we have <para>From within the VE with IP address 206.124.146.178, we have the
the following:</para> following:</para>
<programlisting>server:~ # <command>ip addr ls</command> <programlisting>server:~ # <command>ip addr ls</command>
1: lo: &lt;LOOPBACK,UP,LOWER_UP&gt; mtu 16436 qdisc noqueue state UNKNOWN 1: lo: &lt;LOOPBACK,UP,LOWER_UP&gt; mtu 16436 qdisc noqueue state UNKNOWN
@ -169,36 +170,57 @@ vz venet0 - </programlisting>
<programlisting>#SOURCE DEST PROVIDER PRIORITY <programlisting>#SOURCE DEST PROVIDER PRIORITY
- 206.124.146.178 main 1000</programlisting> - 206.124.146.178 main 1000</programlisting>
</section> </section>
<section>
<title>RFC 1918 Addresses in a Container</title>
<para>You can assign an RFC 1918 address to a VE and use masquerade/SNAT
to provide Internet access to the container. This is just a normal
simple Shorewall configuration as shown in the <ulink
url="two-interface.htm">Two-interface Quick Start Guide</ulink>. In this
configuration the firewall's internal interface is <filename
class="devicefile">venet0</filename>.</para>
</section>
</section> </section>
<section> <section>
<title>Shorewall in an OpenVZ Container</title> <title>Shorewall in an OpenVZ Virtual Environment</title>
<para>If you have optained an OpenVZ container from a service provider, <para>If you have obtained an OpenVZ VE from a service provider, you may
you may find it difficult to configure any type of firewall within the find it difficult to configure any type of firewall within your VE. There
container. There are two container parameters that control iptables are two VE parameters that control iptables behavior within the
behavior within the container:</para> container:</para>
<variablelist> <variablelist>
<varlistentry> <varlistentry>
<term>--iptables <replaceable>name </replaceable></term> <term>--iptables <replaceable>name </replaceable></term>
<listitem> <listitem>
<para>Restrict access to iptables modules inside a container (by <para>Restrict access to iptables modules inside a container (The
default all iptables modules that are loaded in the host system are OpenVZ claims that by default all iptables modules that are loaded
accessible inside a container).</para> in the host system are accessible inside a container; I haven't
tried that).</para>
<para>You can use the following values for name: iptable_filter, <para>You can use the following values for
iptable_mangle, ipt_limit, ipt_multiport, ipt_tos, ipt_TOS, <replaceable>name</replaceable>: <option>iptable_filter</option>,
ipt_REJECT, ipt_TCPMSS, ipt_tcpmss, ipt_ttl, ipt_LOG, ipt_length, <option>iptable_mangle</option>, <option>ipt_limit</option>,
ip_conntrack, ip_conntrack_ftp, ip_conntrack_irc, ipt_conntrack, <option>ipt_multiport</option>, <option>ipt_tos</option>,
ipt_state, ipt_helper, iptable_nat, ip_nat_ftp, ip_nat_irc, <option>ipt_TOS</option>, <option>ipt_REJECT</option>,
ipt_REDIRECT, xt_mac, ipt_owner.</para> <option>ipt_TCPMSS</option>, <option>ipt_tcpmss</option>,
<option>ipt_ttl</option>, <option>ipt_LOG</option>,
<option>ipt_length</option>, <option>ip_conntrack</option>,
<option>ip_conntrack_ftp</option>,
<option>ip_conntrack_irc</option>, <option>ipt_conntrack</option>,
<option>ipt_state</option>, <option>ipt_helper</option>,
<option>iptable_nat</option>, <option>ip_nat_ftp</option>,
<option>ip_nat_irc</option>, <option>ipt_REDIRECT</option>,
<option>xt_mac</option>, <option>ipt_owner</option>.</para>
<para>If your provider is using this option, you may be in deep <para>If your provider is using this option, you may be in deep
trouble using Shorewall. Look at the output of <command>shorewall trouble trying to use Shorewall in your container. Look at the
show capabilities</command> and weep. Then try to get your provider output of <command>shorewall show capabilities</command> and weep.
to remove this restriction on your container.</para> Then try to get your provider to remove this restriction on your
container.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>