[Bridge] eth1394 interface support?

Chris Shaw chriss at watertech.com
Wed Aug 11 13:48:17 PDT 2004

I shudder at the thought.... but... if you want bridging between 1394 and
Ethernet or wireless interfaces, you can do it in W2K3 or WinXP...

Again I know.... gross... but it works if you can stand windows...

You can also use ProxyARP which is a kludge but it can work, provided that
1394 under linux can do ARP in the usual 802 way...

P.S. I don't know if this has been brought up and please don't take it as a
demand for features, just a query, but has support for bridging disparate
interface types been considered or attempted?

True hardware bridges/switches can bridge between wired/wireless,
tokenring/Ethernet FDDI/Ethernet HIPPI/Ethernet, etc etc etc... It would be
cool if linux could do it for the firewalling capabilities and because
hardware like that can be very expensive...

Does anyone know how windows is doing it? Is it more of a ProxyARP than a


----- Original Message -----
From: "Stephen Hemminger" <shemminger at osdl.org>
To: "Yuval Kogman" <nothingmuch at woobling.org>
Cc: <bridge at lists.osdl.org>
Sent: Wednesday, August 11, 2004 9:28 AM
Subject: Re: [Bridge] eth1394 interface support?

> On Wed, 11 Aug 2004 18:16:31 +0300
> Yuval Kogman <nothingmuch at woobling.org> wrote:
> > I have a linux box which sits in the living room and plays
> > ti^H^Hfreevo.
> >
> > Among other things it also talks to the cable modem via interface
> > eth0, and does NAT transformations for eth1.
> >
> > Yesterday i was sitting in the living room with my laptop, thinking
> > about the fact that my wireless access point will only arrive next
> > week, and then remembered they both the laptop and the linux boxhave
> > firewire. The plot thickens.
> >
> > I enabled bridging support in the kernel, and i got to
> >
> > brctl addbr br0
> > brctl addif br0 eth1 # LAN interface
> > brctl addif br0 eth2 # firewire interface
> > br_add_interface: Invalid argument
> >
> > I reckon eth1394 is at fault, but I'd like to know what the bridge
> > code expects from it.
> It must use ethernet link encapsulation: 6 byte dst, 6 byte src, 2 byte
> But 1394 uses 8 byte dst, 2 byte type.  Obviously this can't be bridged.
> The bridge checks this by looking at the device type (dev->type) to
> check if it is ARPHD_ETHER.  For 1394 this is set to ARPHRD_IEEE1394.


Bridge mailing list
Bridge at lists.osdl.org

More information about the Bridge mailing list