From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Richter Subject: Re: Bonding support for eth1394? Date: Sun, 14 Oct 2007 13:47:35 +0200 Message-ID: <471201D7.8090001@s5r6.in-berlin.de> References: <47106EDE.1090601@s5r6.in-berlin.de> <4711087E.1050005@s5r6.in-berlin.de> <20071014021850.9bd7c9ad.billfink@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, Roland Dreier , linux1394-devel@lists.sourceforge.net To: Bill Fink Return-path: In-Reply-To: <20071014021850.9bd7c9ad.billfink@mindspring.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux1394-devel-bounces@lists.sourceforge.net Errors-To: linux1394-devel-bounces@lists.sourceforge.net List-Id: netdev.vger.kernel.org Bill Fink wrote: > I believe the user wanted to bond an eth1394 interface with a normal > Ethernet interface, and I don't think that will work even with the > IPoIB bonding changes, since bonding of different fundamental types > of network interfaces still won't be supported, and I'm pretty sure > eth1394 is not considered a standard Ethernet interface (different > MAC address format for one thing). True, the MAC addresses, frame headers (OSI layer 2?) and so on are different. Of course the case which the original poster had in mind, bonding FireWire with Ethernet, would be at least as interesting as bonding several FireWire interfaces, since most FireWire equipped machines come with only one FireWire link and one or two Ethernet links. -- Stefan Richter -=====-=-=== =-=- -===- http://arcgraph.de/sr/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/