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

Guy Harris <g...@alum.mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |CONFIRMED
     Ever confirmed|0                           |1

--- Comment #4 from Guy Harris <g...@alum.mit.edu> ---
At least part of the problem is that the *second* packet looks "enough like" a
TDS packet, so it marks the entire TCP connection as carrying TDS - but it
doesn't say "the stuff before this doesn't look like TDS, so if it really *is*
TDS, it's probably the middle and end of a TDS packet, so don't try to dissect
it", or something such as that.  That's the problem with byte-stream protocols
such as TCP.

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