The need for traceroute and tracert tools
Digital networks are a constantly changing phenomena, which means, they require constant monitoring and reconfiguration if they are to be kept as efficient as possible. This means the administrators that are responsible for the upkeep of such networks require tools that help them make sense of what today, has become a complicated mash-up of digital highways connecting a cornucopia of gadgets that communicate using insanely-fast data transfer traffic. Their users, on the other hand, have come to expect reliable and fast connections whenever they log on to a network (local or otherwise).
These two common scenarios have created a demand for tools that help make all stakeholders happy. And among many such tools, there is one that can help with identifying connectivity and latency issues: the traceroute or tracert command.
Here is our list of the 3 best traceroute utilities and tracert software tools:
- SolarWinds Traceroute NG – FREE TOOL EDITOR’S CHOICE Vital free tool for troubleshooting network connection issues. Provides an analytical view from source to the destination hosts. Download for free.
- VisualRoute Favored for the GUI visualizations (see screenshots in mini-review below), also offers good reporting and even diagnostics.
- Path Analyzer Pro Simple and efficient tool for both Mac and Windows users, with comprehensive reports.
What is traceroute or tracert?
Traceroute and tracert are two commands that run tools used for network diagnostics and help with resolving connectivity issues by tracing the paths data packets take while traveling from their origins to their destinations.
Related post: What is Matt’s TraceRoute?
On a Windows machine an admin would use the tracert command; while on a Linux or Mac OS one they would use the “traceroute” command instead. The syntaxes for the commands are:
tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout] [-R] [-S srcaddr] [-4] [-6] target_name
traceroute [-46dFITUnreAV] [-f first_ttl] [-g gate,…] [-i device] [-m max_ttl] [-p port] [-s src_addr] [-q nqueries] [-N squeries] [-t tos] [-l flow_label] [-w waittimes] [-z sendwait] [-UL] [-D] [-P proto] [–sport=port] [-M method] [-O mod_options] [–mtu] [–back] host [packet_len]
Although the original tools were initially conceived to run from the CLIs (Command Line Interfaces), there are now more “flashier” versions with remarkable GUIs (Graphical User Interfaces). In this article, we will explore three of the best tools for traceroute and tracert.
Screenshots of traceroute and tracert
In the image below, the tracert command is running on a Windows machine and traces the path data packets would need to traverse if it had to reach the www.yahoo.com domain.
As we can see from the two images, once the command is executed, the program sends out a query across the network. This is to see which routes can be used to transport data packets between the origin machine’s network and the destination’s network.
Trivia: A tracert command from a Windows operating system machine sends out an ICMP (Internet Control Message Protocol) echo request, while a traceroute command from a Linux (or Mac) machine uses the UDP (User Datagram Protocol). The response, however, is always sent back in ICMP, regardless of what the sending host’s operating system is.
How do tracert or traceroute work?
To see how traceroute/tracert works, let us take a look at a breakdown of what occurs once a tracert or traceroute command has been sent:
- The command sends an IP packet out to the target device or network and starts monitoring for reports that are sent back in the form of replies from connected intermediary devices like routers and switches.
- The packets “hop” around from one device to the next and send back replies that help figure out their round-trip-times (RTTs). RTT is defined as the length of time taken for a packet to be sent out and then for a reply to come back confirming it has reached its intended destination.
- Whenever the packets hit a device and bounce back a reply, the admin also gets a bit of information detailing its IP address and device name (if it has one).
- Every time a packet is sent out, it is assigned a TTL (Time to Live) value that defaults to a maximum of 30 hops (but can be changed at will). We can see the advantages of the TTL by looking at what happens as the packet travels or hops across the network:
Step 1: When the first packet is sent out it is assigned a TTL of 1. When it reaches the first network device the TTL is reduced by 1 (making it 0 and hence dropping the packet) and a response is sent back to the source. This returning message will close a transport cycle allowing for the RTT to be calculated. If the replying device was the intended target, then the process ends with a “Resolved” message. If not…
Step 2: A second packet will then be sent with a TTL of 2. It passes through the device identified in Step 1 (where it loses a TTL value) and moves on to the next connected device beyond it. When it reaches a second device, it drops a TTL (making it 0) and a reply is sent back to the original host.
Step … n: The packets keep going out with increasing TTL values (until the maximum is reached) and the replies keep returning with a little more detail about the network that connects the origin and destination hosts.
Step “maximum no. of hops”: Finally, when the packet with the maximum number of hops is sent out, one of two things can be expected:
- Either, the destination host is reached and the network path is resolved or,
- The last packet will lose its TTL value, get dropped, and end with a “maximum number of hops reached” error message indicating the host couldn’t be reached.
A little bit more about the TTL
The TTL value determines the number of intermediate routers or other connecting devices that are going to be traversed as the packet travels towards the destination host. The traceroute/tracert command launches packets with TTL values starting at 1 and gradually increasing with each subsequent outgoing packet.
The TTL values decrease every time the packet hops to a device. Any packet whose TTL value reaches zero, is discarded and a “Time Exceeded” ICMP error message is generated and sent back to the original host.
Proceeding in this way, the networking tool uses the packets and reply messages to build a list of routers that data has to traverse through, until the destination is reached and returns an “ICMP Echo Reply” message.
How does traceroute or tracert help network admins?
Once the network path has been mapped out, a network admin can simply look at it, follow the paths that were taken by consecutive packets. They can see for themselves where the problem is (in case of non-delivery of the packets) or that everything works just as well as it should.
Then, all that remains is to fix disconnected routers and tweak the ones that have a high latency or packet loss rate.
The best traceroute tools and tracert software
Now that we have an idea of how they work, let’s have a look at the three most efficient tracert or traceroute tools that every administrator can use to ensure they have a well-performing network.
What should you look for in a Traceroute tool?
We reviewed the market for tracert software and analyzed the options based on the following criteria:
- A clear layout of a route that is easy to read
- A record of the time each hop took
- The option to rerun tests to see path changes
- Support for both IPv4 and IPv6 addressing
- The ability to export results for analysis in other tools
- A free tool or a free trial for assessment
- A good set of functions that is worth paying for or a free tool that is worth installing
SolarWinds is one of the biggest players in the network performance monitoring market. They are the makers of some impressive tools including the Traceroute NG – an easy-to-use, yet efficient network connection monitoring tool.
Traceroute NG – the tool that makes it all clear
With Traceroute NG, an administrator would have access to accurate single-path analysis visibility via CLI from the source to the destination hosts. It would effectively identify the number of hops, respective IP addresses, hostnames, packet loss, and latency.
- It detects path changes and gives due notification
- The tool allows for continuous probing that yields an iteration number for the user
- Both IPv4 and IPv6 networks are supported and can be analyzed
- The path number and trace information can be saved in a .txt log file
- It is easy to copy data from the tool’s GUI to the clipboard
- The “switch” command allows admins to alternate the probe type between ICMP and TCP
- It allows for simultaneous logging (via the logging command) as well as probing
- DNS lookup can be enabled or disabled
- Lightweight tool allows you to run it on virtually any network off of any machine
- Supports both IPv4 and IPv6, making it flexible or larger networks utilizing more modern protocols
- Acts as a troubleshooting tool to detect packet loss, jitter, and latency
- Offers simple visual representations of network traffic
- Is completely free
- Advanced features such as enterprise reporting are supported but can be found in products like SolarWinds Network Performance Monitor
SolarWinds Traceroute NG is a FREE TOOL and can be downloaded at Solarwinds.com
SolarWinds Traceroute NG should be in every administrator’s toolbox. It’s great for detecting paths, offers continuous probing of IP addresses, has TCP and ICMP network path analysis, IPv4 & IPv6 compatible and is totally free to use.
100% Free Tool: solarwinds.com/free-tools/traceroute-ng
For network administrators looking for an exciting little tool that can perform as well as any of the more complex traceroute tools out there, they will certainly find it all in VisualRoute. This visual traceroute network tool is a joy to use as its GUI makes work a lot of fun.
VisualRoute – reporting and diagnostics at its best
Administrators can get analytics results and reports that give advice like, “In general this route offers a good throughput, with hops responding on average within 68ms. However, all hops after hop 12 in network ‘[Network for 18.104.22.168]’ respond slightly slower than average.”
- A graphical map of the traceroute result makes it easy to comprehend and consume the data.
- Although VisualRoute’s main purpose is to map network paths, it goes above and beyond to perform several other essential network diagnostics with more tools like:
- Reverse tracing with remote agents so admins perform a reverse trace between two locations without actually being in either of the locations.
- Reverse DNS lookup allows for the discovery of IP addresses behind a domain name.
- Ping plotting to gauge and capture response times of IP addresses over a given time and have the data available in informative graphs.
- Storage of tracert data for future reference and performance comparison.
- Sending out of continuous tracert commands over measured time intervals makes it easy for admins to monitor any performance degradations that could occur over time.
- Pairs traceroute commands with a global map, making it easy to see where connection issues exist
- Uses a timeline feature to see what networks along the hop are slower or drop connections
- Supports continuous monitoring as well detailed reporting
- The user interface can take some time to learn
- Would like to see a longer trial period
3. Path Analyzer Pro
Path Analyzer Pro is a visual traceroute tool that administrators with Mac machines can use alongside their Windows brethren as it works on both platforms. It is an amalgamation of tools that, apart from the main traceroute purpose, offers features that help with performance testing, DNS, Whois, and address resolution features.
Path Analyzer Pro – simple yet impressively efficient
Some of the features that admins can expect from their Path Analyzer Pro include:
- A concise and to-the-point GUI that even novices can easily master.
- Excellent time performance that sees admins getting results back 20 times faster.
- Elaborate, yet comprehensible, reports that can either be consumed on the platform or exported for other remote users. They have impressive graphics detailing every aspect of a network.
- Map-based location of IP addresses with zoom, pan, and details.
- E-mail address tracing that can be used by crime stoppers and fighters to dig up more details about spammers or senders of unsolicited email messages
- Available for Mac and Windows
- Can detect network drops, latency, and jitter, making it a solid option for troubleshooting VoIP networks
- Features simple network graphing
- Clunky – especially around the protocol and tracing mode options
- Reporting lacks customization options and isn’t as user friendly as some of the competing tools
traceroute and tracert will draw the network for you
If you are a network administrator, then you will truly appreciate the capabilities of the three best traceroute and tracert tools we have just seen. Using one or all of them will allow you to draw an accurate picture of your network and the connectivity that lies beyond it. Make use of the tools and you will always have a clear image of what your network looks like.
traceroute Tools & tracert FAQs
What does a route issue mean?
A route issue means that there is a problem somewhere on the path to the destination device. Usually, if there is an issue with one of the routers on a path to a faraway place, the neighboring routers will know about the problem and route traffic around the faulty node. Route issues are more likely to happen on your own network and be caused by an error in a routing table.
What is the difference between Traceroute and Tracepath?
Traceroute is an older utility and tracepath was created as a slight improvement. The main difference between the two is that tracepath gives the MTU without it being specifically requested. The MTU is available in the output for traceroute, but you have to add on an extra option in order to get it. One other old difference between the two was that traceroute was only available to superusers on Unix/Linux. However, it is now available to any user just like tracepath.
Why is Traceroute so slow?
Traceroute takes a lot longer than Ping to report back on a path because traceroute reports back on each node. So, if you are tracing a path over three nodes, traceroute goes out to the first node then gets a response, then it goes out to the second node and waits for a response, then it goes out to the third node and then gets a response, then it goes to the destination and waits for a response. All of that waiting and repeated probing means that Traceroute has more work to do than Ping, which just sends a message to the destination and waits for a response.