Wireshark-bugs: [Wireshark-bugs] [Bug 12760] New: Export specified packets doesn't correctly exp
| Bug ID |
12760
|
| Summary |
Export specified packets doesn't correctly export filtered packets
|
| Product |
Wireshark
|
| Version |
2.0.5
|
| Hardware |
x86
|
| OS |
Windows NT
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
twinkeloogje@hotmail.com
|
Created attachment 14824 [details]
Different count for displayed packets
Build Information:
Version 2.0.5 (v2.0.5-0-ga3be9c6 from master-2.0)
Copyright 1998-2016 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 (64-bit) with Qt 5.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.11.0, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.
Running on 64-bit Windows 10, build 10586, with locale Dutch_Belgium.1252, with
WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version
1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without
AirPcap.
Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz (with SSE4.2), with 16266MB of
physical
memory.
--
I'm working with trace files from switch span sources - which seem to contain a
lot of duplicate packets. [the span traffic contains conversations from before
and after a firewall - same IP packets, different mac addresses]
I have an easy way of filtering the packets by specifying a eth.addr== filter
...
This works OK in the GUI, but when I try to export the specified packets, the
packet count doesn't match, and if I apply the reverse filter on the exported
file, there are still some packets found who didn't match the original filter.
You are receiving this mail because:
- You are watching all bug changes.
