Don't forget that warning events are those that Wireshark refers to as non-critical but not a normal behavior of a protocol. Here, you have events such as these:
- TCP resets: They are part of the TCP protocol, but a connection should end with a TCP FIN and not with a TCP reset. So, in this case, it can be due to a problem, or just because the TCP developer has chosen to close a connection in this way.
- TCP zero window: An indication to a slow end device on the connection; here we have another behavior of the protocol that can be due to a problem on one of the sides of the connection, but this is still how TCP works.
Messages like unknown header, BER error: wrong tag in tagged type, and so on. These messages indicate that there ...