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] Using eth1

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Using eth1
From: "Andrew D. Ball" <aball@xxxxxxxxxx>
Date: Thu, 03 Nov 2005 17:06:40 -0500
Delivery-date: Thu, 03 Nov 2005 22:06:56 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Sorry, I forgot to forward this to Xen-devel.

-------- Forwarded Message --------
From: Andrew D. Ball <aball@xxxxxxxxxx>
To: Michael Lessard <michael.lessard@xxxxxxxxx>
Subject: Re: [Xen-devel] Using eth1
Date: Thu, 03 Nov 2005 17:02:15 -0500
On Thu, 2005-11-03 at 15:49 -0500, Michael Lessard wrote:
> 
> 
> On 11/3/05, Li Ge <lge@xxxxxxxxxx> wrote:
>         I've used the way the Ewan provided a couple of day to get
>         eth1 working on my dom0. It works fine for me.
>         
>         <snip>
>         If you need to use a different NIC than eth0, say eth1, like
>         the "IBM blades":
>         
>         dom0: fake eth0 -> vif0.0 -+
>                                   |
>                                 bridge -> real eth1 -> the network
>                                   |
>         domU: fake eth0 -> vifN.0 -+
>         
>         then you want add the following two lines in
>         your /etc/xen/xend-config.sxp file
>         
>         (network-script 'network-bridge netdev=eth1')
>         (vif-script     vif-bridge)
>         
>         <snip>
>         
>         
>         Regards,
>         Li
>         
>         Inactive hide details for Michael Lessard
>         <michael.lessard@xxxxxxxxx>Michael Lessard
>         <michael.lessard@xxxxxxxxx>
>         
> 
> No still doesn't work ...  i still ping eth0 on Dom0 but not eth1 :( 
> 
> 

What do you mean by 'i still ping eth0 on dom0 but no eth1'?  Where are
you pinging from?

Using the edit to /etc/xen/xend-config.sxp above,
I can do 'ping -I eth0 192.168.46.101' and 'ping -I eth1 192.168.46.101'
successfully when eth0 has IP address 192.168.46.143 and eth1 has IP
address 192.168.46.16.

>From 192.168.46.101, I can ping 192.168.46.143 and 192.168.46.16.

Is this the type of test you're doing?

I have also used eth1 explicitly for the bridge by doing 'export
netdev=eth1' before 'xend start' in /etc/rc.d/rc.local, but I like
editing /etc/xen/xend-config.sxp better, since I can have xend run from
a regular init script.

Andrew

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


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

<Prev in Thread] Current Thread [Next in Thread>