Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Ethereal-dev: Re: [Ethereal-dev] WTAP_ENCAP_FRELAY

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

From: Guy Harris <gharris@xxxxxxxxx>
Date: Thu, 1 Jul 2004 01:37:04 -0700
On Wed, Jun 30, 2004 at 10:47:03PM -0400, Nisbet, Tom wrote:
> Someone at the frame relay forum eventually noticed that there is no such
> thing as a one octet frame relay address field, so they stole this bit
> in the first octet to indicate frame relay fragmentation, as defined
> in FRF.12.  The Sniffer is trying to decode this.

...and Ethereal, unfortunately, isn't.  That should probably be changed.


> =============================  Frame Number 2025 =============================
>       Frame source = (User)
>       Length = 87
>       Time received = 11/12/2003 05:48:50.068
> Frame Relay
>       Header = 0x0f00
>           0000 11.. 0000 .... = DLCI 48
>           .... ..1. .... 000. = (Response)
>       EtherType = 0x0800 IP

I assume that's output from some analyzer that's ignoring the problem
with the address field.