![]() Hop 3: A device responded, but we didn't get its name, only the IP address.Or, perhaps it did respond but was too slow, so traceroute timed out. Hop 6: There's a lot of text here because a different remote device handled each of our three UDP requests.Note there's an asterisk in this line, which means we didn't get a response to all three requests. ![]() The (rather long) names and IP addresses for each device were printed. This can happen when you encounter a "richly populated" network on which there's a lot of hardware to handle high volumes of traffic. This hop is within one of the largest ISPs in the U.K. ![]() Hop 11: We've arrived at the Blarney Castle website.Hops 9 and 10: Two more anonymous hops.Hop 8: Again, we get an IP address but not the device name.Hop 7: This is the hop our UDP packets made as they left the ISPs network.So, it would be a minor miracle if the same piece of remote hardware handled our three connection requests. The castle is in Cork, Ireland, but, according to IP address geolocation, the website is in London.Sometimes the place to look for the most helpful traffic information is to the people who are out there driving the streets. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |