Wireshark VS mtr

To begin with Wireshark, visit their official website for the download. The installation process is straightforward, but attention should be paid to the installation of command-line tools, which may require separate steps. Upon launching Wireshark, users are greeted with a selection of network interfaces as seen below. Choosing the correct interface, such as the loopback for local server debugging, is crucial for capturing relevant data.

Wireshark

If you're very curious as to what is really going on under the hood, I recommend you familiarize yourself with port mirroring for your switch platform of choice, and then use a laptop in promiscuous mode to capture traffic using Wireshark. Failing that, hire a network engineer to interview one of their sales engineers or architects, and have them explain it to you.

You should do a hands fins-on lab with Wireshark.

A great way to test the effectiveness of a pinning implementation is by simulating an MITM attack. Tools like Mitmproxy or Wireshack allow us to create a test environment to monitor, intercept, and proxy network requests for a test host.

They even have a nice comment explaining the heuristic: https://github.com/wireshark/wireshark/blob/ef9c79ae81b00a63...

     * Heuristics to detect the WireGuard protocol:

This has been put together for Wireshark, starting on line 1520 https://github.com/wireshark/wireshark/blob/master/epan/dissectors/packet-cip.c

Obviously based on the question you know the answer is a Wireshark-like software and it boils down to how you classify Wireshark. My issue is that Wikipedia refers to it as a Packet Analyzer, Varonis refers to it as a Packet Sniffer, Wireshark refers to itself as a Network Protocol Analyzer, Kali documentation refers to it as a Network Sniffer, Wireshark's README refers to itself as a Network Analyzer OR Sniffer...

As a reminder, Trippy combines the functionality of traceroute and ping and is designed to assist with the analysis of networking issues. You can think of it as a modern, cross platform, Rust based version of tools such as mtr, with a bunch of advanced features and a fancy TUI.

Cool project! Two suggestions, one serious, one frivolous:

- I wonder if you could get more accurate results by using TCP or UDP instead of ICMP. I think traditional traceroute has an option to use UDP, mtr [1] can use TCP or UDP, and tcptraceroute [2] can use TCP.

- This would be a perfect fit for some Talking Heads references. "And you may ask yourself, well, how did I get here?" [3]

[1] https://github.com/traviscross/mtr

[2] https://linux.die.net/man/1/tcptraceroute

[3] https://en.wikipedia.org/wiki/Once_in_a_Lifetime_(Talking_He...

Run mtr, or whatever the Windows equivalent might be, and leave it running shortly before 4:15pm, and see where the traffic stops when the Internet shuts off.

Lot of great stuff here, haven’t seen MTR yet: https://github.com/traviscross/mtr

Consider using MTR (software) towards the actual end-point of the SIP connection to get a combination of traceroute and ping which will be much more revealing. This will also allow you to quickly identify if the problem is local to your equipment or somewhere along the path. Consider allowing her to join a Google Conference from Teams to determine if it is provider related. Yes, port mirroring and wire shark is the gold standard and will display the "answer" on your screen quickly but it requires skills to know what to analyze, look at and how to interpret the data.

Have you tried something like mtr to check for connection issues? I would recommand the view you get when hitting d twice after starting it (with the colored graph for latencies).

Continuing to build trippy; a network diagnostic tool inspired by mtr. There is still a long way to go but it is getting closer to feature parity with mtr.