[Wireshark-dev] Undissected packet bytes

Hi list I was wondering if there is a comfortable way to find out undissected bytes in packets. This would be useful to find incomplete dissectors. Any hint? Thanks! Dario. ___ Sent via:Wireshark-dev mailing list

Re: [Wireshark-dev] Undissected packet bytes

As far as I know this is not currently available, but it would probably be fairly useful and easy. You just need to iterate the proto tree and keep track of which byte ranges are claimed/unclaimed. proto_find_field_from_offset does something related to this (it is used for matching bytes to fields

Re: [Wireshark-dev] Undissected packet bytes

There is some dissector (like ICMPv6, IEEE 802.11 or CAPWAP...) where there is already expert info about undecoded code... On Tue, Feb 3, 2015 at 6:15 PM, Evan Huus eapa...@gmail.com wrote: As far as I know this is not currently available, but it would probably be fairly useful and easy. You

[Wireshark-dev] Building on MAC fails after adding building of the bundle.

Hi, The build now fails with: packaging/macosx/osx-app.sh: line 588: macdeployqt: command not found make[2]: *** [app_bundle] Error 1 make[1]: *** [CMakeFiles/app_bundle.dir/all] Error 2 make: *** [all] Error 2 I don’t have the the path to macdeployqt in my PATH, should I? Fixing the path

[Wireshark-dev] itu-t .0 oid dissector

If you look at the second packet of the attached capture, Wireshark considers this a malformed packet. As per RFC 1155 Section 3.1 The root node itself is unlabeled, but has at least three children directly under it: one node is administered by the International Organization for