SUMMARY: Problem with traceroute under 5.1A?

From: Chris Adams <cmadams_at_hiwaay.net>
Date: Thu, 28 Feb 2002 12:13:29 -0600

I had a couple of suggestions to check /etc/routes and /etc/resolv.conf,
but this isn't a configuration problem (if there was a problem in either
of those I wouldn't have been able to resolve the name or trace by IP).

Richard Fairfield <rcf_at_ms.washington.edu> discovered the same problem
just yesterday. He reported it to Compaq and they have reproduced it on
5.1A both with and without PK1, and are escalating it to engineering.

-- 
Chris Adams <cmadams_at_hiwaay.net>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
Once upon a time, Chris Adams <cmadams_at_hiwaay.net> said:
> I had several people suggest a firewall or routing problem, but that
> isn't the case.  This box isn't behind a firewall, and it is reaching
> the Internet just fine (it is the primary DNS server for ~4000 zones and
> they are all fine).  This is a bug in traceroute.
> 
> Interestingly, I can traceroute via IP, just not name, even though
> traceroute is properly looking up the name (the first line of traceroute
> output shows that it resolved the name just fine):
> 
> $ traceroute 64.58.76.178
> traceroute to www9.dcx.yahoo.com (64.58.76.178): 1-30 hops, 38 byte packets
>  1  servers.hsvcore.hiwaay.net (208.147.154.33)  167 ms  231 ms  0.0 ms
>  2  500.Serial2-6.GW6.ATL5.ALTER.NET (65.208.82.61)  6.83 ms  9.76 ms  5.85 ms
>  3  178.at-6-0-0.XR2.ATL5.ALTER.NET (152.63.82.178)  6.83 ms (ttl=252!)  6.83 ms (ttl=252!)  5.85 ms (ttl=252!)
>  4  0.so-1-0-0.XL2.ATL5.ALTER.NET (152.63.85.193)  8.79 ms  6.83 ms  7.81 ms
>  5  0.so-1-2-0.TL2.ATL5.ALTER.NET (152.63.146.2)  6.83 ms  6.83 ms  6.83 ms
>  6  0.so-6-0-0.TL2.CHI2.ALTER.NET (152.63.13.22)  24.4 ms  22.4 ms  22.4 ms
>  7  0.so-1-0-0.XL2.CHI2.ALTER.NET (152.63.67.122)  22.4 ms  23.4 ms  22.4 ms
>  8  POS7-0.GW7.CHI2.ALTER.NET (152.63.67.185)  20.5 ms  22.4 ms  21.4 ms
>  9  exodus-OC12-CHI2.customer.alter.net (157.130.114.114)  28.3 ms (ttl=250!)  28.3 ms (ttl=250!)  32.2 ms (ttl=250!)
> 10  bbr01-g3-0.okbr01.exodus.net (216.34.183.65)  27.3 ms (ttl=249!)  27.3 ms (ttl=249!)  29.2 ms (ttl=249!)
> 11  bbr01-p2-0.whkn01.exodus.net (206.79.9.134)  39.0 ms (ttl=248!)  39.0 ms (ttl=248!)  39.0 ms (ttl=248!)
> 12  bbr02-g5-0.whkn01.exodus.net (216.35.65.84)  38.0 ms (ttl=248!)  39.0 ms (ttl=248!)  39.0 ms (ttl=248!)
> 13  bbr01-p1-0.nycm01.exodus.net (206.79.9.117)  41.9 ms (ttl=248!)  44.9 ms (ttl=248!)  41.9 ms (ttl=248!)
> 14  bbr01-p0-0.stng01.exodus.net (206.79.9.102)  42.9 ms (ttl=249!)  45.9 ms (ttl=249!)  43.9 ms (ttl=249!)
> 15  dcr03-g10-0.stng01.exodus.net (216.33.96.161)  45.8 ms (ttl=249!)  43.9 ms (ttl=249!)  41.9 ms (ttl=249!)
> 16  csr22-ve241.stng01.exodus.net (216.33.98.19)  42.9 ms (ttl=57!)  42.9 ms (ttl=57!)  43.9 ms (ttl=57!)
> 17  216.35.210.126 (216.35.210.126)  44.9 ms (ttl=247!)  42.9 ms (ttl=247!)  42.9 ms (ttl=247!)
> 18  www9.dcx.yahoo.com (64.58.76.178)  43.9 ms (ttl=246!)  44.9 ms (ttl=246!)  48.8 ms (ttl=246!)
> $ 
> 
> -- 
> Chris Adams <cmadams_at_hiwaay.net>
> Systems and Network Administrator - HiWAAY Internet Services
> I don't speak for anybody but myself - that's enough trouble.
> 
> Original message:
> 
> I just upgraded one system here from 4.0F to 5.1A (did a clean install).
> I just noticed that traceroute no longer works.  For example, I get:
> 
> $ traceroute www.yahoo.com
> traceroute to www.yahoo.akadns.net (64.58.76.178): 1-30 hops, 38 byte packets
>  1  servers.hsvcore.hiwaay.net (208.147.154.33)  0.976 ms * *
>  2  * * *
>  3  * * *
> <and so on>
> 
> When I do the same on another 4.0F system sitting right beside the 5.1A
> system (and on the same network), I get:
> 
> $ traceroute www.yahoo.com
> traceroute to www.yahoo.akadns.net (64.58.76.177), 30 hops max, 40 byte packets
>  1  servers.hsvcore.hiwaay.net (208.147.154.33)  2 ms  3 ms  1 ms
>  2  500.Serial2-6.GW6.ATL5.ALTER.NET (65.208.82.61)  18 ms  13 ms  36 ms
>  3  178.at-5-1-0.XR1.ATL5.ALTER.NET (152.63.82.182)  11 ms  17 ms  8 ms
>  4  0.so-1-0-0.XL1.ATL5.ALTER.NET (152.63.85.189)  16 ms  21 ms  12 ms
>  5  0.so-1-0-0.TL1.ATL5.ALTER.NET (152.63.85.217)  7 ms  10 ms  7 ms
>  6  0.so-1-3-0.TL1.CHI2.ALTER.NET (152.63.13.42)  23 ms  23 ms  22 ms
>  7  0.so-1-0-0.XL1.CHI2.ALTER.NET (152.63.67.106)  22 ms  22 ms  22 ms
>  8  POS6-0.GW7.CHI2.ALTER.NET (152.63.67.189)  22 ms  22 ms  21 ms
>  9  exodus-OC12-CHI2.customer.alter.net (157.130.114.114)  28 ms  28 ms  26 ms
> 10  bbr01-g3-0.okbr01.exodus.net (216.34.183.65)  28 ms  29 ms  27 ms
> 11  bbr01-p2-0.whkn01.exodus.net (206.79.9.134)  43 ms  42 ms  40 ms
> 12  216.74.171.18 (216.74.171.18)  41 ms  42 ms  41 ms
> 13  bbr01-p1-0.nycm01.exodus.net (206.79.9.117)  50 ms  44 ms  44 ms
> 14  bbr01-p0-0.stng01.exodus.net (206.79.9.102)  62 ms  45 ms  54 ms
> 15  dcr04-g9-0.stng01.exodus.net (216.33.96.146)  48 ms  50 ms  66 ms
> 16  csr22-ve241.stng01.exodus.net (216.33.98.19)  58 ms  44 ms  43 ms
> 17  216.35.210.126 (216.35.210.126)  77 ms  123 ms  310 ms
> 18  www8.dcx.yahoo.com (64.58.76.177)  52 ms  47 ms  45 ms
> $ 
> 
> Has anyone else seen this or know of a solution?

Received on Thu Feb 28 2002 - 18:13:47 NZDT