Using Wireshark to Test Troubleshooting Tools
In this video, Tony Fortunato demonstrates how he used Wireshark to analyze a traceroute utility.
October 2, 2017
![Network Computing logo Network Computing logo](https://eu-images.contentstack.com/v3/assets/bltde8121fc52c5c8f3/blt3f3d0318f746b1c2/65a530e4187606040a1d8b8c/placeholder.png?width=1280&auto=webp&quality=95&format=jpg&disable=upscale)
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
You May Also Like
Maximizing cloud potential: Building and operating an effective Cloud Center of Excellence (CCoE)
September 10, 2024Radical Automation of ITSM
September 19, 2024Maximizing Manufacturing Efficiency with Real-Time Production Monitoring
September 25, 2024