This post shows the paths of a network packet using PING and TRACEROUTE commands. Knowing the importance of how these packets travel through the network is a great way to enhance your skills in both Information Technology as well as Cybersecurity. You can learn the times it takes for a packet to travel through the network as well as how many routes it takes to reach its destination and be returned to you.
For the ping requests, I used Google.com, amazon.co.jp, and ireland.ie. The ping back from Google yielded four packets, sent, four packets received, zero lost packets and took an average of 34ms to make the round trip. Amazon.co.jp, Japan's amazon website yielded 4 packets sent, 4 packets received and zero lost packets, it took an average of 88ms to make the round trip. Finally, I attempted to ping the visitor site for Ireland, ireland.ie, after a few attempts the site timed out, four packets were sent, zero were received and four were lost. Several reasons for this error could be the firewall on my computer would not allow the packets to be sent, or the firewall on the receiver blocked the packets, there could also network configuration error or the network could be congested.
Using traceroute with the same sites that were used for Ping, I was able to determine the travel points of the packets sent and the length time it took for each site to respond. Google took an average of 35ms, Amazon Japan took an average of 59ms, after a brief time out the reconnection took approximately 82ms before timing out again and completing the trace. Finally, the ireland.ie site took a maximum of 118ms before timing out. The traceroute command can also be useful in tracking down IP addresses and checking to see if a site may be compromised by being able to see an unfamiliar IP address routing. Using this tool essentially allows someone to track sent IP packets along their route to their destination, the time it takes to reach them and be returned to the sender.
No comments:
Post a Comment