Bug ID |
10260
|
Summary |
Wireshark display filter misses the lost segment (tcp.analysis.lost_segment) when receive window is full (tcp.analysis.window_full)
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
1.10.8
|
Hardware |
x86
|
OS |
Windows 7
|
Status |
UNCONFIRMED
|
Severity |
Normal
|
Priority |
Low
|
Component |
Dissection engine (libwireshark)
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Build Information:
Version 1.10.8 (v1.10.8-2-g52a5244 from master-1.10)
Copyright 1998-2014 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 (64-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, without Kerberos, with GeoIP, with
PortAudio V19-devel (built Jun 12 2014), with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Core(TM) i7-3740QM CPU @ 2.70GHz, with 8123MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
When a packet is tagged with receive window is full (tcp.analysis.window_full)
and this packet also comes after previous segment is lost (i.e. tagged with
tcp.analysis.lost_segment), then filtering this packet will work only with
"tcp.analysis.window_full" but not with "tcp.analysis.lost_segment"
You are receiving this mail because:
- You are watching all bug changes.