| Bug ID |
8223
|
| Summary |
tshark display filter (-R) work on segments
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
x86
|
| OS |
Windows XP
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
TShark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 9815 [details]
Sample capture
Build Information:
Version 1.8.4 (SVN Rev 46250 from /trunk-1.8)
Copyright 1998-2012 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (32-bit) with GTK+ 2.24.10, with Cairo 1.10.2, with Pango 1.30.0, with
GLib 2.32.2, with WinPcap (4_1_2), with libz 1.2.5, without POSIX capabilities,
with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS
2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio
V19-devel (built Nov 28 2012), with AirPcap.
Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.2
(packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
Built using Microsoft Visual C++ 10.0 build 40219
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Tshark read filter when applied to a infile produces a different result that
wireshark read filter applied to the same file.
On the attached file:
tshark -r infile -R "ip.src == 10.90.130.69 && ip.dst == 10.90.130.66 &&
tcp.flags.push == 1" outfile
It return the packet with the TCP PSH flag.
On wireshark when i set the same read filter: "ip.src == 10.90.130.69 && ip.dst
== 10.90.130.66 && tcp.flags.push == 1", the result is similar, it displays the
packet with the TCP PSH flag.
On export wireshark will export the complete segment, the 2 packets, instead of
a single one.
Which one is the correct behavior?
How to reproduce wireshark behavior in tshark?
You are receiving this mail because:
- You are watching all bug changes.