Wireshark-bugs: [Wireshark-bugs] [Bug 8316] New: tshark -2 -R "some filter issues
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 11 Feb 2013 20:10:23 +0000
Bug ID 8316
Summary tshark -2 -R "some filter issues
Classification Unclassified
Product Wireshark
Version 1.8.5
Hardware All
OS All
Status CONFIRMED
Severity Normal
Priority Low
Component TShark
Assignee bugzilla-admin@wireshark.org
Reporter wmeier@newsguy.com 

Build Information:
1.8...
--

    'tshark -2 -R "frame.number == 2" -r ...' doesn't display anything (even
though the frame exists in the input file).

    'tshark -2 -R "frame number == 1"  does work.

    'tshark -R "frame.number == 2" also works.


Another case:

Given: a ~ 400 frame capture file with 60 DNS queries (the last of which at
frame 372 doesn't have a response).

    'tshark -2 -R "dns && (dns.flags.response == 0) && ! dns.response_in" -r
...'

    finds the correct DNS query with no response but shows it as having
    frame number 60.

(Wireshark with the same filter works correctly).

You are receiving this mail because:
  • You are watching all bug changes.