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] Re-use of header fields

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


From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Wed, 09 Aug 2006 12:44:01 -0700

Benjamin M Stocks wrote:

Great! Thanks for the answer, as a follow up question: how does it work when I want to filter on a header field? Will it match ANY of the fields?

Yes. A filter "foo.bar == X", for example, matches all packets that have at least one instance of a "foo.bar" field with the value "X.

(This means, BTW, that the negation of "foo.bar == X" is *NOT* "foo.bar != X". "foo.bar != X" matches all packets that have at least one instance of a "foo.bar" field with a value other than X, but a packet could have one instance with the value "X" and another with the value "Y" and thus match *both* filters. The negation of "foo.bar == X" is "!(foo.bar == X)".)

  • References:
    • Re: [Wireshark-dev] Re-use of header fields
      • From: Benjamin M Stocks
  • Prev by Date: Re: [Wireshark-dev] Re-use of header fields
  • Next by Date: Re: [Wireshark-dev] X11/GLX dissector
  • Previous by thread: Re: [Wireshark-dev] Re-use of header fields
  • Next by thread: [Wireshark-dev] Small ANSI-637 patch for identifying more Teleservice
  • Index(es):
    • Date
    • Thread

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