Wireshark will also do a lot of analysis for us. As an example, when we were frag‐
menting packets earlier using
fragroute
, Wireshark would have colored frames that
weren’t right. If a packet’s checksum didn’t match, for instance, the frames belonging
to that packet would have been colored black. Any error in the protocol where the
packet is malformed would result in a frame that was colored red. Similarly, TCP
resets will get a frame colored red. A warning would be colored yellow and may result
from an application generating an unusual error code. You may also see yellow if
there are connection problems. If you want to save a little time, you can use the Ana‐
lyze menu and select Expert Info to see the entire list of frames that have been flag‐
ged. You can see a sample of this view in
Figure 2-6
.
Figure 2-6. Expert information output
Wireshark has so many capabilities; we aren’t even skimming the surface of what it
can do. A lot of what you may find it useful for is just to see the headers for each
protocol broken out in a way that you can easily read them. This will help you see
what is happening if you run into issues with your testing. One other feature I should
mention is the statistics menu. Wireshark will provide graphs and different views of