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: Shehjar Tikoo <shehjart@xxxxxxxxxxxxxxx>
Date: Mon, 05 Mar 2007 13:44:34 +1100

Hi

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

Thanks. I've been looking at the tap mechanism as a mechanism for the anonymizer and I see that we'll have to add calls to tap_queue_packet(..) in every packet-nfs.c:dissect_nfs_<messagetype> call to queue the message for the tap listener.

Is that an acceptable addition to the NFS dissector, since it doesn't already have a tap listener in it?

Regards
Shehjar

  • Follow-Ups:
    • Re: [Wireshark-dev] [PATCH] Dissector hooks: Small and Simple additions
      • From: Guy Harris
  • References:
    • Re: [Wireshark-dev] [PATCH] Dissector hooks: Small and Simple additions
      • From: Shehjar Tikoo
    • Re: [Wireshark-dev] [PATCH] Dissector hooks: Small and Simple additions
      • From: Guy Harris
  • Prev by Date: Re: [Wireshark-dev] WireShark + LUA
  • Next by Date: Re: [Wireshark-dev] [SPAM] - Re: WireShark + LUA - Email found in subject
  • 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