https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14937
--- Comment #7 from Graham Bloice <graham.blo...@trihedral.com> ---
I started implementing the outline discussed, and added a new internal flag and
display filter field for "dup ack (SACK)".
This appears to work well, however this means that a regular dup ack and dup
ack (SACK) are two different things and to find both in a capture you will need
to add both flags (tcp.analysis.duplicate_ack and tcp.analysis.duplicate_sack).
Is this acceptable?
The marking of retransmissions is quite a bit harder, the SACK options are
sequences which have been received, so I have to compute the sequences that are
missing in a map, then on receipt of an apparently out pf order sequence check
that map for a matching sequence number and annotate accordingly and then
adjust the map if only a portion of the "hole" has been filled.
--
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
