{"id":6726,"date":"2024-01-15T09:19:57","date_gmt":"2024-01-15T16:19:57","guid":{"rendered":"https:\/\/ioflood.com\/blog\/?p=6726"},"modified":"2024-01-15T09:20:21","modified_gmt":"2024-01-15T16:20:21","slug":"install-traceroute-command-linux","status":"publish","type":"post","link":"https:\/\/ioflood.com\/blog\/install-traceroute-command-linux\/","title":{"rendered":"How to Install and Use the ‘Traceroute’ Command in Linux"},"content":{"rendered":"
\n
\"Linux<\/figure>\n<\/div>\n

Are you trying to trace the route that your data packets take to reach a network host but finding it challenging? Like a digital breadcrumb trail, the ‘traceroute’ command in Linux can help you track this path. The ‘traceroute’ command is a network diagnostic tool for understanding and diagnosing network issues, making it a utility worth mastering. Additionally, it’s readily available on most package management systems, making the installation process straightforward once you know the steps.<\/p>\n

In this comprehensive guide, we will walk you through how to install the ‘traceroute’ command on your Linux system.<\/strong> We will cover methods for both APT and YUM-based distributions like Debian, Ubuntu, CentOS, and AlmaLinux. We will delve into more advanced topics like compiling from source and installing a specific version of the command. Finally, we will wrap up with guidance on how to use the ‘traceroute’ command and verify that the correct version is installed.<\/p>\n

So, let’s dive in and start installing ‘traceroute’ on your Linux system!<\/p>\n

TL;DR: How Do I Install and Use the ‘traceroute’ Command in Linux?<\/h2>\n

\n In most Linux distributions, the 'traceroute'<\/code> command comes pre-installed. If it’s not, you can install it in Debian based distributions like Ubuntu by running the command sudo apt-get install traceroute<\/code>. For distributions like CentOS that use the RPM package manager, you would run the command sudo yum install traceroute<\/code>.\n<\/p><\/blockquote>\n

For example:<\/p>\n

# For Debian based distributions like Ubuntu\nsudo apt-get install traceroute\n\n# For RPM based distributions like CentOS\nsudo yum install traceroute\n\n# Output:\n# Reading package lists... Done\n# Building dependency tree\n# Reading state information... Done\n# The following NEW packages will be installed:\n#   traceroute\n# 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.\n# Need to get 45.3 kB of archives.\n# After this operation, 192 kB of additional disk space will be used.\n# Get:1 http:\/\/archive.ubuntu.com\/ubuntu bionic\/universe amd64 traceroute amd64 1:2.1.0-2 [45.3 kB]\n# Fetched 45.3 kB in 1s (33.3 kB\/s)\n# Selecting previously unselected package traceroute.\n# (Reading database ... 130812 files and directories currently installed.)\n# Preparing to unpack ...\/traceroute_1%3a2.1.0-2_amd64.deb ...\n# Unpacking traceroute (1:2.1.0-2) ...\n# Setting up traceroute (1:2.1.0-2) ...\n# Processing triggers for man-db (2.8.3-2ubuntu0.1) ...\n<\/code><\/pre>\n
This is a basic way to install the ‘traceroute’ command in Linux, but there’s much more to learn about installing and using ‘traceroute’. Continue reading for more detailed information and advanced installation options.<\/p>\n
Understanding and Installing the ‘traceroute’ Command<\/h2>\n
The ‘traceroute’ command is a network diagnostic tool that provides a detailed view of the path that data packets take from your computer to a specified destination. It’s useful for identifying where problems occur when data is not reaching its intended destination. It’s a must-have tool for network administrators and anyone interested in understanding their network better.<\/p>\n
Let’s now dive into how to install the ‘traceroute’ command in Linux using different package managers.<\/p>\n
Installing Traceroute with APT<\/h3>\n
For Debian-based distributions like Ubuntu, we use the APT package manager to install the ‘traceroute’ command. Here’s how:<\/p>\n
sudo apt update\nsudo apt install traceroute\n\n# Output:\n# Reading package lists... Done\n# Building dependency tree\n# Reading state information... Done\n# The following NEW packages will be installed:\n#   traceroute\n# 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.\n# Need to get 45.3 kB of archives.\n# After this operation, 192 kB of additional disk space will be used.\n# Get:1 http:\/\/archive.ubuntu.com\/ubuntu bionic\/universe amd64 traceroute amd64 1:2.1.0-2 [45.3 kB]\n# Fetched 45.3 kB in 1s (33.3 kB\/s)\n# Selecting previously unselected package traceroute.\n# (Reading database ... 130812 files and directories currently installed.)\n# Preparing to unpack ...\/traceroute_1%3a2.1.0-2_amd64.deb ...\n# Unpacking traceroute (1:2.1.0-2) ...\n# Setting up traceroute (1:2.1.0-2) ...\n# Processing triggers for man-db (2.8.3-2ubuntu0.1) ...\n<\/code><\/pre>\n
The first command updates the list of available packages and their versions, while the second command installs the ‘traceroute’ package. The output confirms that the traceroute package has been successfully installed.<\/p>\n
Installing Traceroute with YUM<\/h3>\n
For RPM-based distributions like CentOS, we use the YUM package manager to install the ‘traceroute’ command. Here’s how:<\/p>\n
sudo yum check-update\nsudo yum install traceroute\n\n# Output:\n# Loaded plugins: fastestmirror\n# Loading mirror speeds from cached hostfile\n#  * base: mirror.sjc02.svwh.net\n#  * extras: mirror.sfo12.us.leaseweb.net\n#  * updates: mirror.sfo12.us.leaseweb.net\n# Resolving Dependencies\n# --> Running transaction check\n# ---> Package traceroute.x86_64 0:2.0.22-2.el7 will be installed\n# --> Finished Dependency Resolution\n<\/code><\/pre>\n
The first command checks for updates, and the second command installs the ‘traceroute’ package. The output confirms that the traceroute package has been successfully installed.<\/p>\n
Installing Traceroute from Source Code<\/h2>\n
If the package managers don’t offer the version of ‘traceroute’ you need, or if you simply prefer to compile your own binary, you can install ‘traceroute’ from the source code.<\/p>\n
First, you need to download the source code. For ‘traceroute’, you can find it on the Debian website. Use the ‘wget’ command to download it:<\/p>\n
wget http:\/\/deb.debian.org\/debian\/pool\/main\/t\/traceroute\/traceroute_2.1.0.orig.tar.gz\n\n# Output:\n# --2022-01-01 12:00:00--  http:\/\/deb.debian.org\/debian\/pool\/main\/t\/traceroute\/traceroute_2.1.0.orig.tar.gz\n# Resolving deb.debian.org (deb.debian.org)... 151.101.0.204, 151.101.64.204, 151.101.128.204, ...\n# Connecting to deb.debian.org (deb.debian.org)|151.101.0.204|:80... connected.\n# HTTP request sent, awaiting response... 200 OK\n# Length: 45484 (44K) [application\/x-gzip]\n# Saving to: \u2018traceroute_2.1.0.orig.tar.gz\u2019\n<\/code><\/pre>\n
Next, decompress the tarball and navigate into the new directory:<\/p>\n
tar xvf traceroute_2.1.0.orig.tar.gz\n\n# Output:\n# traceroute-2.1.0\/\n# traceroute-2.1.0\/COPYING\n# traceroute-2.1.0\/ChangeLog\n# ...\n<\/code><\/pre>\n
Finally, use ‘make’ to compile the source code and ‘make install’ to install it:<\/p>\n
make\nsudo make install\n\n# Output:\n# cc -DHAVE_CONFIG_H -I.  -D_GNU_SOURCE   -g -O2 -c traceroute.c\n# cc -g -O2  -o traceroute traceroute.o -lnsl -lm -lresolv\n# \/usr\/bin\/install -c traceroute \/usr\/local\/bin\/traceroute\n# \/usr\/bin\/install -c -m 644 traceroute.8 \/usr\/local\/share\/man\/man8\/traceroute.8\n<\/code><\/pre>\n
Installing Different Versions of Traceroute<\/h2>\n
Different versions of ‘traceroute’ may have different features or be compatible with different systems.<\/p>\n
Installing Different Versions from Source Code<\/h3>\n
To install a different version from source code, you can follow the same steps as above, but download a different tarball. For example, to install version 2.0.22, you would start with:<\/p>\n
wget http:\/\/deb.debian.org\/debian\/pool\/main\/t\/traceroute\/traceroute_2.0.22.orig.tar.gz\n<\/code><\/pre>\n
Installing Different Versions with Package Managers<\/h3>\n
With package managers, you can often specify a version to install. For example, with APT, you can use the ‘=’ operator:<\/p>\n
sudo apt-get install traceroute=2.0.22-2\n<\/code><\/pre>\n
With YUM, you can use the ‘-‘ operator:<\/p>\n
sudo yum install traceroute-2.0.22-2\n<\/code><\/pre>\n
However, not all versions may be available in the repositories used by your package manager.<\/p>\n
Version Comparison<\/h3>\n\n\n\n\n\n\n
Version<\/th>\nNotable Changes<\/th>\nCompatibility<\/th>\n<\/tr>\n<\/thead>\n
2.1.0<\/td>\nLatest stable release<\/td>\nMost systems<\/td>\n<\/tr>\n
2.0.22<\/td>\nLast version before major update<\/td>\nOlder systems<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Basic Usage of Traceroute<\/h2>\n
To use ‘traceroute’, you simply need to type ‘traceroute’ followed by the destination you want to trace a route to. For example:<\/p>\n
traceroute example.com\n\n# Output:\n# traceroute to example.com (93.184.216.34), 30 hops max, 60 byte packets\n#  1  router (192.168.1.1)  1.275 ms  1.233 ms  1.211 ms\n#  2  10.0.0.1 (10.0.0.1)  10.591 ms  10.589 ms  10.564 ms\n#  3  * * *\n#  4  * * *\n#  5  * * *\n#  6  example.com (93.184.216.34)  20.204 ms  20.393 ms  20.360 ms\n<\/code><\/pre>\n
This shows the route from your computer to example.com, including the time taken to reach each hop. If a ‘*’ is shown, that means the packet was lost or dropped.<\/p>\n
Verifying Traceroute Installation<\/h2>\n
To verify that ‘traceroute’ is installed correctly, you can use the ‘which’ command:<\/p>\n
which traceroute\n\n# Output:\n# \/usr\/sbin\/traceroute\n<\/code><\/pre>\n
This shows the location of the ‘traceroute’ binary, confirming that it is installed.<\/p>\n
Exploring Alternative Methods for Route Tracing in Linux<\/h2>\n
While ‘traceroute’ is a powerful tool, it’s not the only method for tracing routes in Linux. Let’s look at some alternative approaches, their advantages and disadvantages, and when you might want to use them.<\/p>\n
The ‘tracepath’ Command<\/h3>\n
The ‘tracepath’ command is another tool for tracing network paths. It’s similar to ‘traceroute’, but it doesn’t require root privileges and it automatically adjusts the packet length to find the MTU along the path.<\/p>\n
Here’s how to use ‘tracepath’:<\/p>\n
tracepath example.com\n\n# Output:\n#  1?: [LOCALHOST]                      pmtu 1500\n#  1:  gateway                                            2.598ms \n#  1:  gateway                                            2.570ms \n#  2:  no reply\n#  3:  no reply\n#  4:  no reply\n#  5:  example.com                                       20.265ms reached\n#      Resume: pmtu 1500 \n<\/code><\/pre>\n
This output is similar to ‘traceroute’, but it includes the Path MTU (PMTU) at each hop.<\/p>\n
Manual Route Tracing<\/h3>\n
You can also trace a route manually by using the ‘ping’ command with increasing TTL values. This method is more time-consuming and less convenient, but it can be useful for understanding exactly what happens at each step of the route.<\/p>\n
Here’s how to trace a route manually:<\/p>\n
for i in {1..30}; do ping -c 1 -t $i example.com; done\n\n# Output:\n# PING example.com (93.184.216.34) 56(84) bytes of data.\n# From gateway (192.168.1.1) icmp_seq=1 Time to live exceeded\n# ...\n<\/code><\/pre>\n
This runs a ‘ping’ command for each TTL value from 1 to 30. The output shows the response from each hop along the route.<\/p>\n
Comparing Route Tracing Methods<\/h3>\n
Each of these methods has its own advantages and disadvantages:<\/p>\n\n\n\n\n\n\n\n
Method<\/th>\nAdvantages<\/th>\nDisadvantages<\/th>\n<\/tr>\n<\/thead>\n
traceroute<\/td>\nDetailed output, widely used<\/td>\nRequires root privileges for full functionality<\/td>\n<\/tr>\n
tracepath<\/td>\nAutomatically finds PMTU, doesn’t require root<\/td>\nLess detailed output<\/td>\n<\/tr>\n
Manual<\/td>\nComplete control, educational<\/td>\nTime-consuming, less convenient<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Which method you should use depends on your specific needs and constraints. If you’re just starting out, ‘traceroute’ is a good choice because of its wide usage and detailed output. If you need to find the PMTU or can’t use root privileges, consider ‘tracepath’. If you want to learn more about how route tracing works, try tracing a route manually.<\/p>\n
Common Issues and Solutions with ‘traceroute’<\/h2>\n
While ‘traceroute’ is a powerful tool, like any software, it can sometimes behave unexpectedly or produce confusing results. Let’s discuss some common issues you may encounter when using the ‘traceroute’ command and how to solve them.<\/p>\n
‘traceroute’: command not found<\/h3>\n
If you see this error, it means ‘traceroute’ is not installed on your system. You can install it using your package manager, as we discussed earlier.<\/p>\n
sudo apt-get install traceroute\n\n# Output:\n# Reading package lists... Done\n# Building dependency tree\n# Reading state information... Done\n# The following NEW packages will be installed:\n#   traceroute\n# 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.\n# Need to get 45.3 kB of archives.\n# After this operation, 192 kB of additional disk space will be used.\n# Get:1 http:\/\/archive.ubuntu.com\/ubuntu bionic\/universe amd64 traceroute amd64 1:2.1.0-2 [45.3 kB]\n# Fetched 45.3 kB in 1s (33.3 kB\/s)\n# Selecting previously unselected package traceroute.\n# (Reading database ... 130812 files and directories currently installed.)\n# Preparing to unpack ...\/traceroute_1%3a2.1.0-2_amd64.deb ...\n# Unpacking traceroute (1:2.1.0-2) ...\n# Setting up traceroute (1:2.1.0-2) ...\n# Processing triggers for man-db (2.8.3-2ubuntu0.1) ...\n<\/code><\/pre>\n
‘traceroute’ output shows ‘*’ for all hops<\/h3>\n
If you see ‘*’ for all hops, it means the packets are not reaching their destination or responses are not coming back. This could be due to a network issue, a firewall blocking ICMP packets, or the destination host not responding. You may need to check your network settings or contact your network administrator.<\/p>\n
‘traceroute’ takes a long time or doesn’t finish<\/h3>\n
If ‘traceroute’ takes a long time or doesn’t finish, it could be due to network congestion, high packet loss, or a routing loop. You can try using the ‘-w’ option to adjust the wait time for responses, or the ‘-m’ option to adjust the maximum number of hops.<\/p>\n
traceroute -w 5 -m 20 example.com\n\n# Output:\n# traceroute to example.com (93.184.216.34), 20 hops max, 60 byte packets\n#  1  router (192.168.1.1)  1.275 ms  1.233 ms  1.211 ms\n#  2  10.0.0.1 (10.0.0.1)  10.591 ms  10.589 ms  10.564 ms\n#  3  * * *\n#  4  * * *\n#  5  * * *\n#  6  example.com (93.184.216.34)  20.204 ms  20.393 ms  20.360 ms\n<\/code><\/pre>\n
In this example, we’ve set the wait time to 5 seconds and the maximum number of hops to 20. This can help speed up ‘traceroute’ or prevent it from getting stuck in a routing loop.<\/p>\n
Remember, ‘traceroute’ is a diagnostic tool, so unexpected results often indicate network issues that need to be investigated.<\/p>\n
Delving into Network Routing Fundamentals in Linux<\/h2>\n
Before we delve deeper into the ‘traceroute’ command, let’s take a step back and understand the underlying concept: network routing in Linux. This knowledge will help you get a better grasp of the ‘traceroute’ command and its importance in network troubleshooting.<\/p>\n
Static vs Dynamic Routing<\/h3>\n
In Linux, there are two main types of routing: static and dynamic. Static routing is where routes are manually set up by an administrator, while dynamic routing involves protocols that automatically calculate routes.<\/p>\n
# Example of a static route\nsudo ip route add 192.0.2.0\/24 via 203.0.113.1 dev eth0\n\n# Output:\n# [No output means the command was successful]\n<\/code><\/pre>\n
In this example, we’re manually adding a static route to the network 192.0.2.0\/24 via the gateway 203.0.113.1 on the network interface ‘eth0’. This command doesn’t produce any output if it’s successful.<\/p>\n
Dynamic routing, on the other hand, uses protocols like RIP, OSPF, or BGP to automatically calculate the best path for data packets.<\/p>\n
Importance of Route Tracing in Network Troubleshooting<\/h3>\n
Route tracing, as performed by the ‘traceroute’ command, is an essential tool for network troubleshooting. It allows you to visualize the path data packets take from your computer to a destination host. This can help you identify where problems are occurring when data isn’t reaching its intended destination.<\/p>\n
For example, if you’re experiencing a slow network connection, running a ‘traceroute’ to the server you’re trying to reach can help identify if there’s a particular hop along the route that’s causing a delay.<\/p>\n
traceroute slow-website.com\n\n# Output:\n# traceroute to slow-website.com (203.0.113.1), 30 hops max, 60 byte packets\n#  1  router (192.168.1.1)  1.275 ms  1.233 ms  1.211 ms\n#  2  10.0.0.1 (10.0.0.1)  10.591 ms  10.589 ms  10.564 ms\n#  3  * * *\n#  4  slow-isp.com (203.0.113.1)  120.204 ms  120.393 ms  120.360 ms\n#  5  slow-website.com (203.0.113.2)  20.204 ms  20.393 ms  20.360 ms\n<\/code><\/pre>\n
In this example, you can see that the fourth hop to ‘slow-isp.com’ is taking significantly longer than the other hops. This suggests that the issue may be with ‘slow-isp.com’.<\/p>\n
The Relevance of Route Tracing in Network Administration and Security<\/h2>\n
Route tracing is an essential tool in the arsenal of network administrators and security professionals. By providing a detailed path of network traffic, it enables these professionals to pinpoint bottlenecks, detect anomalies, and troubleshoot connectivity issues. It’s a first line of defense in diagnosing network problems and ensuring optimal performance.<\/p>\n
Exploring IP Routing and Subnetting in Linux<\/h3>\n
‘IP routing’ and ‘subnetting’ are two fundamental concepts in network administration. IP routing is the process of sending data from a source to a destination on a network. Subnetting, on the other hand, is a way to divide a network into smaller, more manageable pieces.<\/p>\n
# Displaying the IP routing table\nip route show\n\n# Output:\n# default via 192.168.1.1 dev eth0 proto dhcp src 192.168.1.2 metric 100\n# 192.168.1.0\/24 dev eth0 proto kernel scope link src 192.168.1.2\n# 192.168.1.1 dev eth0 proto dhcp scope link src 192.168.1.2 metric 100\n<\/code><\/pre>\n
In this example, we’re displaying the IP routing table, which shows how packets will be forwarded based on their destination IP address.<\/p>\n
Further Resources for Network Mastery in Linux<\/h3>\n
If you’re interested in delving deeper into these topics, here are some resources that provide a wealth of information:<\/p>\n
    \n
  1. Linux Network Administrator’s Guide<\/a>: An in-depth guide to network administration in Linux, covering everything from basic networking concepts to advanced topics like IP routing and subnetting.<\/p>\n<\/li>\n
  2. \n
    The Linux Documentation Project<\/a>: A comprehensive resource for all things Linux, including detailed guides on networking and security.<\/p>\n<\/li>\n
  3. \n
    Linux Networking Commands<\/a>: This tutorial covers the basics of networking in Linux, including IP addressing, routing, and subnetting.<\/p>\n<\/li>\n<\/ol>\n
    Wrapping Up: Installing the ‘traceroute’ Command in Linux<\/h2>\n
    In this comprehensive guide, we’ve explored how to install and use the ‘traceroute’ command in Linux, an essential tool for network diagnostics.<\/p>\n
    We began with the basics, learning how to install ‘traceroute’ using package managers such as APT and YUM. We then ventured into more advanced territory, exploring how to install ‘traceroute’ from source code, and how to install specific versions. We also delved into the usage of ‘traceroute’, demonstrating how to trace a route to a destination and interpret the output.<\/p>\n
    Along the way, we tackled common issues you might face when using ‘traceroute’, such as command not found errors and confusing output, providing you with solutions and workarounds for each issue.<\/p>\n
    We also looked at alternative approaches to route tracing in Linux, comparing ‘traceroute’ with other methods like ‘tracepath’ and manual route tracing. Here’s a quick comparison of these methods:<\/p>\n\n\n\n\n\n\n\n
    Method<\/th>\nPros<\/th>\nCons<\/th>\n<\/tr>\n<\/thead>\n
    traceroute<\/td>\nDetailed output, widely used<\/td>\nRequires root privileges for full functionality<\/td>\n<\/tr>\n
    tracepath<\/td>\nAutomatically finds PMTU, doesn’t require root<\/td>\nLess detailed output<\/td>\n<\/tr>\n
    Manual<\/td>\nComplete control, educational<\/td>\nTime-consuming, less convenient<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
    Whether you’re just starting out with ‘traceroute’ or you’re looking to level up your network troubleshooting skills, we hope this guide has given you a deeper understanding of ‘traceroute’ and its capabilities.<\/p>\n
    With its balance of detail and wide usage, ‘traceroute’ is a powerful tool for network diagnostics in Linux. Happy troubleshooting!<\/p>\n","protected":false},"excerpt":{"rendered":"
    Are you trying to trace the route that your data packets take to reach a network host but finding it challenging? Like a digital breadcrumb trail, the ‘traceroute’ command in Linux can help you track this path. The ‘traceroute’ command is a network diagnostic tool for understanding and diagnosing network issues, making it a utility […]<\/p>\n","protected":false},"author":1,"featured_media":16030,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[124,3,9],"tags":[],"class_list":["post-6726","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-bash","category-linux","category-sysadmin","cat-124-id","cat-3-id","cat-9-id","has_thumb"],"_links":{"self":[{"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/posts\/6726","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/comments?post=6726"}],"version-history":[{"count":6,"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/posts\/6726\/revisions"}],"predecessor-version":[{"id":16081,"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/posts\/6726\/revisions\/16081"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/media\/16030"}],"wp:attachment":[{"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/media?parent=6726"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/categories?post=6726"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ioflood.com\/blog\/wp-json\/wp\/v2\/tags?post=6726"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}