Ryan Lovett wrote: > What does this mean?
It means that there needs to be some way in a Wireshark protocol tree to distinguish "XXX is a protocol inside YYY" from "XXX is the next instance of a protocol after the YYY instance of that protocol". Currently, there isn't, so the protocol statistics are bogus for protocols that, for example, run over TCP, so that you can have multiple packets for the protocol within one TCP segment. > Is the mysql protocol hierarchy fragmented into minor > mysql protocols? No, but, from the point of view of the protocol statistics code in Wireshark, it looks that way. _______________________________________________ Wireshark-users mailing list Wireshark-users@wireshark.org http://www.wireshark.org/mailman/listinfo/wireshark-users
