WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Routing problem

To: "Steffen Heil" <lists@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Routing problem
From: "Janke Dávid" <janke.david@xxxxxxxxx>
Date: Wed, 13 Sep 2006 12:35:30 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 13 Sep 2006 03:36:13 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Gmz/iWJmuhs6can6sFemJFkQmcSlztXlJ2OeTBtzWtr3vKrFIkDYmwdPNUP8II3LKd0kw1L4MbvQox0Tv9aXmEQcydOvCLGPHs55WxmzjM+VzuvYXMhJWQoPAIu6KuajCtBrAC3Dv1w7//4MZ/hxCJ1dGMIhBc4+TIeQEj62anY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <005c01c6d71c$198dd720$0b4613ac@shs1>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <889f15280609130239v3aaa8f22u1fd80dcff6da9257@xxxxxxxxxxxxxx> <005c01c6d71c$198dd720$0b4613ac@shs1>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
OK. But what if I (will) have a similar situation like described in the article ( http://www.debian-administration.org/articles/360 )? I somehow will have to route packages from outside to dumUs.
In our case, intranet traffic is routed via 10.2.0.10. I guess that if we tell the router to route traffic to 10.12.<whatever> via 10.2.0.9 that should solve some issues (if dom0 is set up correctly).

But I still don't know why domUs can't ping their own ethernet interfaces, nor the other hosts connected to the same xenbridge.

Xenbridge is a virtual device behaving similar to a switch?

thanks,
David

On 9/13/06, Steffen Heil <lists@xxxxxxxxxxxxxxx> wrote:
Hi

> I'm trying to set up several test systems as domUs. We've got a 10.0.0.0/8
Intranet, the ethernet interface in dom0 is 10.2.0.9 and the test servers
would be 10.12.1.2/29 (testhost1), 10.12.1.3/29 (testhost2), 10.12.2.2/24
(testhost3), 10.12.2.3/24 (testhost4).
> I guess routing via dom0 would be appropriate.

This will force you to add a static route to every system in your intranet
to reach the testhosts, because they would try to reach them without using
the router (in fact they are in their local subnet).

Use bridging in dom0 instead and it will work.

Regards,
  Steffen



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>