Xen users - Oct 2005 - routed network (not only one vif needed?)

Hi!

 Now I tried to set up xen for routed network. I didn''t understand why
so
much vifs will be create, as much as domains I have.
My routed network consists of the domain0 (with public IP), and domainU-s 
as the subnetwork (192.168.0.x)
So I modified the vif-route script in order to have only one vif for all
domainsU-s (with ip 192.168.0.254).  But in this case only the domainU
works, for that I created the vif. So I need more VIF in order to have
networking also in all my DomainU-s? all of these Vifs should have the
same IP address. (My subdomains are in one private network (192.168.0.1))
How is about the routing table (route)?

Thnx for the answers in advance

George



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

Hi Georg,

georg@etixpert.com schrieb:
>Hi!
>
> Now I tried to set up xen for routed network. I didn''t understand
why so
>much vifs will be create, as much as domains I have.
>My routed network consists of the domain0 (with public IP), and domainU-s 
>as the subnetwork (192.168.0.x)
>So I modified the vif-route script in order to have only one vif for all
>domainsU-s (with ip 192.168.0.254).  But in this case only the domainU
>works, for that I created the vif. So I need more VIF in order to have
>networking also in all my DomainU-s? all of these Vifs should have the
>same IP address. 
>
Why should that make sense? I do not see what you are after with this.

Routed networking implies that every domU is a subnet of its own, so it 
has to have an address space (not only a single address) of its own. 
Dom0 has to have a routing table that connects the dom0 NIC with the the 
virtual subnets that the domUs are.
>(My subdomains are in one private network (192.168.0.1))
>  
>
Why don''t you use bridging, then?

Dirk

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

Hi

  Thnx for the answer.

So do you think I need bridged network?
I have the dom0 (having public IP, and being also part of the private  
network) and ths DOMU-s as the subnetwork (192.168.0.x).
I don''t understand what will be happened with the network interfaces at
briding:
  - There will be an xen-br0 interface created with my  DOMU''s IP
address
  - When starting my DOM1 a mew VIF interface on DOM0 will be created, but  
there will be no interface created on DOM1.

What I would except: having one virtual interface on dom0, that all the  
domU could see as gateway. On  DOMu there should be an eth0 everywehere  
where I would set the appropriate IP adresses, gateways.. So with that
I''d
have a virtual router on DOM0. Maybe is this concept worng?

How schould I live with the interfaces created by xen bridge scripts in  
this case?
Thnx
  George





On Tue, 25 Oct 2005 21:00:56 +0200, Dirk H. Schulz  
<dirk.schulz@kinzesberg.de> wrote:
> Hi Georg,
>
> georg@etixpert.com schrieb:
>
>> Hi!
>>
>> Now I tried to set up xen for routed network. I didn''t
understand why so
>> much vifs will be create, as much as domains I have.
>> My routed network consists of the domain0 (with public IP), and  
>> domainU-s as the subnetwork (192.168.0.x)
>> So I modified the vif-route script in order to have only one vif for
all
>> domainsU-s (with ip 192.168.0.254).  But in this case only the domainU
>> works, for that I created the vif. So I need more VIF in order to have
>> networking also in all my DomainU-s? all of these Vifs should have the
>> same IP address.
> Why should that make sense? I do not see what you are after with this.
>
> Routed networking implies that every domU is a subnet of its own, so it  
> has to have an address space (not only a single address) of its own.  
> Dom0 has to have a routing table that connects the dom0 NIC with the the  
> virtual subnets that the domUs are.
>
>> (My subdomains are in one private network (192.168.0.1))
>>
> Why don''t you use bridging, then?
>
> Dirk
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users


-- 
Using Opera''s revolutionary e-mail client: http://www.opera.com/m2/

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

My curent setup is similar to what you trying to get. I have:

gw:/home/bdew# ip link
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
     link/ether 00:07:95:36:e6:ad brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
     link/ether 00:10:4b:2e:ac:17 brd ff:ff:ff:ff:ff:ff
4: br-exp: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
5: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP> mtu 1460 qdisc pfifo_fast
     link/ppp
6: vif1.0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
7: vif2.0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff


eth0 and eth1 are phisical cards connected to real networks.

ppp0 is an l2tp link running thru eth1.

vif1.0 and vif2.0 are created by xen scripts and connected to eth0 in 2
domains, they are assigned to br-exp and not used anywhere else.

br-exp is a (bridge) virtual interface connect to both domu''s.

Routing looks like this:

172.28.0.0/19 dev eth1  proto kernel  scope link  src 172.28.29.156
10.0.0.0/16 dev eth0  proto kernel  scope link  src 10.0.0.1
10.1.0.0/16 dev br-exp  proto kernel  scope link  src 10.1.0.1
default via 212.143.208.155 dev ppp0

The domU''s have adresses from 10.1.x.x subnet, and use 10.1.0.1
(br-exp)
as their default gateway.
The computers on eth0 network have their netmask set to 255.255.0.0, and
adresses from 10.0.x.x, 10.0.0.1 being the default gateway.

Infact this is a routed setup (no direct conection between domU''s and
real networks), but it uses xen in bridged mode to consolidate all
vif''s
to 1 interface.

Sueveges Gyoergy wrote:
 > Hi
 >
 >  Thnx for the answer.
 >
 > So do you think I need bridged network?
 > I have the dom0 (having public IP, and being also part of the private
 > network) and ths DOMU-s as the subnetwork (192.168.0.x).
 > I don''t understand what will be happened with the network
interfaces at
 > briding:
 >  - There will be an xen-br0 interface created with my  DOMU''s IP
address
 >  - When starting my DOM1 a mew VIF interface on DOM0 will be created,
 > but  there will be no interface created on DOM1.
 >
 > What I would except: having one virtual interface on dom0, that all the
 > domU could see as gateway. On  DOMu there should be an eth0 everywehere
 > where I would set the appropriate IP adresses, gateways.. So with that
 > I''d  have a virtual router on DOM0. Maybe is this concept worng?
 >
 > How schould I live with the interfaces created by xen bridge scripts in
 > this case?
 > Thnx
 >  George


-- 
Best regards, Black Dew.
=============================~ bdew@bdew.yi.org ~ ICQ:2666606 ~ 2:400/567 ~


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