A computer wants to send a packet to a certain location. A packet is first sent to a DNS server to look up the IP address. A packet contains all kinds of information like an address for a destination computer, different types of data and its sizes. Packets travel over communication links like cable wires, fiber optic cables, and wireless satellite communications. Packets travel through other computers, on its way to its destination. If routes are congested, packets may take different routes to get to a location.
For my ping to Google, I added a counter to 4 in my ping results, which shows that 4 packets were sent out and 4 were received. Pinging Google shows me the average time it took to communicate with the domain, which was 16.670 ms.
The trace route for Google showed me the routes it took to get to that domain. It looks like the packets went through a few frontier routers before getting to the final location.
With the ping to the Australian website, Australian Broadcasting News (ABC), I added a counter of 8 and the request timed out every time. 8 packets were sent out with 0 packets received. 100% of the packets sent out were lost. This could be caused by traffic or the routes that the packets took. Perhaps another server was down and the packets couldn’t communicate. When doing a trace route, I can see that the packets never reach the domain destination.
Pinging another Australian news website, there were 8 packets sent out and 8 were received. The average time it took for the packets to reach their destination was 77.003 ms. When running a trace, I can see the routes it took to reach the location.
I did notice that it takes a bit longer for packets to be received when the destination is in a foreign country than it does using a domain that is in the US. A ping of Google was done in 16 ms, whereas a Ping to the Australian news website was 77 ms.
Comments
Post a Comment