| Bug ID |
11624
|
| Summary |
TCP ACKed unseen segment
|
| Product |
Wireshark
|
| Version |
1.12.6
|
| Hardware |
x86
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Build process
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 13931 [details]
Wireshark capture
Build Information:
Version 1.12.6 (v1.12.6-0-gee1fce6 from master-1.12)
Copyright 1998-2015 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.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 Jun 17 2015), with
AirPcap.
Running on Windows Server 2003 Service Pack 2, build 3790, 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, without AirPcap., with
3839MB
of physical memory.
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.
--
Hello Wireshark,
I have read the other bugs related to "TCP ACKed unseen segment" and I still
think Wireshark v1.12.6 reports this incorrectly. Please note that v1.99.8
(legacy) also shows the same display.
Please see the attached capture. Packets 39-46 are ACKing for packet 47.
Shouldn't this be normal behavior to ack for the next expected packet with
data? Look at packets 69-76. 69-74 are ACKing for packet 76, but these are not
flagged as "TCP ACKed unseen segment".
I looked for a TCP preference to change the behavior but I could not find any.
Can you help please?
Thank you,
Tom Ferguson
You are receiving this mail because:
- You are watching all bug changes.