TCP/IP over IEEE 1394?

johnMG · 01-29-2005, 03:22 PM

On Windows machines, I regularly see IEEE 1394 devices listed under the Windows "Networks" control panel. As if a 1394 card was just like a network card...

Can a LAN use 1394 instead of ethernet?

If so, how would that work? Do they sell special IEEE 1394 routers or switches?

What would TCP/IP over IEEE 1394 have in common with TCP/IP over ethernet?

Is there a how-to or a FAQ on this somewhere that someone could point me to?

Thanks.

acid_kewpie · 01-29-2005, 04:16 PM

http://www.linux1394.org/eth1394.php

johnMG · 01-29-2005, 05:22 PM

Ahhh... thanks for the link AK.

So there's actually 2 ways to get IP over 1394:

1. IPv4-over-1394, RFC-2734
http://www.ietf.org/rfc/rfc2734.txt?number=2734

2. The eth1394 kernel module supplied by the linux1394 project, which encapsulates ethernet packets with some other frame format (?) to shoot them out the 1394 connector.

Then there's this comment on that linux1394 eth1394 page:

One will be able to use this in conjunction with the ip1394 driver in Windows XP, and in Apple's upcoming IP Over Firewire implementation.

Which is cryptic to me; does this ip1394 Windows driver differ from both (1) and (2) above?

tulcod · 06-04-2008, 11:20 AM

Quote:

Originally Posted by johnMG

Ahhh... thanks for the link AK.

So there's actually 2 ways to get IP over 1394:

1. IPv4-over-1394, RFC-2734
http://www.ietf.org/rfc/rfc2734.txt?number=2734

2. The eth1394 kernel module supplied by the linux1394 project, which encapsulates ethernet packets with some other frame format (?) to shoot them out the 1394 connector.

Then there's this comment on that linux1394 eth1394 page:

One will be able to use this in conjunction with the ip1394 driver in Windows XP, and in Apple's upcoming IP Over Firewire implementation.

Which is cryptic to me; does this ip1394 Windows driver differ from both (1) and (2) above?

for those still interested in the answer, this guy is confused. (1) is ONLY the specification for the protocol, not an implementation. (2) is a driver which implements the protocol described in (1)

windows and apple apparently implement (1) too, but probably with a different driver than (2)