Re: [Xen-users] Own network for domU, how to connect to dom0?

[Thomas Karsten <thomas@xxxxxxxxxxx>]

Hello,

I finally found a solution for my scenario. Actually it is very simple to
realise this configuration, just use the script 'network-bridge' to create a
new bridge and to set the virtual device as required. In my example I use the
dummy device that is in a different network (192.168.2.0/24) than my physical
device (192.168.1.0/24):

# /etc/xen/scripts/network-bridge start vifnum=1 netdev=dummy0
# ...
# brctl show
bridge name    bridge id            STP enabled    interfaces
xenbr0         8000.feffffffffff    no             vif0.0
                                                   peth0
                                                   vif1.0
xenbr1         8000.feffffffffff    no             vif0.1
                                                   pdummy0
                                                   vif2.0

Now each bridge is "responsible" for an own network. Since dom0 has
interfaces in both networks (eth0 in 192.168.1.0/24 and dummy0 in
192.168.2.0/24), I can access all domU's in both networks from dom0 and vice
versa. That's what I wanted. I just have to take care to use the correct
bridge and the correct network settings when creating a domU.

For those who are interested, the introduction in
http://wiki.xensource.com/xenwiki/XenNetworking helped me a lot to understand
Xen's handling of the network interfaces much better.

Thanks,
Thomas


On Tuesday 25 July 2006 20:08, Thomas Karsten wrote:
> 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
> 

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