https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5952
--- Comment #5 from Guy Harris <guy@xxxxxxxxxxxx> 2011-05-25 10:41:49 PDT ---
"The 802.15.4 MAC header itself doesn't have a length field"
That's not unique to 802.15.4, so if its absence causes issues for 802.15.4, it
would also cause issues for other protocols.
"Frame.len seems to be the wrong size, as it includes everything below the
802.15.4 frame"
Maybe it's a question of what "below" means here; I presume you mean "it
includes the protocol layers inside which 802.15.4 is encapsulated", such as,
for ZEP, the link-layer header, IP header, UDP header, and ZEP header.
That's also not unique to 802.15.4, as other link-layer protocols can be
encapsulated inside other link-layer protocols. Perhaps there should be a
filter expression that, for a given protocol layer in a packet, gives the
length of the data initially handed to that protocol layer. Given that some
protocols have an FCS that may or may not be present in a capture (true, at
minimum, for 802.3, 802.11, and 802.15.4), perhaps there should be a way to
arrange that it not include the FCS (so that looking for frames of a given
length will work the same regardless of whether the capture happens to include
the FCS or not).
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
