Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: Re: [Wireshark-dev] malformed packet

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Jeff Morriss <jeff.morriss.ws@xxxxxxxxx>
Date: Mon, 07 Jul 2008 11:26:22 -0400



Martin Corraine (mcorrain) wrote:
Hello,
If I check a packet's header and size and return 0 because it wasn't my protocol (GED125), should I get the following message: "Malformed Packet: GED125"?

Probably not.

Are you sure it's actually returning 0 for that packet? It sounds like your dissector generated an exception (normally because it read beyond the end of a TVB). Maybe you need to check tvb_length() before the rest of your heuristic checks?

  • References:
    • [Wireshark-dev] malformed packet
      • From: Martin Corraine (mcorrain)
  • Prev by Date: Re: [Wireshark-dev] col_set_str not working from plugin ?? bug 1967
  • Next by Date: [Wireshark-dev] buildbot failure in Wireshark (release) on OSX-10.5-x86
  • Previous by thread: [Wireshark-dev] malformed packet
  • Next by thread: [Wireshark-dev] buildbot failure in Wireshark (release) on OSX-10.5-x86
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation