Traceroute not working in 9.3
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......
On Tuesday 31 May 2005 4:32 pm, 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......
Works fine here, more than likely, the packets are being dropped upstream from you. Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-20a-default x86_64
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......
--- melissad <melissad@speakeasy.net> wrote:
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.
Nope, still ain't working. :( I tried to trace to Earthlink's DNS here: amd64:~ # traceroute 207.69.188.185 traceroute to 207.69.188.185 (207.69.188.185), 30 hops max, 40 byte packets 1 192.168.1.1 0.423 ms 0.461 ms 0.393 ms 2 * * * 3 * * * 4 * * * Curiouser and curiouser. It doesn't seem to want to go past the router (Linksys BEFW11S4). I have a W2K box connected that tracert's fine. This also worked fine in 9.2. mtr works okay but it's overkill. Maybe my system's getting confused and trying to use IPv6? Weird.
participants (3)
-
jerry bookter -
melissad -
Scott Leighton