Jerry, If you are still able to connect to Yahoo.com on port 80, it isn't your traceroute that is broken. Traceroute is given lowest priority on many routers, such that the response times out. You are clearly getting beyond the first hop to the second, second to the third and so on up to 8. Also, traceroute, for the same low priority reasons, is not a reliable measure of delay/latency over the Internet access, distribution and core. YOu can evaluate a traceroute in your local network, perhaps even to your DNS servers if you are a SOHO or consumer. The core routers, however, only respond if they have the higher priority queues clear. melissa On Tue, 2005-05-31 at 16:32 -0700, jerry bookter wrote:
Hi Folks--
Traceroute (0.6.2) seems to be broken in 9.3:
traceroute yahoo.com traceroute to yahoo.com (216.109.112.135), 30 hops max, 40 byte packets 1 192.168.1.1 0.412 ms 0.409 ms 0.405 ms 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * ....etc.
Any ideas? TIA......