[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Routing problem


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Janke Dávid" <janke.david@xxxxxxxxx>
  • Date: Wed, 13 Sep 2006 11:39:13 +0200
  • Delivery-date: Wed, 13 Sep 2006 02:39:56 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=DGioUxkL5mmRBTpagF0n9meC4ACoiVK9HM2RJZAchMSwYQxfiUpkM8abr0SsvuVoas+/PCUwS3gV+kswmYK0D6piYm05HhqaPO18oq+9/C2HJvk8t1ZCS4NGeRtrcjf7hIySCE9nWMJF0IVQFyjwcK4LUXascXUFEpJU3M08hVg=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi all!

I'm trying for a few days now and I don't get it so I need help.
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.

I've also read this: http://www.debian-administration.org/articles/360
According to this I have to create dummy ethernet drivers in dom0 and then create a bridge to connect interfaces on one LAN to it.

Here's the layout in ASCII:
           +-----------------------------------------------+
           | physical machine, dom0                        |
           |                                   +---------+ |
Intranet -----eth0                         +---|testhost1| |
           |                               |   +---------+ |
           |         dummy0 --- xenbridge0 +               |
           |                               |   +---------+ |
           |                               +---|testhost2| |
           |                                   +---------+ |
           |                                   +---------+ |
           |                               +---|testhost3| |
           |                               |   +---------+ |
           |         dummy1 --- xenbridge1 +               |
           |                               |   +---------+ |
           |                               +---|testhost4| |
           |                                   +---------+ |
           +-----------------------------------------------+

xend-config.xsp contains:
(network-script network-route)
(vif-script vif-route)

The config file of a host looks like:
-----------------------------------------
name = "testhost1"
kernel = "/boot/vmlinuz-2.6-xen"
ramdisk = "/boot/initrd.img-2.6.16-xen"
memory = 256
disk = ['phy:/dev/mapper/vg0-testhost1root,sda1,w','phy:/dev/mapper/vg0-testhost1swap,sda2,w']
root = "/dev/sda1"
# network config
vif = [ 'ip=10.12.1.2 ' ]
dhcp = "off"
hostname = "testhost1"
-----------------------------------------

Here are the problems.
#1:
When starting a teshost, xend creates vif<x>.0 and assigns 10.2.0.9 as IP!!!! Not 10.12.whatever

#2:
I know I have to assign vif<x>.0 to xenbridge manually (will do that later in vif-route). But for testing reasons I do this per hand. 'brctl show' says:
xenbridge0              8000.66c7fb672b7e       no              dummy0
                                                        vif36.0
                                                        vif37.0

'route' says:
10.12.1.0       *               255.255.255.0   U     0      0        0 vif37.0
10.12.1.0       *               255.255.255.0    U     0      0        0 vif36.0
localnet        *               255.0.0.0       U     0      0        0 eth0
default         gw.localnet 0.0.0.0         UG    0      0        0 eth0

dummy0 is: 10.12.1.1/24

default gw on teshosts is set 10.12.1.1

And I can NOT ping 10.12.1.3 from 10.12.1.2 or the other way. Nor can I ping 10.12.1.1 or 10.2.0.9. What i CAN is pinging 10.12.1.2 and 10.12.1.3 from dom0

I know, I doing something wrong but I can't figure it out.

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.