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-users: Re: [Wireshark-users] Destination capture filtering not working

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


From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Fri, 04 Jan 2008 12:45:41 -0800

Cliff Fogle wrote:

This also applies to tcpdump.

Not surprising, as this is probably a libpcap issue, and both tcpdump and Wireshark/TShark use libpcap to do capturing.

If I do an unfiltered capture and use a display
filter I see these packets,

If you look at those packets, is there an 802.1Q VLAN header between the Ethernet header and the IP header?

If so, you need to prefix the filters with "vlan and", e.g. "vlan and dst port 80".

  • Follow-Ups:
    • Re: [Wireshark-users] Destination capture filtering not working
      • From: Cliff Fogle
  • References:
    • [Wireshark-users] Destination capture filtering not working
      • From: Cliff Fogle
  • Prev by Date: [Wireshark-users] Destination capture filtering not working
  • Next by Date: Re: [Wireshark-users] Destination capture filtering not working
  • Previous by thread: [Wireshark-users] Destination capture filtering not working
  • Next by thread: Re: [Wireshark-users] Destination capture filtering not working
  • Index(es):
    • Date
    • Thread

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