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-devel

Re: [Xen-devel] network-bridge defunct

To: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] network-bridge defunct
From: Michael Lessard <michael.lessard@xxxxxxxxx>
Date: Wed, 26 Oct 2005 08:21:04 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 26 Oct 2005 12:18:14 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=CRcrS+RMX3P9aS2JBMRP3rXJ/7nHOo8gk03MjtSLRvn4Yj1GCfVNBC5MJ7JW/bTzIqpexseSuJq+DdDlsDp+fhfHwkacIVvVgro7fQAzh4sFfM+4tOMX6yi3ZPO+6E612FWlf9Vt6kQj7nLfd2bjjwM4AoYMz8jEWwx25B4Qw/k=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20051026102303.GM13783@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <c5530b840510180648m4f89939ewbcdf63b53fa81b30@xxxxxxxxxxxxxx> <20051018140539.GE12489@xxxxxxxxxxxxxxxxxxxxxx> <c5530b840510180717w369ba65fh4827aff4d853dd07@xxxxxxxxxxxxxx> <c5530b840510251249n323bc1ffu878a3882425092d@xxxxxxxxxxxxxx> <20051026102303.GM13783@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx


On 10/26/05, Ewan Mellor <ewan@xxxxxxxxxxxxx> wrote:
On Tue, Oct 25, 2005 at 03:49:09PM -0400, Michael Lessard wrote:

> My setup :
> 2 Network Carfs on Debian Sid for both of my domains (Dom0 and DomU)
> 1 network cards (eth0) for my DomU, the config for network cards on Dom0
> is :
>       iface eth0 inet manual
>             up /sbin/ifconfig eth0 up
>
> When i start DomU, i see appear vif1.0 , when i ping Dom0 from Dom0 i see
> only RX bytes growth
>
> On Dom0 , i have do echo "1" > /proc/sys/net/ipv4/ip_forward  and iptables
> -P FORWARD ACCEPT
>
> My xen config for DomU :
> kernel = "/boot/vmlinuz-2.6.12-xenU"
> memory = 200
> name = "Albert"
> nics=1
> vif = [ 'mac=aa:00:00:00:00:11, bridge=xenbr0' ]
> disk = [ 'phy:/dev/hdc3,hdc3,w', 'phy:/dev/hdc5,hdc5,w',
> 'phy:/dev/hdc1,hdc1,w' ]
> root = "/dev/hdc3 ro"
>
> I have try with and without mac address specified ...
> What's wrong with my setup ?

The network-bridge script is for multiplexing each domain's packets onto a
single network interface, through a bridge.  If you want to have one card
dedicated to dom0, and one dedicated to domU, then you don't want to use the
network-bridge configuration at all.

I think what you want to use is network-route / vif-route.  Edit your
xend-config.sxp to set

(network-script network-route)
(vif-script vif-route)

The intention is to have dom0 route traffic for your domU from eth1 to vif1.0,
and vice versa.  You're going to need to have the two cards on different
subnets for this to work using the standard scripts, though I guess that's
what you're doing already.

These scripts haven't had a lot of testing, and I'm not sure they are even the
right thing for you, so you may have to do some hacking to get the right
result.  Let us know how you get on.

Ewan.

What i modigy to xend-config.sxp
(network-script network-route)
(vif-script vif-route)
#(network-script    network-bridge)
#(vif-bridge        xenbr0)
#(vif-script        vif-bridge)

I restart Xend and restart my DomU ... i still couldn't ping dom0 from DomU

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>