https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12855

--- Comment #15 from Peter Wu <pe...@lekensteyn.nl> ---
So Erik also reported this problem on SF and there is another post on Ask
wondering about this issue. Would it be possible to revert to the previous
behavior while a long-term fix is being developed?

Or at least take Pascal's patch and hope for the best?

As for your suggestions, tieing seq numbers with the data is effectively what
the reassembly API is doing right?

If you then want to allow for gaps while following the TCP stream, maybe the
TCP window size can be used as a hint on whether data is still expected or not
before attempting partial reassembly.

-- 
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

Reply via email to