Traveling Through A Network
Here are the results from my Ping Tests.
Here are the results from my Trace Routes.
Traveling Through a Network Reflection Essay
So for this week's discussion, we will be breaking down how ping tests and trace routes work. The two are somewhat similar but have their differences. The ping test lets you send data via packets to the address that you have selected, and it sends back the allotted time that it took to get there. We use this at my job quite often, considering I work for a large ISP, and we get called out for trouble calls about packet loss. We use the command -t to send a continuous ping so it can gather a larger pool of data. It's quite simple if you are sending 100 and get back 90, you have a 10% packet loss. Trace Routes are a little different than ping tests. A traceroute gives you the path that your packet is traveling. When you have this data, you can see where there is any drop-off and where it was when this happened. This is crucial for troubleshooting internet issues because sometimes someone's problem may not be directly at the location. For example, if you look at the traceroute to australia.gov.au you can see we start to see no response after it leaves Comcast's backbone. They each take a different path to their end destination, but they all leave from the same spot, which travels through your ISP's head end and backbone. As far as when they make a return with no response, the Ping test will do that if the packet was unable to be delivered and there was no response. As mentioned above, this is known as packet loss. During a traceroute, just like the ping test, if no response is given, it will result in no information. This is also known as packet loss. It will skip over and go to the next hop.
Comments
Post a Comment