> When you start mixing class Cs, venet, veth and what have you, is when you > see forum postings.
I should note there is a RTFM on having different containers use different interfaces: http://wiki.openvz.org/Source_based_routing However, what is missing is a RTFM on having a single container use different interfaces to route to different IP ranges. For example, a host that is a router with separate interfaces to 192.168.1.0/24 and 192.168.42.0/24, as well as a gateway to the internet, and we want a container on this host to access all three networks (for example, a container running Squid as a web proxy). Another example which has been annoying me: Having an OpenVZ container inside of a VirtualBox guest. I would like to have my OpenVZ container be accessible from both my host and access both the internet at the same time, in a way that does not require a bridged interface. [1] VirtualBox uses one interface to access the internet (10.0.4.X) and another interface that the host can use to connect to the guest (192.168.56.X). The OpenVZ container can connect to one or the other, but not both at the same time. I just did a STFW to find a way to resolve this problem and only got other reports of people with similar issues, such as http://forum.openvz.org/index.php?t=msg&goto=9978&; So, here's my question: Is there a page out there which details exactly how to have an OpenVZ container use two or more different interfaces on the host machine? - Sam [1] The VirtualBox issue can be somewhat resolved by having the VirtualBox guest also have a bridged interface, and having the OpenVZ container use said bridged interface. This, alas, doesn't work when there isn't a DHCP server on the network to connect to, such as when I'm on a plane or somewhere else without WiFi. _______________________________________________ Users mailing list [email protected] https://openvz.org/mailman/listinfo/users
