Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 5548] Missing out of order detection

Date: Wed, 5 Jan 2011 09:11:05 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5548

--- Comment #4 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2011-01-05 09:11:03 PST ---
(In reply to comment #3)
> Yes, it's a valid ACK, but doesn't an out-of-order packet occur when a packet
> is seen with a sequence number lower than the previously sequence number on
> that connection direction, like packet #10?

Not for ACK's, or more accurately, as you suspected, not for any packet where
the segment length is zero.  From packet-tcp.c:tcp_analyze_sequence_number(),
starting at line 953:

    if( seglen>0
    &&  tcpd->fwd->nextseq
    &&  (LT_SEQ(seq, tcpd->fwd->nextseq)) ){
        ...

        /* out of order determination code */

        ...
    }

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.