Spurious TCP SEQ/ACK analysis errors

[Graham Bloice <graham.bloice () trihedral com>]

 Are folks seeing a lot of these on trunk?  Almost every capture I load seems
to have some "TCP ACKed lost segment" and "TCP Previous segment lost"
warnings, even though the sequence numbers are fine.

Even more oddly, the displayed warnings toggle on and off with every click of
the reload button, along with the Seq value in the first packet (a SYN)
changing from absolute to relative (in both the Info column and the packet
tree for TCP).

I've also just noticed the stream index field for the first packet toggles
between 0 and some other integer with each reload.

-- 
Regards,

Graham Bloice

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe