RE: another routing inefficiency anecdote

Stefan Savage (savage@cs.washington.edu)
Thu, 12 Nov 1998 09:08:29 -0800

The same thing used to routinely happen with Metricom. I'd watch the
packet go from Ed's radio to Metricom's local POP, then to SFO or
Austin, and back to Seattle. Basically, they didn't want to be in the
ISP business, they just wanted to be an ISP customer. It brings up a
whole new source of routing inefficiency:
"Too Lazy to Peer"

- Stefan

-----Original Message-----
From: Neal Cardwell [mailto:cardwell@cs.washington.edu]
Sent: Wednesday, November 11, 1998 7:03 PM
To: syn@cs
Subject: another routing inefficiency anecdote

When tracerouting to my roomie's new workplace -- Data Critical, over in
Redmond -- i noticed that packets are going from Seattle to Redmond via
San Francisco! Packets from both my US West DSL setup and UW go through
SF
to Data Critical. I'm guessing Data Critical must have an ISP
(netcom.net)
that's so small that it's forced to hook up down at Mae West rather than
up here somewhere.

68 saba:emacs >traceroute www.datacritical.com
traceroute to www.datacrit.com (206.216.111.160), 30 hops max, 40 byte
packets
1 hoover-V4.cac.washington.edu (128.95.4.100) 0.851 ms 0.766 ms
0.704
ms
2 uwbr2-FE0-1-0.cac.washington.edu (140.142.150.24) 0.807 ms 0.737
ms
0.666 ms
3 fe0-0.seatr1-gw.nw.verio.net (204.200.8.3) 1.805 ms 1.906 ms
1.678
ms
4 166.48.205.253 (166.48.205.253) 1.934 ms 2.072 ms 1.86 ms
5 core3.SanFrancisco.cw.net (204.70.4.17) 19.602 ms 43.01 ms 18.343
ms
6 mae-west-nap.SanFrancisco.cw.net (204.70.1.14) 20.305 ms 18.486 ms
19.228 ms
7 mae-west.netcom.net (198.32.136.15) 208.992 ms 150.544 ms 28.97
ms
8 h1-1-0-scl-ca-gw3.netcom.net (163.179.232.61) 27.783 ms 20.631 ms
25.257 ms
9 h0-0-stl-wa-gw1.netcom.net (163.179.232.53) 55.913 ms 57.9 ms
59.832 ms
10 stl-wa-gw7.netcom.net (165.236.128.37) 62.343 ms 64.102 ms 62.455
ms
11 206.216.111.1 (206.216.111.1) 64.291 ms 65.754 ms 103.712 ms
12 206.216.111.160 (206.216.111.160) 79.72 ms 97.883 ms 69.629 ms

[cardwell@fdsl115 cardwell]$ /usr/sbin/traceroute www.datacritical.com
traceroute to www.datacrit.com (206.216.111.160), 30 hops max, 40 byte
packets
1 209.180.204.254 (209.180.204.254) 18.436 ms 18.590 ms 18.884 ms
2 premiumD6 (207.224.255.6) 18.341 ms 18.610 ms 18.858 ms
3 206.81.192.218 (206.81.192.218) 19.856 ms 19.359 ms 19.531 ms
4 907.Hssi3-0-0.GW1.SEA1.ALTER.NET (137.39.136.61) 21.001 ms 22.583
ms
24.862 ms
5 103.ATM3-0.XR2.SEA1.ALTER.NET (146.188.200.38) 22.290 ms 20.490 ms
19.529 ms
6 194.ATM2-0.TR2.SEA1.ALTER.NET (146.188.200.114) 19.678 ms 24.602
ms
28.146 ms
7 110.ATM7-0.TR2.SCL1.ALTER.NET (146.188.137.189) 51.491 ms 54.415
ms
53.294 ms
8 198.ATM7-0.XR2.SJC1.ALTER.NET (146.188.146.53) 56.807 ms 55.714 ms
56.620 ms
9 192.ATM1-0-0.SAN-JOSE9-GW.ALTER.NET (146.188.144.133) 66.717 ms
57.043 ms 60.609 ms
10 * mae-west.netcom.net (198.32.136.15) 70.078 ms 67.616 ms
11 h1-1-0-scl-ca-gw3.netcom.net (163.179.232.61) 47.420 ms 47.048 ms
48.036 ms
12 h0-0-stl-wa-gw1.netcom.net (163.179.232.53) 89.882 ms 85.466 ms
171.269 ms
13 stl-wa-gw7.netcom.net (165.236.128.37) 83.918 ms 84.172 ms 87.108
ms
14 206.216.111.1 (206.216.111.1) 89.909 ms 90.895 ms 93.732 ms
15 206.216.111.160 (206.216.111.160) 95.827 ms 127.954 ms 92.403 ms