This session was recorded at Sharkfest 2017 - June 19th at Carnegie Mellon University in Pittsburgh. It delves into the reasons why people blame the network for performance problems, why these issues linger, and how network engineers can solve them using Wireshark. I hope this helps you in resolving those pesky network and application issues.

Packets don’t lie – well, most of the time. They tell the truth unless they have been captured incorrectly. In those cases, packets can tell bold-faced lies. When digging through trace files, we can come upon symptoms in the packets that may raise an eyebrow. These are events that look strange on the surface and […]

  Sometimes packet digging can get tedious. We've all been there. It can be hard to set the right filter that lets us hone in on the root cause. In many cases, it is just as helpful to remove protocols from view that are not probably not related to the problem. At least that will […]

It’s all about time. When it comes to network monitoring, NetFlow and Metadata-based tools allow engineers to get a handle on traffic usage, statistics, capacity, and even security attacks. They quickly help us visualize the conversations and applications involved in congestion, as well as hone in on strange traffic behavior. It would be difficult (and […]

The delta time column has always been one of the first things to add when configuring Wireshark. It shows the time between displayed packets, or captured packets, depending on how you set it up. It makes finding delays in conversations much easier to do - that is unless you are dealing with a trace file […]

What is the difference between a regular retransmission and a spurious one? What can I do about them if I find them in a trace file? Spurious retransmissions are not uncommon. They find their way into our trace files somewhat often. In this video, we explain the differences in retransmission flavors, as well as examine […]