On Tue 2011-05-17 (17:18), David Touzeau wrote: > the host is a Virtual Machine stored on ESXi 4.0 > > The container can ping the host, the host can ping the container. > Issue is others computers network. cannot ping the container and the > container cannot ping the network.
I have had the same problems. My solution is: "lxc.network.type = phys" Every container has its own (pseudo) physical ethernet interface, which indeed is a ESX virtual interface, but Linux (LXC) sees a real ethernet interface, therefore: lxc.network.type = phys I have created 10 more ethernet interface via vSphere. This costs virtually nothing :-) root@zoo:/lxc# fpg network *cfg bunny.cfg: lxc.network.type = phys lxc.network.link = eth4 lxc.network.name = eth4 lxc.network.flags = up lxc.network.mtu = 1500 lxc.network.ipv4 = 129.69.8.7/24 flupp.cfg: lxc.network.type = phys lxc.network.link = eth1 lxc.network.name = eth1 lxc.network.flags = up lxc.network.mtu = 1500 lxc.network.ipv4 = 129.69.1.219/24 vmtest1.cfg: lxc.network.type = phys lxc.network.link = eth2 lxc.network.name = eth2 lxc.network.flags = up lxc.network.mtu = 1500 lxc.network.ipv4 = 129.69.1.42/24 -- Ullrich Horlacher Server- und Arbeitsplatzsysteme Rechenzentrum E-Mail: [email protected] Universitaet Stuttgart Tel: ++49-711-685-65868 Allmandring 30 Fax: ++49-711-682357 70550 Stuttgart (Germany) WWW: http://www.rus.uni-stuttgart.de/ ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Lxc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxc-users
