Traveling the Network Routable Path
Network packets travel through the network using switches and routers between the source and destination. There are the preamble, source, and destination in each packet and the information being sent (Payload). Using a packet tracing application such as the Cisco IP Packet tracer allows the Network Engineer to follow the packet path through the network and determine if their problems along the path. Diving a bit deeper, the network hop path can be manipulated using routing protocols or administrative distances. In other words, you can traffic shape packets to take network routes that you want.
I was a Network Engineer in my previous professional life and often used both of these tools. The PING command is important because it could tell me if the destination device is online. The challenge with PING is if the remote device is blocking ICMP protocol, the ping packets will fail to reach the destination. However, this does not mean the device is offline. By default, you send a 32byte packet four times to the receiver and expect to receive replies to each packet. Should the ping packet fail to echo back, you will see a lost packet in the output after the PING. Finally, you can manipulate the packet payload by increasing the payload to 1024Bytes or 2048Bytes and beyond. I like increasing to determine simple bandwidth capacity to and from source and destination.
Traceroute is another command that I enjoy using. Traceroute allows you to see the network path and hops (Routers) between the source and destination. This utility provides the response time at each hop. If a hostname is applied to the router, the output will be IP and hostname. Routers that don’t respond are either blocking ICMP packets or are down.
Leveraging my ping and traceroutes, the traceroute output of router hops depends on geographical locations and round trip time. The hop count and the round trip time are reduced as close to the destination as the source. However, another factor in round trip time is latency and jitter along the routable path.
Below are my outputs of ping and traceroutes for www.google.com, www.amazon.co.jp, and www.abc.net.au
Comments
Post a Comment