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] Own network for domU, how to connect to dom0?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Own network for domU, how to connect to dom0?
From: Thomas Karsten <thomas@xxxxxxxxxxx>
Date: Tue, 25 Jul 2006 20:08:33 +0800
Delivery-date: Tue, 25 Jul 2006 05:16:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Reply-to: thomas@xxxxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8.2
Dear all,

I would like to setup my domU's to be in an own network. But when I do this,
then I am unable to reach the domU's from dom0 and vice versa. However, I am
able to ping each domU from each domU. Here is the setup:

domU (eth0):   192.168.2.xxx/24
dom0 (eth0):   192.168.1.58/24
dom0 (dummy0): 192.168.2.1/24

(It works well, if the domU's are also in 192.168.1.0/24.)

From this point on I am not sure what I can do to let the system send all the
packets going to 192.168.2.0 to the proper interfaces (vifx.0). I tried to
add the dummy device to the bridge xenbr0, but it did not help:

# brctl show
bridge name        bridge id                STP enabled        interfaces
xenbr0             8000.a22af5b58606        no                 vif0.0
                                                               peth0
                                                               dummy0
                                                               vif9.0
                                                               vif10.0

I also tried to add the dummy0 device to the routing table, but without
success:

# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.2.0     *               255.255.255.0   U     0      0        0 dummy0
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
default         192.168.1.1     0.0.0.0         UG    0      0        0 eth0

The configuration of each domU is as follows (the IP address is different for
each domU):

domU120# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         192.168.2.1     0.0.0.0         UG    0      0        0 eth0

domU120# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:16:3E:1C:AB:FF  
          inet addr:192.168.2.120  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::216:3eff:fe1c:abff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:30 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2323 (2.2 KiB)  TX bytes:510 (510.0 b)

How can I manage reaching dom0 from the domU's and vice versa? What am I
doing wrong in the configuration? Do I have to change the networking scripts
of Xen, and if so, which one and how?

Thank you very much,
Thomas

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

<Prev in Thread] Current Thread [Next in Thread>