On 5/21/2011 7:48 PM, Benjamin Kiessling wrote: > Hi, > > Indeed this is not a virtualization specific problem. You want your host to > operate as a router for > the other two IP addresses and, depending on the configuration of OVH, > ARP-Proxy the whole stuff. > Assuming you want have PUB-IP1 on the host and want to assign PUB-IP2 to the > container (lets say > with veths). > Just assign PUB-IP1 to your host (ip addr a PUB-IP1 dev ethN), add the route > for PUB-IP2 to the > veth of the container on the host (ip r a PUB-IP2 dev vethN), add PUB-IP2 to > the interface in the > container (ip addr a PUB-IP2 dev vethContainer) and set a default route over > PUB-IP1 in the > container (ip r a PUB-IP1/32 dev vethContainer&& ip r a default via PUB-IP1 > dev vethContainer). > Enable Routing (/proc/sys/net/ipv4/ip_forward) and if OVH uses reverse path > filtering proxy-arp > (/proc/sys/net/ipv4/conf/$DEV/proxy_arp) on the host. > That should do it. You could use a bridge and still reach all containers (the > bridge would have the > address PUB-IP1 and would include all veths and the physical device) but > it'll complicate the setup > if NAT is required for certain containers. Just set the routes explicitly for > each container veth. > > Regards, > Benjamin Kiessling
I'm not the OP but just wanted to say this was good stuff and I appreciate a handy run-down like that. -- bkw ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
