Ethereal-dev: Re: [Ethereal-dev] dissector for FrameRelay

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Guy Harris <gharris@xxxxxxxxxxxx>
Date: Sun, 7 Jan 2001 14:26:26 -0800
On Sun, Jan 07, 2001 at 09:07:56PM +0200, Paul Ionescu wrote:
> The Frame Relay dissector is FAR from perfect, but I wanted to know what
> are you thinking about it.

It should perhaps also, if the protocol field is 0x0300, treat that as
RFC 2427-style "Multiprotocol Interconnect over Frame Relay" - the next
byte after the 0300 is an NLPID, and then, if the NLPID is 0x80
(NLPID_SNAP), what follows is a SNAP header (a handler for which should
probably be exported by "packet-llc.c").

For example, frame 7 of your Frame-Relay-over-GRE capture is probably an
ARP frame - after the 0300 comes 0x80, for NLPID_SNAP, followed by 3
bytes of 00, for "encapsulated Ethernet", followed by 0806, or
ETHERTYPE_ARP.

(RFC 2427 discusses the full story of the first 2 bytes of the payload -
the first byte is 0x03, but it may be followed immediately by an NLPID
or may be followed by a pad byte.)