From: <ope...@li...> - 2010-09-22 11:21:10
|
The problem is that the server has a main IP address 88.1.1.1 for example, and the IP address pool for the guests are not in the same subnet. They are routed by my provider through 88.1.1.1. I could imagine they have something like this in their router: route add -host 55.1.2.3 gw 88.1.1.1 (with 55.1.2.3 being the IP to assign to the guest). The provider is OVH (if that helps anyone seeing this)... and those IP addresses can be routed to any of the dedicated servers you own, by using their web interface... So if a server fails, you just route the IP to the other server, and everything keeps working. I currently have 3 Openvz Guests... and the setup looks like this: On the HN: # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 188.x.y.226 0.0.0.0 255.255.255.255 UH 0 0 0 venet0 188.x.y.227 0.0.0.0 255.255.255.255 UH 0 0 0 venet0 188.x.y.225 0.0.0.0 255.255.255.255 UH 0 0 0 venet0 What I want is to replicate (as much as possible) this setup for the Windows Guests Julian J. M. On Wed, Sep 22, 2010 at 12:10, <ope...@li...> wrote: > By default on OpenNode we use bridged network to KVM VM - seems that if > you are doing NAT with iptables on HN then you use routed network with KVM? > > ---------------------------------------------- > Andres Toomsalu, an...@ac... > > > > > ope...@li... wrote: >> Thanks for the reply. >> >> Ok... I have done this in the past: >> >> 1) Setup a network (192.168.99.1 on the HN, 192.168.99.2 in the >> Guest). They can ping each other. >> 2) Setup iptables to do forward packets on the HN to the Guest >> 3) Setup iptables to do NAT on packets going out with a src address of >> 192.168.99.2 >> >> That works, but I don't like that setup very much, because the windows >> Guest doesn't have notion of its public IP address. >> >> Note that I'm talking about Windows Guests... >> >> Julian J. M. >> >> On Wed, Sep 22, 2010 at 11:58, <ope...@li...> wrote: >> >>> I think you must add proper routes inside KVM VM and/or also to vmbr0 >>> for these subnets. >>> >>> venet interfaces work magically because they are point-to-point and >>> required routes get added automatically - as seen with: route -n >>> >>> To add additional routes to vmbr0 interface do something like that >>> (192.168.55.0 being desired subnet and 192.168.55.1 as gateway to this >>> subnet) : >>> >>> route add -net 192.168.55.0 netmask 255.255.255.0 gw 192.168.55.1 vmbr0 (vmbr0 on HN or eth0 inside VM) >>> >>> Let me know if that helps. >>> >>> ---------------------------------------------- >>> Andres Toomsalu, an...@ac... >>> >>> >>> >>> >>> ope...@li... wrote: >>> >>>> Hello, >>>> >>>> I have a server with 1 public IP address, and 8 more IP addresses >>>> routed through it. These are individual IPs, they aren't in the same >>>> block. >>>> >>>> OpenVZ guests work very well in this setup... the HN just forwards >>>> packets directed to their IP to the corresponding VNET interface, and >>>> everything works very well. >>>> >>>> How can I replicate this setup with Windows Guests under KVM? Can >>>> anyone point me to a tutorial or howto on how to setup both the HN and >>>> the Windows Guest networking? >>>> >>>> Thanks in advance, >>>> Julián J. M. >>>> >>>> >>>> >>> ------------------------------------------------------------------------------ >>> Start uncovering the many advantages of virtual appliances >>> and start using them to simplify application deployment and >>> accelerate your shift to cloud computing. >>> http://p.sf.net/sfu/novell-sfdev2dev >>> _______________________________________________ >>> OpenNode-users mailing list >>> Ope...@li... >>> https://lists.sourceforge.net/lists/listinfo/opennode-users >>> >>> >> >> >> >> > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > -- http://www.julianmenendez.es |