I tried this way either, but there's two blocking problems with that - At least for me:<br>- Can't use this feature on 2.6.32 kernels <br>- Have to reboot to had a new interface to setup a new container - Yeah the say you want to add up a 11th container ;)<br>
<br><br>Olivier<br><br><div class="gmail_quote">On Tue, May 17, 2011 at 5:36 PM, Ulli Horlacher <span dir="ltr"><<a href="mailto:framstag@rus.uni-stuttgart.de">framstag@rus.uni-stuttgart.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Tue 2011-05-17 (17:18), David Touzeau wrote:<br>
<br>
> the host is a Virtual Machine stored on ESXi 4.0<br>
><br>
> The container can ping the host, the host can ping the container.<br>
> Issue is others computers network. cannot ping the container and the<br>
> container cannot ping the network.<br>
<br>
</div>I have had the same problems.<br>
<br>
My solution is: "lxc.network.type = phys"<br>
<br>
Every container has its own (pseudo) physical ethernet interface, which<br>
indeed is a ESX virtual interface, but Linux (LXC) sees a real ethernet<br>
interface, therefore: lxc.network.type = phys<br>
<br>
I have created 10 more ethernet interface via vSphere. This costs<br>
virtually nothing :-)<br>
<br>
root@zoo:/lxc# fpg network *cfg<br>
<br>
bunny.cfg:<br>
lxc.network.type = phys<br>
lxc.network.link = eth4<br>
<a href="http://lxc.network.name" target="_blank">lxc.network.name</a> = eth4<br>
lxc.network.flags = up<br>
lxc.network.mtu = 1500<br>
lxc.network.ipv4 = <a href="http://129.69.8.7/24" target="_blank">129.69.8.7/24</a><br>
<br>
flupp.cfg:<br>
lxc.network.type = phys<br>
lxc.network.link = eth1<br>
<a href="http://lxc.network.name" target="_blank">lxc.network.name</a> = eth1<br>
lxc.network.flags = up<br>
lxc.network.mtu = 1500<br>
lxc.network.ipv4 = <a href="http://129.69.1.219/24" target="_blank">129.69.1.219/24</a><br>
<br>
<br>
vmtest1.cfg:<br>
lxc.network.type = phys<br>
lxc.network.link = eth2<br>
<a href="http://lxc.network.name" target="_blank">lxc.network.name</a> = eth2<br>
lxc.network.flags = up<br>
lxc.network.mtu = 1500<br>
lxc.network.ipv4 = <a href="http://129.69.1.42/24" target="_blank">129.69.1.42/24</a><br>
<font color="#888888"><br>
<br>
<br>
--<br>
Ullrich Horlacher Server- und Arbeitsplatzsysteme<br>
Rechenzentrum E-Mail: <a href="mailto:horlacher@rus.uni-stuttgart.de">horlacher@rus.uni-stuttgart.de</a><br>
Universitaet Stuttgart Tel: <a href="tel:%2B%2B49-711-685-65868" value="+4971168565868">++49-711-685-65868</a><br>
Allmandring 30 Fax: <a href="tel:%2B%2B49-711-682357" value="+49711682357">++49-711-682357</a><br>
70550 Stuttgart (Germany) WWW: <a href="http://www.rus.uni-stuttgart.de/" target="_blank">http://www.rus.uni-stuttgart.de/</a><br>
</font><div><div></div><div class="h5"><br>
------------------------------------------------------------------------------<br>
Achieve unprecedented app performance and reliability<br>
What every C/C++ and Fortran developer should know.<br>
Learn how Intel has extended the reach of its next-generation tools<br>
to help boost performance applications - inlcuding clusters.<br>
<a href="http://p.sf.net/sfu/intel-dev2devmay" target="_blank">http://p.sf.net/sfu/intel-dev2devmay</a><br>
_______________________________________________<br>
Lxc-users mailing list<br>
<a href="mailto:Lxc-users@lists.sourceforge.net">Lxc-users@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/lxc-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/lxc-users</a><br>
</div></div></blockquote></div><br>