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/8Intranet, 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@lists.xensource.com
http://lists.xensource.com/xen-users
Additional info: Within testhosts I can NOT ping their own interfaces. So no reply from 10.12.1.2 within testhost1 On 9/13/06, Janke Dávid <janke.david@gmail.com> wrote:> > 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/8Intranet, 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.3from dom0 > > I know, I doing something wrong but I can''t figure it out. > > David >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi> I''m trying to set up several test systems as domUs. We''ve got a 10.0.0.0/8Intranet, 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@lists.xensource.com http://lists.xensource.com/xen-users
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@steffen-heil.de> 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@lists.xensource.com http://lists.xensource.com/xen-users
Hi> I somehow will have to route packages from outside to domUs.If your local LAN has 10.x.x.x and your domUs are part of that then a bridge suffices.> In our case, intranet traffic is routed via 10.2.0.10. I guess that if wetell 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). Where is it routed using 10.2.0.10? If it is an intranet I expect it to be a LAN, so no routing nessessary.> But I still don''t know why domUs can''t ping their own ethernet interfaces,nor the other hosts connected to the same xenbridge. Neither do I. Show us all your config files. What gives ifconfig inside the dom0/domUs? Show us all of it''s output.> Xenbridge is a virtual device behaving similar to a switch?Yes. It''s just a linux bridge and equal to a hardware switch. Xen''s default configuration uses bridging and should be flawless in your environment. That you vifs show the IP of dom0 is normal with routing. I think we can help more after seeing your ifconfig infos. Regards, Steffen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi! OK. I''m now using bridge to override the problem. But still I''m eager to know how the config in the article works (because I''m intending to provide such a service in future): http://www.debian-administration.org/articles/360 If anyone has experience, please share it with us. I''ll try to contact the author of the article. Best ragards, David PS.: thanks for the Xen developing team for such a great thing _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello, I have a server running Xen 3.0.2. It has 3 ethernet cards: eth0 is behind a DSL router in network 192.168.1, eth1 is connected to LAN 192.168.5, eth2 is used for something else, unrelated to my question. DomUs host virtual servers on 192.168.4, and I want to make dom0 a firewall for virtual servers and for internal network. I am trying to use routing setup of Xen but cannot make it work. The configuration for test domU is kernel = "/boot/vmlinuz-2.6.16-xen" memory = 256 name = "tst" disk = [ ''phy:sda5,hda1,w'', ''phy:sda6,hda2,w'' ] vif = [ ''ip=192.168.4.200,mac=00:16:3e:00:00:01'' ] netmask = "255.255.255.0" dhcp = "off" hostname = "tst" root = "/dev/hda1 ro" extra = "4" Whether I configure networking for domU in /etc/network/interfaces or not, domU is brought up with eth0 down (but routing to its IP gets added to dom0''s routing table). If I manually configure domU''s network by ifconfig eth0 inet 192.168.4.200 netmask 255.255.255.0 route add default dev eth0 I am able to ping domU (192.168.4.200) from dom0 (192,168.1.111) and vice versa, but I cannot ping anything outside the server from domU. Am I missing something obvious in routing setup? Is there a way to configure domU''s networking via configs? Standard way does not seem to work. I do not mind to put the above commands to rc.local, but is there better way? The system is running Ubuntu 6.06 LTS with kernel 2.6.16 installed from Dapper packages. Both /proc/sys/net/ipv4/conf/eth0/proxy_arp and /proc/sys/net/ipv4/ip_forward are set to 1. Thanks a lot, Alex _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users