mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: lepton <ytht.net@gmail.com>, lkm <linux-kernel@vger.kernel.org>,
	bcollins@debian.org, linux1394-user@lists.sourceforge.net
Subject: Re: I have two 1394 port in my computer, why did I get only one eth1394 interface?
Date: Tue, 14 Aug 2007 15:13:38 +0200	[thread overview]
Message-ID: <46C1AA82.1090403@s5r6.in-berlin.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0708141017571.30582@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Aug 13 2007 17:24, Stefan Richter wrote:
>>The PHY may have several ports, but all of these ports belong to the same
>>FireWire bus. The PHY not only connect the link layer controller with each
>>port, it also acts as hub/repeater between those ports.
> 
> So given one has two firewire ports with only one PHY, it is not possible
> to make a firewall with two interfaces out of it, which each routed only to the
> specific firewire port...

Well, depends on whether one FireWire node could expose multiple network
interfaces on the same FireWire bus.  I'm not quite sure if the IPv4
over IEEE 1394 spec, RFC 2734, allows this.  It is however possible to
expose one RFC 2734 interface and one RFC 3146 interface (IPv6 over IEEE
1394) on the same bus --- hence it might also be possible to implement
more than one IPv4 interface per node per bus.  On a quick glance,
unicast doesn't seem to be a problem, but broadcast and multicast might be.

Linux' eth1394 driver implements only one IPv4 interface per bus, and no
IPv6 interface.

Anyway, an IP router from FireWire to FireWire seems to be a rather
exotic application, especially as LAN to internet router or firewall.
-- 
Stefan Richter
-=====-=-=== =--- -===-
http://arcgraph.de/sr/

      reply	other threads:[~2007-08-14 13:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13 12:35 lepton
2007-08-13 15:24 ` Stefan Richter
2007-08-14  8:19   ` Jan Engelhardt
2007-08-14 13:13     ` Stefan Richter [this message]

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=46C1AA82.1090403@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=bcollins@debian.org \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-user@lists.sourceforge.net \
    --cc=ytht.net@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®