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

["Carlos M. Pignataro" <cpignata@xxxxxxxxx>]

At 02:05 AM 5/2/2004 -0700, Guy Harris wrote:
>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.

That was exactly my thought. Like the control field after dsap ssap.


>If so, I guess it'd belong at the same layer as the protocol type field.

Yes.

>Are there any protocol type field values other than 0xfefe that have
>that pad byte? 

No. Only for 0xfefe. I agree it makes sense to put in the chdlc dissector.

Thanks,

--Carlos.

> If not, it might make sense to put it in the CHDLC
>dissector.
>
>_______________________________________________
>Ethereal-dev mailing list
>Ethereal-dev@xxxxxxxxxxxx
>http://www.ethereal.com/mailman/listinfo/ethereal-dev