OpenVZ Forum


Home » General » Support » *SOLVED* VEs with different subnets
Re: VEs with different subnets [message #14551 is a reply to message #14548] Mon, 02 July 2007 08:31 Go to previous messageGo to previous message
ugo123 is currently offline  ugo123
Messages: 22
Registered: June 2007
Junior Member
dev wrote on Mon, 02 July 2007 03:29

have you read the following article aboute multiple devices/GW and routed venet:
http://wiki.openvz.org/Source_based_routing
?

The typical configuration of secured OVZ looks the following way:


    HN                                        VEs
-----------------------------------        ---------

   eth0 (assigned local IP address)

   eth1 (assigned global IP address)      VEs are routed
   and set as default default GW          through eth1, since
                                          it's default GW.


the only difference is that eth1 still has global IP assigned to HN. But this is a plus on the other hand, since HN often needs an access to internet for example for upgrades.

In this case you simple need to put "eth1" to /etc/vz/conf variable:
17 # The name of the device whose ip address will be used as source ip for VE.
18 # By default automatically assigned.
19 #VE_ROUTE_SRC_DEV="eth1"




Hello,

Thanks for you answer.

Yes, I did read the wiki "Source based routing", but it implies to have a new device set up for each new route that I want to give access to, to my VEs, right ?
So it means to assign a global IP to each HN ?

As I said, I would like to avoid "wasting" global IPs on the HNs, because I only have 64 IP and about 20 HNs... so it would mean only 44 IPs left for the VEs, which is not a lot in my case.
That's why I've built the explained configuration with Xen... well and of course the HN (dom0) have Internet access from their private subnet, because 10.1.1.1 acts as a NAT Gateway to them, so I can do upgrades, etc... with the HNs.

Ugo
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: *RESOLVED* Solaris 10 Template
Next Topic: *BUG REPORTED* Migration problem with 2.6.18-028stab035
Goto Forum:
  


Current Time: Mon Oct 14 09:25:21 GMT 2024

Total time taken to generate the page: 0.05777 seconds