This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] Xen : How to configure a Proxy as DomU ?

To: Grant McWilliams <grantmasterflash@xxxxxxxxx>
Subject: Re: [Xen-users] Xen : How to configure a Proxy as DomU ?
From: Mirco Santori <mirco.santori@xxxxxxxxx>
Date: Tue, 22 Sep 2009 17:50:06 +0200
Cc: Simon Hobson <linux@xxxxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 22 Sep 2009 08:50:53 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=p0wq3XLKz1SjxwtDzFZGl91bLbCGnvzctDpqWlrL1xs=; b=I2fDwDiXv1iX4C92GDnIlSHKhfAv3VeenL99qwe33iu6YNphlFgomXANtm88Bv3D0F 2jPZFH3MkuEvM2zClAYEqskhovC5GZY3oFhRCwuZM9UtFFR1XUglksVZwdwSRkKYo24o uiLh41gQLzTcfKCtC3K4HR3M1lzANCOKpMeN0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QqOsYGGXE5QV2ukmYjfJfkNxX/sQJSAPGINnnT+N+561NunJksOnOn4eUHQEguBE3K ram7aa5M713XhyPPGVpYVu/OkGLu47mU81Uv9MhxiFnptYSW7VYQ4qyFbkzB2Vqz1u4E XLbMUBBusydKlM0MdgQUf264oTzPcIVW2soUU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <ed123fa30909220703m1b008224m903cb7d2cec597d2@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <bf0c4f970909220240s22dd1c98r1b28069a9a011f2a@xxxxxxxxxxxxxx> <p06240807c6de5502f96a@xxxxxxxxxxxxxxxxxxxxxx> <bf0c4f970909220422o28ff80c4qcbfdd2715c5fccad@xxxxxxxxxxxxxx> <p06240808c6de6d9abd40@xxxxxxxxxxxxxxxxxxxxxx> <bf0c4f970909220600w2976619y13085fc25373a175@xxxxxxxxxxxxxx> <ed123fa30909220703m1b008224m903cb7d2cec597d2@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Simon .. here is the output :

svrlnx05:/# brctl show
bridge name    bridge id        STP enabled    interfaces
xenbr0        8000.00238b174296    no        eth0
xenbr1        8000.00238b174297    no        eth1

  1. All VMs can talk to each other -> yes
  2. All VMs are connected to the xenbr0 network -> yes
  3. The Dom0 can access the real network -> yes
actually .. i cannot realize what happening ..

2009/9/22 Grant McWilliams <grantmasterflash@xxxxxxxxx>
On Tue, Sep 22, 2009 at 6:00 AM, Mirco Santori <mirco.santori@xxxxxxxxx> wrote:
i think to have made a wrong  question.

- I installed Dom0 with debian lenny and xen
- i configured network with the bridge method (xenbr0 - xenbr1)
- installed and configured apache with proxy module
- installed and configured two web servers with apache / php5 / mysql

all servers are connected to the internet and intranet (which allow them to work togheter in a private netork)

i dont need any help by you about proxy - web server and other stuff .. but actually i need help to configure the Dom0 in order to allow the proxy to work fine. I guess .. i missing some configuration on Dom0 with the command "route" .. seems that there is a problem with the proxy which is not able to forward the request by using xenbr0 (which is the eth0 on Dom0)

thank you so much Simon

I'm going to assume a few things here
  1. All VMs can talk to each other
  2. All VMs are connected to the xenbr0 network
  3. The Dom0 can access the real network
If these are true then I need something from you. Can you give me the output of

brctl show

Depending on your version of Xen the network is set up different ways. What we want is for the physical ethernet device to be attached to the xenbr0 if you want the VMs to communicate with the real network as if they were real Servers. You may find that you have two bridges - eth0 (which peth0 is a member) and xenbr0 (which vif1.0 and vif2.0 are members). If this is the case then traffic from the eth0 bridge will not traverse thin air and end up on xenbr0. You might need to add peth0 to xenbr0.

Grant McWilliams

Xen-users mailing list