https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4075
--- Comment #4 from Owen Kirby <osk@xxxxxxxxxx> 2009-10-05 11:14:35 PDT ---
Bill:
> Owen:
>
> There are 2 instances where the comments say "Pad ...." for which the
> associated code (upon quick inspection) doesn't seem to act as indicated by the
> the comment.
At line 1045, before parsing the flow label in an IPHC header, the padding is
inserted by adding bits to the offset before parsing the next field. And at
line 1383, the padding isn't being parsed from the packet, but is instead being
added to the end of the reconstructed IPv6 extension header (in order to
guarantee the 8-byte alignment required by IPv6).
>
> Also: the Example capture file doesn't seem to have frames of the following
> 6LoWPAN types:
> - Broadcast;
> - IP Header Compression;
> - Mesh.
>
> Can you provide a capture file (or files) with these types ??
Unfortunately, I cannot at this time, our current 6LoWPAN implementation
doesn't generate these header types yet. I tested the dissector for these types
by repeatedly fuzz testing the example captures until the right header options
appeared. Embarrassingly bad programming, I apologize :)
Thanks,
Owen
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.