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] [PATCH] Dissector hooks: Small and Simple additions

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


From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Thu, 1 Mar 2007 19:46:51 -0800


On Mar 1, 2007, at 4:57 PM, Shehjar Tikoo wrote:

One drawback of a per-field hook could be that hooks which need a global
view or state of the full message might not get access to the needed
fields.

Couldn't the private data passed to the hook be used to store the kind of state needed for that?

Also, can this be done with the existing tap mechanism, by searching for particular fields in the generated protocol tree?

  • Follow-Ups:
    • Re: [Wireshark-dev] [PATCH] Dissector hooks: Small and Simple additions
      • From: Shehjar Tikoo
    • Re: [Wireshark-dev] [PATCH] Dissector hooks: Small and Simple additions
      • From: Shehjar Tikoo
    • Re: [Wireshark-dev] [PATCH] Dissector hooks: Small and Simple additions
      • From: Shehjar Tikoo
  • References:
    • Re: [Wireshark-dev] [PATCH] Dissector hooks: Small and Simple additions
      • From: Shehjar Tikoo
  • Prev by Date: Re: [Wireshark-dev] [PATCH] Dissector hooks: Small and Simple additions
  • Next by Date: Re: [Wireshark-dev] [PATCH] Dissector hooks: Small and Simple additions
  • Previous by thread: Re: [Wireshark-dev] [PATCH] Dissector hooks: Small and Simple additions
  • Next by thread: Re: [Wireshark-dev] [PATCH] Dissector hooks: Small and Simple additions
  • Index(es):
    • Date
    • Thread

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