[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <46C1AA82.1090403@s5r6.in-berlin.de>
Date: Tue, 14 Aug 2007 15:13:38 +0200
From: Stefan Richter <stefanr@...6.in-berlin.de>
To: Jan Engelhardt <jengelh@...putergmbh.de>
CC: lepton <ytht.net@...il.com>, lkm <linux-kernel@...r.kernel.org>,
bcollins@...ian.org, linux1394-user@...ts.sourceforge.net
Subject: Re: I have two 1394 port in my computer, why did I get only one eth1394
interface?
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/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists