Wireshark-bugs: [Wireshark-bugs] [Bug 11624] Wireshark erroneously reports "TCP ACKed unseen seg

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sat, 24 Oct 2015 12:26:03 +0000

Comment # 4 on bug 11624 from 
(In reply to Christopher Maynard from comment #3)
> (In reply to tferguson from comment #2)
> > However, #48 is acking for 12725 (up to, but not including, 12725) which is
> > seen in #47. seq 11456 with 1269 data. Can you explain this please?
> 
> Yes, this seems wrong to me.  I don't think Wireshark should be indicating
> "TCP ACKed unseen segment" here because clearly that segment is present in
> Frame 47.
> 
> But Frame 49 *should* be indicating "TCP ACKed unseen segment" as that's an
> ACK for a segment not captured somewhere between Frames 27 and 29.


I made a recent fix in packet-tcp.c for the handling of "TCP ACKed unseen
segment"(see fe8d943) which was done after v1.12.6 and v1.99.8.  (In fact, this
change may not yet be in a released Wireshark released version).

I don't know what Wireshark version Chris used as the basis for his comment
above when looking at the capture .

I'll look at this tomorrow (Sunday).

You are receiving this mail because:
  • You are watching all bug changes.