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-bugs: [Wireshark-bugs] [Bug 3231] Tshark capture filter does not work when IP is of APIPA type (169.254)

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


From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 2 Feb 2009 10:08:10 -0800 (PST)

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3231





--- Comment #1 from Sake <sake@xxxxxxxxxx>  2009-02-02 10:08:04 PDT ---
Are you sure the frames you are *not* seeing when using a capture filter are
not vlan-tagged? Could you provide a small capture file on that interface when
no filter is applied?

AFAIK, there is no ip-address awareness in the capture filter code...


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  • References:
    • [Wireshark-bugs] [Bug 3231] New: Tshark capture filter does not work when IP is of APIPA type (169.254)
      • From: bugzilla-daemon
  • Prev by Date: [Wireshark-bugs] [Bug 3231] New: Tshark capture filter does not work when IP is of APIPA type (169.254)
  • Next by Date: [Wireshark-bugs] [Bug 3204] Brought up to date with version C of the specification
  • Previous by thread: [Wireshark-bugs] [Bug 3231] New: Tshark capture filter does not work when IP is of APIPA type (169.254)
  • Next by thread: [Wireshark-bugs] [Bug 3231] Tshark capture filter does not work when IP is of APIPA type (169.254)
  • Index(es):
    • Date
    • Thread

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