[Bug 8404] New: Bug with TCP Acked unseen segment

[b***@wireshark.org]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8404

Bug ID: 8404
Summary: Bug with TCP Acked unseen segment
Classification: Unclassified
Product: Wireshark
Version: 1.8.4
Hardware: x86
OS: Windows XP
Status: UNCONFIRMED
Severity: Normal
Priority: Low
Component: Wireshark
Assignee: bugzilla-***@wireshark.org
Reporter: ***@siemens.com

Created attachment 10123
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=10123&action=edit
The trace where the error occurs

Build Information:

--
There is a message "TCP Acked unseen segment", but obviously the specified
segment has been trace.
A part of the trace is saved at cloudshark:
http://www.cloudshark.org/captures/a47e3794dd1a

[b***@wireshark.org]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8404

***@gmail.com changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #1 from ***@gmail.com ---
I received a similar bug in wireshark (ver 1.86) recently.

Attaching error wireshark trace - error.pcap

If you see packet #11 is received correctly and ACK in packet #12 is correctly
ACKing the packet but still an error is displayed "TCP ACKed unseen packet"

[b***@wireshark.org]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8404

--- Comment #2 from ***@gmail.com ---
Created attachment 10705
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=10705&action=edit
trace showing the issue - error.pcap

[b***@wireshark.org]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=8404

Josh <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com