Wireshark-bugs: [Wireshark-bugs] [Bug 10725] New: Retransmission incorrectly identified as out-o
| Bug ID |
10725
|
| Summary |
Retransmission incorrectly identified as out-of-order
|
| Product |
Wireshark
|
| Version |
1.12.2
|
| Hardware |
x86
|
| OS |
Windows Vista
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
Jim@agdatasystems.com
|
Created attachment 13288 [details]
Trace with retransmission identified as out-of-order
Build Information:
Version 1.12.2 (v1.12.2-0-g898fa22 from master-1.12)
Copyright 1998-2014 Gerald Combs <gerald@wireshark.org> 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.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
with
MIT Kerberos, with GeoIP, with PortAudio V19-devel (built Nov 12 2014), with
AirPcap.
Running on 32-bit Windows Vista Service Pack 2, build 6002, 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 3.2.15, Gcrypt 1.6.2, with AirPcap 4.1.1 build
1838, from the PortableApps U3 device in drive L:.
AMD Athlon(tm) 64 X2 Dual Core Processor 4000+, with 1917MB of physical memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
In Wireshark 1.12, a packet should be identified as a retransmission if it
arrives more than one RTT from when it should have arrived, provided the TCP
three-way handshake is present in the trace.
In the attached trace file, the initial RTT is 167 ms.
Wireshark 1.12.2 identifies packet 239 as out-of-order. Looking at the sequence
numbers, packet 239 should have arrived right after packet 183. In fact, packet
185 shows "TCP Previous segment not captured." Setting a Time Reference on
packet 185 gives a time from packet 185 to packet 239 of 296 ms. This is 129 ms
MORE than the initial RTT.
Packet 239 should have been identified as a retransmission, instead of
out-of-order, since it arrives considerably more than either 3 ms or the
initial RTT from when it should have.
You are receiving this mail because:
- You are watching all bug changes.
