From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Karl Svec <karlsvec@gmail.com>
Cc: netdev@vger.kernel.org, linux1394-devel@lists.sourceforge.net
Subject: Re: Bonding support for eth1394?
Date: Sat, 13 Oct 2007 09:08:14 +0200 [thread overview]
Message-ID: <47106EDE.1090601@s5r6.in-berlin.de> (raw)
In-Reply-To: <FFB081ED-646B-489D-8836-FBA619A57E3E@gmail.com>
(Adding Cc: netdev)
Karl Svec wrote to linux1394-devel:
> I'm trying to create a bonded network interface for an Xdmx setup out
> of a regular ethernet device (sungem) and a firewire ethernet
> (eth1394) device. However, ifenslave fails on the firewire device,
> and gives me the following output:
>
> Master 'bond0' : Error : SIOCBONDENSLAVE failed : Operation not
> supported
>
> I'm assuming that this error message means that bonding support is
> not implemented in the eth1394 driver. If this is the case, I'd like
> to request that bonding support be added to the eth1394 driver. Is
> this a reasonable request (i.e. is this something that was left out
> of the driver because it is difficult to do, or was it left out
> because nobody anticipated anyone using this feature)?
>
> I'm happy to do any testing.
>
> Thanks for your time,
What criteria has a networking driver to fulfill to be interoperable
with the bonding driver? From a brief look at the top of the files in
linux/drivers/net/bonding/, it appears that it is meant for Ethernet
drivers.
Unlike eth1394's name suggests, it is not Ethernet over FireWire but
IPv4 over FireWire, in a partial implementation of RFC 2734.
http://www.faqs.org/rfcs/rfc2734.html
What is missing to fully support RFC 2734 is multicast capability.
http://lxr.linux.no/source/drivers/ieee1394/eth1394.c#L25
The bonding sources have a few occurrences of EOPNOTSUPP. Unless I
missed something, they are all related to setting the hardware address
of the interface. AFAICS this is impossible with IP over FireWire. If
it is crucial to bonding to be able to change the slaves' hardware
addresses, then you are out of luck.
--
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/
next parent reply other threads:[~2007-10-13 7:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FFB081ED-646B-489D-8836-FBA619A57E3E@gmail.com>
2007-10-13 7:08 ` Stefan Richter [this message]
2007-10-13 15:34 ` Bonding support for eth1394? Roland Dreier
2007-10-13 18:03 ` Stefan Richter
2007-10-14 6:18 ` Bill Fink
2007-10-14 11:47 ` Stefan Richter
2007-10-15 17:02 ` Rick Jones
2008-02-19 21:27 ` Stefan Richter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47106EDE.1090601@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=karlsvec@gmail.com \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).