Hi Guy.
> -----Original Message-----
> From: owner-ethereal-users@xxxxxxxx
> [mailto:owner-ethereal-users@xxxxxxxx]On Behalf Of Guy Harris
> Sent: Thursday, July 13, 2000 10:21
> To: tgegenwart
> Cc: ethereal-users@xxxxxxxx
> Subject: Re: [ethereal-users] Support for Token-Ring
>
>
> ...
> The DLT_ value that appears to be used for Token Ring is DLT_IEEE802; it
> may be reasonable to have Win32 libpcap ports use that for Token Ring
> captures - even if there aren't any Token Ring machines at the
> Politecnico di Torino, it might still be worth sticking the code in, so
> that users who *do* have Token Ring can test it (the page at
>
> http://netgroup-serv.polito.it/winpcap/misc/comp.htm
>
> says that FDDI support is also untested as they don't have the
> hardware).
>
> Fulvio?
It shouldn't be too difficult. Anyway, we need that libpcap supports Token
Ring . As far as I know, current libpcap doesn't.
> (Note that the packet filter compiler in libpcap won't generate code to
> correctly handle source-routed packets; making it do so would, I
> suspect, involve a fair bit of work to handle variable-length link-layer
> headers - the BPF machine language might support it, but it really
> prefers fixed-length headers.
>
> It looks as if it should generate correct code for non-source-routed
> packets, however.
>
> It also can't handle tests of link-layer addresses on Token Ring, but
> mergng in changes from patches out there for Token Ring support should
> allow it to do that - at least for non-source-routed packets.
>
> Windump won't be able to dissect them, as it's based on a version of
> tcpdump that can't handle Token Ring; I have a Token Ring dissector
> constructed by merging the FreeBSD and NetBSD tcpdump ones, which I'll
> check into the tcpdump.org code base if the tcpdump-workers list
> approves.
I approve.
>
> Ethereal/Tethereal can dissect Token Ring packets.)
:-))
Thanks,
fulvio