netdev - Re: Bonding support for eth1394?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <471201D7.8090001@s5r6.in-berlin.de>
Date:	Sun, 14 Oct 2007 13:47:35 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Bill Fink <billfink@...dspring.com>
CC:	Roland Dreier <rdreier@...co.com>, netdev@...r.kernel.org,
	linux1394-devel@...ts.sourceforge.net
Subject: Re: Bonding support for eth1394?

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/
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html