Wireshark-dev: [Wireshark-dev] 6lowpan dissector fails RFC 4944 compliance: field hop limit

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: John Sucaet <john.sucaet@xxxxxxxxxxxxxxxxx>
Date: Thu, 22 Jul 2010 11:33:47 +0200
Hi,

According to RFC 4944, §10.3.1:

...
The non-compressed IPv6 field that MUST be always present is the Hop
   Limit (8 bits).  This field MUST always follow the encoding fields
   (e.g., "HC1 encoding" as shown in Figure 9), perhaps including other
   future encoding fields).  Other non-compressed fields MUST follow the
   Hop Limit as implied by the "HC1 encoding" in the exact same order as
   shown above (Section 10.1) ...


packet-6lowpan.c assumes the hop limit field following the other non-compressed fields.

I am using Wireshark 1.4.0rc1

Is this the correct way to report an error in a dissector or should I file a bug report in the wireshark bug db?


Kind regards

John Sucaet