From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Andrew D. Ball" <aball@us.ibm.com>
Subject: Re: Using eth1
Date: Thu, 03 Nov 2005 17:06:40 -0500
Message-ID: <1131055600.16408.19.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Sorry, I forgot to forward this to Xen-devel.

-------- Forwarded Message --------
From: Andrew D. Ball <aball@us.ibm.com>
To: Michael Lessard <michael.lessard@gmail.com>
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@us.ibm.com> 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@gmail.com>Michael Lessard
>         <michael.lessard@gmail.com>
>         
> 
> 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@lists.xensource.com
> http://lists.xensource.com/xen-devel