Re: [Xen-users] Topology question

[Manuel Knitza <manuel.knitza@xxxxxxxxxxxxxxx>]

Am 11.09.2013 um 14:43 schrieb Adam Goryachev 
<mailinglists@xxxxxxxxxxxxxxxxxxxxxx>:

> On 11/09/13 22:16, Manuel Knitza wrote:
>> Hi,
>> 
>> I tried to find what I am looking for for a while, but did not succeed so 
>> far.
>> 
>> So maybe one could point me into the right direction, or give me a nice 
>> hint, or
>> even a solution...
>> 
>> I've got a root server, which is my Xen Host (Debian Wheezy)
>> and managed to install Xen 4.2, by modifying the apt-sources.
>> 
>> I've got 5 public IPs available (say x.x.x.A to x.x.x.A) so far.
>> 
>> I now have a Domain, let's say mydoma.in pointing to x.x.x.D (this is going 
>> to be
>> my coordinating guest)
>> 
>> with two PVs - my name servers:
>> 
>>      - ns1.mydoma.in pointing to  x.x.x.B and
>>      - ns2.mydoma.in pointing to  x.x.x.C and
>> 
>> whereas the domain itself:
>> 
>> So far the network setup is as follows:
>> 
>> on host:
>> xenbr0 (ip x.x.x.A) via eth0 with all guests attached to it. (x.x.x.{B,C,D}).
>> All guests have internet access, are pingable etc.
>> 
>> Next thing is that I want to setup an own guest for every subdomain, e.g.
>> 
>>      - oc.mydoma.in
>>      - mail.mydoma.in
>>      - www.mydoma.in
>>      - vpn.mydoma.in
>>      - etc.
>> 
>> I want all the the subdomain DomUs as well as the domain DomU itself
>> to be able to see each other, but only want to assign one single public IP
>> to the "mydoma.in"-DomU.
>> Depending on the Port my domain main DomU should route the requests
>> to the corresponding sub domain domU.
>> 
>> I also only have one physical NIC (eth0) on my server and only can add
>> vif's (eth0:0, eth0:1...).
>> 
>> A lot of examples I found is for XEN 3.0. I could not yet get everything up
>> and running as desired.
>> 
> 
> Maybe I'm missing something, but I'd start with something like this:
> 1) I assume you currently add eth0 to a bridge called xenbr0, and each
> domU's network interface is also bridged to xenbr0
exactly:

# brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.6805ca0a286f       no              eth0
                                                        ns1
                                                        ns2

> 2) Create a new bridge called xenbr1
# brctl addbr xenbr1
# brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.6805ca0a286f       no              eth0
                                                        ns1
                                                        ns2
xenbr1          8000.000000000000       no              

> 3) Add a second network interface (on xenbr1) to the domU that has the
> IP you want to split up depending on port (probably x.x.x.D) and
> configure this interface with an internal IP 10.34.72.1

brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.6805ca0a286f       no              eth0
                                                        mydoma.in
                                                        ns1
                                                        ns2
xenbr1          8000.feffffffffff       no              mydoma.in_prv
                                                        oc

Now got mydoma.in with public ip x.x.x.D (via. xenbr0) and private ip 
192.168.1.1 via xenbr1.

> 4) Setup a domU for oc.mydoma.in, with a single network interface on
> xenbr1, and configure with an IP of 10.34.72.2

For oc.mydoma.in i set up private IP 192.168.1.4. But with both VMs up and 
running from neither one i'm able to ping the other one (192.168.1.1 <-> 
192.168.1.4).

I think I know how to forward to the subdomain-DomUs, but I don't get why my 
VMs can't see each other via private network.

> 5) Now refer to standard linux networking on how to port forward http
> from x.x.x.D to 10.34.72.2 (hint, use iptables command).
> 
> 6) Repeat for each other IP/port/service/domU.
> 
> 
> That is how I would do it in xen 4.1.x anyway. If you need help with any
> of the above, please advise more details on what you tried, and what
> happened, or which part you do not understand.
> 
> Regards,
> Adam
> 
> -- 
> Adam Goryachev
> Website Managers
> www.websitemanagers.com.au

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users