Ethereal-dev: Re: [Ethereal-dev] Patch for CLNS over Cisco HDLC dissecting

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

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Guy Harris <gharris@xxxxxxxxx>
Date: Sun, 2 May 2004 02:05:16 -0700
On Sat, May 01, 2004 at 11:38:49PM -0400, Carlos M. Pignataro wrote:
> I suppose it's a matter of point of view or perception, as to where
> the padding byte "belongs" to.

Yeah, that's a good question.

0xFE is an 802.2 LLC SAP value for OSI network layer protocols; perhaps
the idea was that, following the C-HDLC header, you had something that
sort of looked like an 802.2 header, e.g. 0xfe 0xfe {pad byte}, where
the pad byte would be equivalent to an 802.2 control field byte.

If so, I guess it'd belong at the same layer as the protocol type field.
Are there any protocol type field values other than 0xfefe that have
that pad byte?  If not, it might make sense to put it in the CHDLC
dissector.