Here's some random geeky amusement for the day...
I was working on deneb (my server at home, 15 miles away), when I noticed that for some odd reason the latency went up to something like 2 seconds (for you non-geeks, latency is the time it takes for a computer to respond to something that's sent over the network). So I did a traceroute to figure out what was going on...
Tracing route to deneb.condordes.net [63.194.109.9]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms slo-wilma-vlan51.netadm.calpoly.edu [129.65.51.250]
2 <1 ms <1 ms <1 ms slo-ramoth-bezar.netadm.calpoly.edu [129.65.9.17]
3 <1 ms <1 ms <1 ms ramoth--gsr-4cnet.netadm.calpoly.edu [129.65.1.1]
4 5 ms 5 ms 5 ms dc-lax-dc1--slo-dc2-pos.cenic.net [137.164.22.24]
5 5 ms 5 ms 5 ms inet-lax-isp--dc-lax-dc1-ge--1.cenic.net [137.164.22.9]
6 4 ms 4 ms 4 ms ge-5-2-520.ipcolo1.LosAngeles1.Level3.net [64.156.191.9]
7 4 ms 5 ms 5 ms unknown.Level3.net [209.244.10.129]
8 6 ms 5 ms 9 ms so-5-3-0.bbr1.LosAngeles1.Level3.net [209.247.9.149]
9 67 ms 67 ms 66 ms so-0-0-0.bbr2.Washington1.Level3.net [64.159.1.158]
10 141 ms 140 ms 141 ms so-0-0-0.mp2.london2.level3.net [212.187.128.133]
11 156 ms 155 ms 155 ms so-6-0-0.mp1.Frankfurt1.Level3.net [212.187.128.62]
12 156 ms 156 ms 155 ms ge-10-2.ipcolo2.Frankfurt1.Level3.net [195.122.136.100]
13 953 ms 957 ms * 62.67.38.186
14 973 ms * * so-1-2-0.2488M.kd4nxu1.ip.tele.dk [195.249.14.6]
15 * * 1050 ms pos3-1.622M.newyork2nxg1.ip.tele.dk [195.249.6.134]
16 * * * Request timed out.
17 * * 959 ms bb1-p4-0.nycmny.sbcglobal.net [151.164.189.61]
18 963 ms * * core1-p6-0.crnyny.sbcglobal.net [151.164.188.90]
19 * * * Request timed out.
20 * * * Request timed out.
21 * 1044 ms 997 ms core2-p3-0.cratga.sbcglobal.net [151.164.241.94]
22 * 948 ms 909 ms core1-p1-0.cratga.sbcglobal.net [151.164.241.81]
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * 494 ms 721 ms bb2-p3-1.snloca.sbcglobal.net [151.164.189.6]
29 765 ms * 41 ms adsl-63-194-109-9.dsl.snlo01.pacbell.net [63.194.109.9]
Trace complete.
I guess someone over at Sprint rebooted a router, because packets were going from here (on campus), to LA, to Washington, to London, to Frankfurt and then to Denmark before finally coming back over here (looks like through New York and Georgia).
So packets that were destined for a computer 15 miles away ended up having to travel around the entire world. I find that highly amusing.
Normally, the traceroute looks like this:
Tracing route to deneb.condordes.net [63.194.109.9]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms slo-wilma-vlan51.netadm.calpoly.edu [129.65.51.250]
2 <1 ms <1 ms <1 ms slo-ramoth-bezar.netadm.calpoly.edu [129.65.9.17]
3 <1 ms <1 ms <1 ms ramoth--gsr-4cnet.netadm.calpoly.edu [129.65.1.1]
4 4 ms 4 ms 5 ms dc-lax-dc1--slo-dc2-pos.cenic.net [137.164.22.24]
5 4 ms 5 ms 5 ms inet-lax-isp--dc-lax-dc1-ge--1.cenic.net [137.164.22.9]
6 6 ms 6 ms 6 ms ge-5-2-520.ipcolo1.LosAngeles1.Level3.net [64.156.191.9]
7 6 ms 6 ms 5 ms unknown.Level3.net [209.244.10.133]
8 5 ms 5 ms 5 ms sprint-level3-oc48.LosAngeles1.Level3.net [64.152.193.74]
9 7 ms 8 ms 7 ms sl-bb24-ana-9-0.sprintlink.net [144.232.20.68]
10 10 ms 10 ms 7 ms sl-gw28-ana-1-0.sprintlink.net [144.232.1.50]
11 15 ms 13 ms 13 ms sl-swb-64-0.sprintlink.net [144.228.75.162]
12 13 ms 13 ms 13 ms bb1-p5-0.lsan03.pbi.net [151.164.241.17]
13 23 ms 24 ms 23 ms 151.164.189.154
14 29 ms 30 ms 29 ms dist1-vlan40.snlo01.pbi.net [216.102.182.21]
15 23 ms 23 ms 23 ms rback1-fa2-0.snlo01.pbi.net [216.102.182.70]
16 39 ms 39 ms 40 ms adsl-63-194-109-9.dsl.snlo01.pacbell.net [63.194.109.9]
Trace complete.
...and that leads me to believe that it was Sprint's fault. Everything's happy now, though, so I'm not complaining. I'm just highly amused.
-- Des
14:22:32 up 51 days, 18:22, 10 users, load average: 0.00, 0.00, 0.00
amused
