All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yuval Kogman <nothingmuch@woobling.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] eth1394 interface support?
Date: Wed, 11 Aug 2004 21:04:44 +0300	[thread overview]
Message-ID: <20040811180444.GA14424@woobling.org> (raw)
In-Reply-To: <20040811092851.43c57af7@dell_ss3.pdx.osdl.net>

[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]

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@woobling.org> 0xEBD27418  perl hacker &
 /\  kung foo master: /me spreads pj3Ar using 0wnage: neeyah!!!!!!!!!!!


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-08-11 18:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 15:16 [Bridge] eth1394 interface support? Yuval Kogman
2004-08-11 16:28 ` Stephen Hemminger
2004-08-11 18:04   ` Yuval Kogman [this message]
2004-08-11 20:48   ` Chris Shaw
2004-08-11 23:36     ` Yuval Kogman
2004-08-11 23:56       ` Chris Shaw

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040811180444.GA14424@woobling.org \
    --to=nothingmuch@woobling.org \
    --cc=bridge@lists.osdl.org \
    --cc=shemminger@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.