Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 2 Feb 2004 15:22:10 +0900
From:      Kobayashi Katsushi <ikob@koganei.wide.ad.jp>
To:        Hidetoshi Shimokawa <simokawa@sat.t.u-tokyo.ac.jp>
Cc:        Dario Freni <saturnero@gufi.org>
Subject:   Re: Will rfc2734 be supported?
Message-ID:  <21FEFF58-5548-11D8-AD86-000A95C44FDC@koganei.wide.ad.jp>
In-Reply-To: <87d68yowr7.wl@tora.nunu.org>
References:  <1075559223.615.9.camel@localhost> <87d68yowr7.wl@tora.nunu.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

I have once tried to implement IP over firewire with earlier ID. spec.
in the previous version of driver. The packetization, ARP and broadcast
is not difficult to implement.

However, I cannot believe the MCAP mechanism will not work properly,
since limited No. of acceptable stream channels is supported on
current firewire chipset. I think the current IP over Firewire spec.=20
does
not include mechanism to suppress channel allocation in the case of
receiver cannot open more stream channels.


On 2004/02/02, at 14:50, Hidetoshi Shimokawa wrote:

> At Sat, 31 Jan 2004 15:27:03 +0100,
> Dario Freni wrote:
>>
>> [1  <text/plain (quoted-printable)>]
>> Hi guys,
>> I was wondering if the standard implementation of IPoFW is planning =
to
>> be implemented. I'm not expert on device writing, I was also looking=20=

>> for
>> some workarounds, like attach the fwe0:lower netgraph hook to a=20
>> virtual
>> interface, but reading the rfc I realized that the normal IP packet
>> needs an encapsulation before it's sent on the wire.
>
> I have no plan to implement rfc2734 by myself near future.
> IEEE1394 is somewhat complicated, compared with Ethernet.
> Because there are some types of packets, fwe and IPoFW uses very
> different packet type and formats, so you don't have an easy
> workaround using netgraph.
>
> If you are interested in implementing rfc2734, you need several steps.
>
> - Implement rfc2734 encapsulation as /sys/net/if_ethersubr.c for
> ethernt. rfc2734 uses very different packet format from ethernet.
>
> - Implement generic GASP receive routin in the firewire driver.
> You need this service for multicast/broadcast packet such as an arp
> packet.
>
> - Implement if_fw.c for the interface device.
>
> Though I'm not sure it actually worked, the firewire driver for
> FreeBSD-4.0 seems to have a support for IPoFW
> See ftp://ftp.uec.ac.jp/pub/firewire/ for the patch.
>
>> Bye,
>> Dario
>>
>> --=20
>> Dario Freni (saturnero@gufi.org) - SaturNero on IRCNet, Azzurra
>> Gruppo Utenti FreeBSD Italia (http://www.gufi.org)
>> GPG Public key at http://www.saturnero.net/saturnero.asc
>> [2 Questa parte del messaggio =E8 firmata <application/pgp-signature=20=

>> (7bit)>]
>>
>
> /\ Hidetoshi Shimokawa
> \/  simokawa@sat.t.u-tokyo.ac.jp
> PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html
> _______________________________________________
> freebsd-firewire@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-firewire
> To unsubscribe, send any mail to=20
> "freebsd-firewire-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?21FEFF58-5548-11D8-AD86-000A95C44FDC>