On Thu, 28 Feb 2013 11:06:35 -0800, John R Pierce wrote:
thats a rather high hop count to get that far.
Assuming you're in Santa Cruz, I'm not more than 20 miles from you, but, I'm using a mountain WISP (with radio relays on all the hilltops), so that's likely why I have many more hops than you do.
Here is my traceroute with a bit more detail (my local stuff is redacted, for privacy).
$ date Thu Feb 28 12:54:47 PST 2013
$ traceroute www.centos.org traceroute to www.centos.org (72.232.194.162), 30 hops max, 60 byte packets 1 router (192.168.1.1) 27.845 ms 27.807 ms 27.787 ms 2 REDACTED STATIC IP ADDRESS 27.766 ms 27.745 ms 27.725 ms 3 10.10.0.1 (10.10.0.1) 45.639 ms 51.532 ms 51.523 ms 4 10.52.0.1 (10.52.0.1) 51.505 ms 53.765 ms 53.759 ms 5 10.30.0.1 (10.30.0.1) 59.289 ms 62.681 ms 62.672 ms 6 10.0.0.1 (10.0.0.1) 65.632 ms 114.790 ms 124.655 ms 7 REDACTED WISP 127.280 ms 127.282 ms 127.266 ms 8 REDACTED WISP backbone 127.247 ms 121.642 ms 48.416 ms 9 REDACTED WISP backbone 51.977 ms 55.483 ms 55.473 ms 10 REDACTED WISP backbone 64.521 ms 67.369 ms 67.352 ms 11 xe-9-0-0.edge1.SanJose3.Level3.net (4.68.110.49) 64.463 ms 67.261 ms xe-11-1-0.edge1.SanJose3.Level3.net (4.68.111.189) 69.552 ms 12 vlan60.csw1.SanJose1.Level3.net (4.69.152.62) 88.431 ms vlan70.csw2.SanJose1.Level3.net (4.69.152.126) 91.063 ms vlan90.csw4.SanJose1.Level3.net (4.69.152.254) 90.976 ms 13 ae-62-62.ebr2.SanJose1.Level3.net (4.69.153.17) 96.160 ms ae-61-61.ebr1.SanJose1.Level3.net (4.69.153.1) 90.955 ms ae-82-82.ebr2.SanJose1.Level3.net (4.69.153.25) 90.896 ms 14 ae-5-5.ebr1.SanJose5.Level3.net (4.69.148.137) 76.111 ms ae-2-2.ebr2.SanJose5.Level3.net (4.69.148.141) 89.501 ms ae-5-5.ebr1.SanJose5.Level3.net (4.69.148.137) 76.081 ms 15 ae-6-6.ebr2.LosAngeles1.Level3.net (4.69.148.201) 76.597 ms 76.026 ms 82.326 ms 16 ae-3-3.ebr3.Dallas1.Level3.net (4.69.132.78) 82.317 ms ae-6-6.ebr2.LosAngeles1.Level3.net (4.69.148.201) 95.557 ms ae-3-3.ebr3.Dallas1.Level3.net (4.69.132.78) 95.517 ms 17 ae-3-3.ebr3.Dallas1.Level3.net (4.69.132.78) 95.466 ms 97.991 ms 95.449 ms 18 ae-83-83.csw3.Dallas1.Level3.net (4.69.151.157) 97.945 ms ae-1-60.edge3.Dallas1.Level3.net (4.69.145.8) 97.927 ms ae-93-93.csw4.Dallas1.Level3.net (4.69.151.169) 95.342 ms 19 ae-4-90.edge3.Dallas1.Level3.net (4.69.145.200) 97.833 ms LAYERED-TEC.edge3.Dallas1.Level3.net (4.71.170.6) 97.845 ms ae-3-80.edge3.Dallas1.Level3.net (4.69.145.136) 62.875 ms 20 LAYERED-TEC.edge3.Dallas1.Level3.net (4.71.170.6) 77.207 ms 77.174 ms * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *
What I now know (that I had not known prior), is that the hop you see at 20 is the penultimate hop.
So either hop 20 is not forwarding the packets, or the final destination is not acknowledging them.
Someone suggested I might be on a blacklist, somehow, and that, at least, would make technical sense.