Using Wireshark to Test Troubleshooting Tools

In this video, Tony Fortunato demonstrates how he used Wireshark to analyze a traceroute utility.

Tony Fortunato

October 2, 2017

1 Min Read
Network Computing logo

Every time I post a network troubleshooting article, I get email from readers asking how I did certain things or how to analyze packets. Even though I explain the methodology in many of the articles, I agree that it would help if I walked you through it.

In this video, I show you how I analyzed tracetcp, a traceroute tool available on GitHub that uses TCP instead of ICMP for network troubleshooting, using Wireshark.

Throughout the years, I’ve used the term “tool calibration” to describe the process of documenting how your tools behave. After you document how your tools behave, you can provide valuable feedback to the vendor regarding feature suggestions. The other benefit is that you can determine if any software upgrades change or affect the tool's behavior.

About the Author(s)

Tony Fortunato

Sr Network Performance Specialist

Tony Fortunato is a network performance expert who has been designing, implementing and troubleshooting networks since 1989. His company, The Technology Firm, provides clients of all sizes with services ranging from project management, network design, consulting, troubleshooting, designing custom-designed training courses, and assisting with equipment installation. Tony's experience in networking started with financial trading floor networks and ISPs, where he learned to integrate and support equipment from various vendors. Tony has taught and presented at numerous colleges and universities, public forums and private classes. He blogs frequently at NetworkDataPediaand has a popular YouTube channel.

Stay informed! Sign up to get expert advice and insight delivered direct to your inbox

You May Also Like

More Insights