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

[Xen-users] subnet crossing multiple machines - a typical use I think, b

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] subnet crossing multiple machines - a typical use I think, but can't work
From: "Zhan Xiaoying" <xyzhan@xxxxxxxxxxxxx>
Date: Tue, 6 Dec 2005 10:47:30 -0000
Delivery-date: Tue, 06 Dec 2005 10:48:00 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcXyActx1PXCA9NPQlOpOUzQiy6s+wAEMg7AAfgVB9AAF6tl8A==
Thread-topic: subnet crossing multiple machines - a typical use I think, but can't work
Hi,
As titled, the scenario is:
1. Three machines A (130.x.x.15), B (130.x.x.16), C(130.x.x.17) within a
same subnet running Xen.
2. On each of them, there is one guest domain as configured as below:
left_node : Dom1 on A: eth0 10.15.0.2
central_node: Dom1 on B: eth0 10.15.0.1, eth1 10.16.0.1
right_node: Dom1 on C: eth0 10.16.0.2.

The target is: I hope to point left-node's gw to eth0 on central node,
and point right-node's gw to eth1 on central_node; therefore the
central_node acts as a router, through which left-node and right-node
can ping each other.(Furthermore, left, and right node will be replaced
by a cloud.)

I have tried configuring everything on one physical machine by creating
3 domains, and it works. But when across three physical machines, it
fails. (by adding an extra routing entry, "vertically " each internal IP
address can ping the underlying public IP address.)

I have tried both bridging and routing. I guess it should be a practical
scenario; but I might miss a big point. Do I need to configure NAT or
ipchains? Could anyone point me some direction? Please, any help is very
much appreciated!
Zhan

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] subnet crossing multiple machines - a typical use I think, but can't work, Zhan Xiaoying <=