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] Help me to set up network (routes)

To: AlannY <m@xxxxxxxxx>
Subject: Re: [Xen-users] Help me to set up network (routes)
From: Jeff Williams <jeffw@xxxxxxxxxxxxxx>
Date: Thu, 07 May 2009 14:41:32 +0800
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 06 May 2009 23:42:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A02961B.1080402@xxxxxxxxx>
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: <4A01EBC5.3050602@xxxxxxxxx> <4A023820.2000807@xxxxxxxxxxxxxx> <4A02961B.1080402@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.21 (X11/20090409)
On 07/05/09 16:04, AlannY wrote:
Jeff Williams wrote:
I haven't set up routed networking, but I would say the problem is that the gateway on the Windows DomU is 10.9.3.1, which it doesn't know how to get to. I would suggest to changing it to 10.0.2.254 which is on the same subnet as the DomU's network interface, the traffic should then come out via vif2.0 and be handled by Dom0.

I changed it. Nothing happens.

In DomU with gateway 10.0.2.254 (BTW, from where you get *.254 address?):
The 10.0.2.254 came from http://wiki.kartbuilding.net/index.php/Xen_Networking#Two-way_Routed_Network_2

%# ping 10.0.2.254

Pingin 10.0.2.254 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

And so on for every IP...

Still no luck
You won't be able to ping 10.0.2.254 - it does not exist, but I thought this should get traffic out to the dom0 as it is on the network assigned to vif2.0 from the Windows side. You can't ping 10.9.3.92 from the domU?

What does 'route print' show on the Windows domU?

Jeff

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users