2,253
edits
Changes
m
Robot: Automated text replacement (-VEs +containers)
Usually you supply public IP addresses to your VEscontainers. Sometimes you don't want to do it (lack of IPs, etc.). This article describes how to use private IP addresses for VEscontainers.
== Prerequisites ==
</pre>
where <tt>src_net</tt> is a range of IP addresses of VEs containers to be translated by SNAT, and <tt>ip_address</tt> is the external IP address of your [[Hardware Node]]. Multiple rules are allowed, for example, in case you wish to specify several ranges of IP addresses. If you are using a number of physical network interfaces on the [[Hardware Node|Node]], you may need to specify a different interface for outgoing connections, e.g. <tt>-o eth2</tt>.
To make all IP addresses to be translated by SNAT (not only the ones of [[VE]]s with private addresses), you should type the following string:
{{Note|If the above is not working then check if one of the following solutions does the trick.}}
1. If you are using stable (currently 2.6.8-based) kernel, then to enable SNAT for the VEs containers on your local network you need to explicitly enable connection tracking in [[VE0]]. Make sure that the following string is present in the <tt>/etc/modprobe.conf</tt> file:
<pre>
options ip_conntrack ip_conntrack_enable_ve0=1
