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] New: 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 06:56:50 -0800 (PST)

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

           Summary: Tshark capture filter does not work when IP is of APIPA
                    type (169.254)
           Product: Wireshark
           Version: unspecified
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: TShark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: ioannis_k@xxxxxxxxxxx


Build Information:
Windows XP SP3, Wireshark 1.0.2 or 1.0.3 or 1.0.5 always with Winpcap 4.0.2.
--
I tried to capture from an Interface with an IP address of type 169.254 using
tshark with the following command:

tshark -i4 -a filesize:100 -b files:1000 -f "tcp port 80" -w tracetest.pcap

The result is that Tshark doesn't capture anything. When I do not use the
capture filter for that interface, I capture all the packets on the wire. 

At the same PC there are more interfaces and one of them has ip address
10.3.xxx.xxx and the same command (except that the -i4 is -i2 for example)
works without any problem.

I know that it is weird to have an interface set to 169.254 ... believe me it
was not my choice :-)

Thanks in advance for your help.

regards,
Yiannis


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

  • Follow-Ups:
    • [Wireshark-bugs] [Bug 3231] Tshark capture filter does not work when IP is of APIPA type (169.254)
      • From: bugzilla-daemon
    • [Wireshark-bugs] [Bug 3231] Tshark capture filter does not work when IP is of APIPA type (169.254)
      • From: bugzilla-daemon
    • [Wireshark-bugs] [Bug 3231] Tshark capture filter does not work when IP is of APIPA type (169.254)
      • From: bugzilla-daemon
  • Prev by Date: [Wireshark-bugs] [Bug 3163] MIBS error on launch 1.0.5
  • Next by Date: [Wireshark-bugs] [Bug 3231] Tshark capture filter does not work when IP is of APIPA type (169.254)
  • Previous by thread: [Wireshark-bugs] [Bug 3230] New: negative INTEGER number displayed as positive number in snmp dissector
  • 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