On Wed, Aug 11, 2004 at 09:28:51 -0700, Stephen Hemminger wrote: > It must use ethernet link encapsulation: 6 byte dst, 6 byte src, 2 byte type. > But 1394 uses 8 byte dst, 2 byte type. Obviously this can't be bridged. Ah.. So, if I understand correctly, ethernet like behavior is in effect emulated with firewire "messages", instead of firewire completely encapsulating ethernet frames? I always reckoned that the arp protocol over firewire contains some sort of translation from the firewire addressing to an ethernet like addressing scheme, and that host addresses are provided for by address allocation faries. Come to think of it, now that I'm looking, the fw based interfaces don't have a MAC address [of the type i'm familiar with], instead the hardware address is 8 bytes on OSX, and 16 with the bottom half all zeros on linux. *sigh*. It could have been fun. Thanks for your knowlege and input! -- () Yuval Kogman <nothingmuch@xxxxxxxxxxxx> 0xEBD27418 perl hacker & /\ kung foo master: /me spreads pj3Ar using 0wnage: neeyah!!!!!!!!!!! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.osdl.org/pipermail/bridge/attachments/20040811/696de78d/attachment.bin
