traceroute

[Corey Edwards]

On Wed, 2005-06-29 at 11:09 -0600, Von Fugal wrote:
> My connection at home (OCT) is really lame and slow as of late, tons of
> latency as well. So I did a traceroute, and these results seem really
> odd to me:
> 
> ~$ traceroute google.com
> traceroute: Warning: google.com has multiple addresses; using
> 216.239.39.99
> traceroute to google.com (216.239.39.99), 30 hops max, 38 byte packets
> 1  172.17.99.1 (172.17.99.1)  0.871 ms  0.885 ms  1.764 ms
> 2  67.137.24.193 (67.137.24.193)  1.745 ms  1.720 ms  1.263 ms
> 3  absu-raintree.octelecom.net (208.187.180.213)  800.194 ms  760.263 ms  747.098 ms
> 4  * 192.168.76.254 (192.168.76.254)  591.658 ms  723.829 ms
> 5  192.168.75.254 (192.168.75.254)  628.861 ms  719.860 ms  615.636 ms
> 6  192.168.101.254 (192.168.101.254)  695.693 ms  626.387 ms 640.457 ms
> 7  192.168.252.254 (192.168.252.254)  667.887 ms  657.647 ms 652.576 ms
> 8  192.168.243.5 (192.168.243.5)  698.662 ms  689.019 ms 655.560 ms
> 9  t3-2-2-1--0.gw02.slkc.eli.net (209.210.71.157)  712.306 ms 726.557 ms  654.175 ms
> 10  ge-3-1-0--0.cr01.slkc.eli.net (207.173.115.245)  624.812 ms 677.539 ms  590.150 ms
> 11  p10-0.cr01.rcrd.eli.net (207.173.114.9)  701.901 ms 650.000 ms  2641.865 ms
> 
> 4 - 8 are what baffle me... what's it routing through a private network
> for? And as you see, the latency is through the roof.

There's nothing odd about running through a private network. My company
does it all the time. For example, my T1 runs over a 192.168.0.x
network. That's because my office router and my gateway router need to
have a network for their serial devices. There's no point in wasting a
perfectly good /30 on a link when we're just routing a /28 on top of it.
So we used RFC1918 addresses instead. We also do the same thing for our
wireless devices which is the same thing only larger scale, and we
really don't want anybody mucking with the access points except us.

So I don't think your latency has anything to do with the RFC1918
addresses. I'm guessing absu-raintree sits on a IP-over-avian-carrier
link.

Corey

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://plug.org/pipermail/plug/attachments/20050629/d41bdcdb/attachment.bin