From IEEE 1394 FireWire Wiki
Revision as of 13:27, 5 June 2011 by Stefanr (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search



eth1394 was originally an ethernet encapsulation protocol that allowed for the transfer of ethernet packets between two IEEE-1394 Linux hosts. It has since gained many aspects of the IPv4-over-1394 RFC 2734 specification, and is nearly completely compliant, albeit not rock-solid.

eth1394 is now interoperable with the RFC 2734 implementations in Windows XP and Mac OS X.

eth1394 has been removed in Linux 2.6.37. The same functionality is now provided by the firewire-net driver.


Maximum number of partially received fragmented datagrams (default = 25)
The maximum number of fragmented datagrams per node that eth1394 will keep in memory. Providing an upper bound allows us to limit the amount of memory that partial datagrams consume in the event that some partial datagrams are never completed.


  • ieee1394


When loaded, along with a host controller, you can configure the ethX (e.g., eth0, eth1, eth2) interfaces the same as you would for a normal ethernet interface. One ethernet interface is configured for each present IEEE 1394 controller.

The kernel names of firewire-net's interfaces are firewireX (firewire0, firewire1, ...). This avoids confusion with Ethernet interfaces.

Known Problems

  • Not completely RFC 2734 compliant, yet. Please read the TODO list in the eth1394.c source.
  • In Linux 2.6.21 and older: Unless eth1394 has been blacklisted, eth1394 was auto-loaded by hotplug as soon as a 1394 controller was activated. This was widely perceived as a bug.
Personal tools