Some devices played ball, some responded but didn’t tell us their names, and others remained completely anonymous. The castle is in Cork, Ireland, but, according to IP address geolocation, the website is in London. Hop 11: We’ve arrived at the Blarney Castle website.Hops 9 and 10: Two more anonymous hops.It is a useful tool for troubleshooting and understanding connection issues. Hop 8: Again, we get an IP address but not the device name. Traceroute is a command-line tool that can be used in Windows, Linux, and other operating systems.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. This hop is within one of the largest ISPs in the U.K. This can happen when you encounter a “richly populated” network on which there’s a lot of hardware to handle high volumes of traffic. The (rather long) names and IP addresses for each device were printed. 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. 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. Perhaps it was configured never to send ICMP packets. This is how our UDP packets leave the local network and get on the internet.
0 Comments
Leave a Reply. |