Wireshark-bugs: [Wireshark-bugs] [Bug 11397] DUP ACK Counter resetting after Window Update

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 27 Jul 2015 23:11:13 +0000

Comment # 8 on bug 11397 from 
> shouldn't frames #18, #43 and #79 also be marked as DUP ACK's?  The ACK #
> hasn't changed since frame 15.  I guess the problem is that the PSH bit is set
> for all 3 of those frames, so that is the reason?

Ya, the code currently only marks it as a dupack if `seglen == 0`, which is not
satisfied by those packets since they actually carry data. Whether that's a
legitimate condition or not is beyond my knowledge of TCP internals.

Regardless, I'm more comfortable with the current state of my change now.

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