Digging Deep Into The IT World

Have you ever encountered a situation?  when you ping a device, it fails but when you traceroute to the same devices, it works. At the end of the blog post, you will have a great understanding of why this happens. In my previous blog post "But How Does Traceroute Works", I have explained in detail how does traceroute works. You can continue reading this blog post without reading my previous blog post but it will really help you out to read that blog post as well. Click  But How Does Traceroute Works?  to read my previous blog. For the purpose of demonstration, I will use the following topology. Figure 1 Throughout this blog post i will use the terms Source and Destination. Whereas  Source = Kali-Linux ( having ip address 192.168.10.105) Destination = Linux Server ( having ip address 192.168.30.105). Case 1 Linux Server  can receive ICMP echo request packets and can respond with ICMP echo replies when it receives ICMP echo request packets. ping -c 4 192.168.30.10...

What is Traceroute? So if you want to determine the HOP count ( total number of HOPs that packets travel through.)  from source to destination or in other words if you want to trace the path that packets take from source to destination you will use Traceroute .     Is It Traceroute Or Tracert ?  Though both Traceroute and Tracert do the same job, they work a bit differently. I will explain it later in detail. For the time being keep in mind that the Traceroute utility is available on Unix-like systems such as Linux and macOS , It is also available on Cisco IOS . Whereas Tracert utility   is available on Microsoft Windows. How does Traceroute work? To help you really understand this I would like to explain it in three different ways. Traceroute can be implemented using ICMP, UDP, and TCP. Traceroute over ICMP Traceroute over UDP Traceroute over TCP Before discussing all these, let us understand ICMP which will really help us understand this blog. ICMP stands for...