Currently I'm using Ashburn tserv. Curiosity prompted me to test the HE tunnel creation to see what tserv is recommended, and the result was Chicago. While I'm aware comcast itself is not going to peer with HE in the forseeable future, I'm curious about GBLX presence in the traceroutes shown below, the first to Chicago tserv, the latter Ashburn. If I read these traces correctly, could HE peer with GBLX in Chicago?
traceroute 209.51.181.2
traceroute to 209.51.181.2 (209.51.181.2), 30 hops max, 38 byte packets
1 * * *
2 ge-1-3-ur01.oakridge.tn.knox.comcast.net (68.85.207.65) 9.452 ms 9.366 ms 8.527 ms
3 te-9-1-ur02.sharpsridge.tn.knox.comcast.net (68.86.136.85) 9.782 ms 10.211 ms 9.755 ms
4 te-8-1-ur01.sharpsridge.tn.knox.comcast.net (68.86.136.78) 10.716 ms 8.939 ms 11.966 ms
5 te-8-1-ar01.sharpsridge.tn.knox.comcast.net (68.86.136.82) 9.809 ms 7.505 ms 9.792 ms
6 te-5-2-ar01.nashville.tn.nash.comcast.net (68.85.232.93) 16.270 ms 15.103 ms 16.560 ms
7 pos-0-7-0-0-cr01.chicago.il.ibone.comcast.net (68.86.90.73) 27.788 ms pos-0-6-0-0-cr01.chicago.il.ibone.comcast.net (68.86.90.69) 29.374 ms pos-0-7-0-0-cr01.chicago.il.ibone.comcast.net (68.86.90.73) 29.611 ms
8 TenGigabitEthernet2-2.ar5.CHI1.gblx.net (64.213.79.245) 30.077 ms 29.974 ms 28.598 ms
9 HURRICANE-ELECTRIC-LLC-Ashburn.TenGigabitEthernet4-4.ar3.DCA3.gb (64.214.121.170) 58.338 ms 65.583 ms 59.984 ms
10 10gigabitethernet1-2.core1.nyc4.he.net (72.52.92.85) 60.803 ms 60.060 ms 60.106 ms
11 10gigabitethernet1-2.core1.chi1.he.net (72.52.92.102) 66.325 ms 58.844 ms 64.752 ms
12 tserv9.chi1.ipv6.he.net (209.51.181.2) 59.965 ms 59.996 ms 60.561 ms
traceroute 216.66.22.2
traceroute to 216.66.22.2 (216.66.22.2), 30 hops max, 38 byte packets
1 * * *
2 ge-1-3-ur01.oakridge.tn.knox.comcast.net (68.85.207.65) 13.812 ms 15.848 ms 11.184 ms
3 te-9-1-ur02.sharpsridge.tn.knox.comcast.net (68.86.136.85) 14.907 ms 9.522 ms 9.777 ms
4 te-8-1-ur01.sharpsridge.tn.knox.comcast.net (68.86.136.78) 10.700 ms 9.193 ms 12.040 ms
5 te-8-1-ar01.sharpsridge.tn.knox.comcast.net (68.86.136.82) 8.811 ms 7.973 ms 9.400 ms
6 te-5-2-ar01.nashville.tn.nash.comcast.net (68.85.232.93) 110.448 ms 64.698 ms 27.507 ms
7 pos-0-7-0-0-cr01.chicago.il.ibone.comcast.net (68.86.90.73) 33.902 ms 33.441 ms pos-0-6-0-0-cr01.chicago.il.ibone.comcast.net (68.86.90.69) 28.709 ms
8 162.97.117.45 (162.97.117.45) 112.437 ms 84.903 ms 221.376 ms
9 HURRICANE-ELECTRIC-LLC-New-York.TenGigabitEthernet1-3.ar5.NYC1.g (64.209.92.98) 59.628 ms 55.872 ms 54.179 ms
10 10gigabitethernet2-3.core1.ash1.he.net (72.52.92.86) 66.713 ms 61.270 ms 60.013 ms
11 * * *
12 * * *
13 * * *
^C
Oh, and I'm guessing somethings in place at Ashburn, due to kiddies DoSing it, thats preventing traceroutes to go through.
Quote from: kriteknetworks on October 31, 2009, 11:16:06 AM
Currently I'm using Ashburn tserv. Curiosity prompted me to test the HE tunnel creation to see what tserv is recommended, and the result was Chicago. While I'm aware comcast itself is not going to peer with HE in the forseeable future, I'm curious about GBLX presence in the traceroutes shown below, the first to Chicago tserv, the latter Ashburn. If I read these traces correctly, could HE peer with GBLX in Chicago?
Global Crossing is one of HE's transit providers, not a peer and they do connect to Global Crossing in Chicago as well.
I see, so there's no way to eliminate hops to NY and Ashburn before Chicago?
Quote from: kriteknetworks on October 31, 2009, 01:32:19 PM
I see, so there's no way to eliminate hops to NY and Ashburn before Chicago?
HE would have to look into this. It is a good question though why traffic from Global Crossing in Chicago comes into HE's network via Ashburn instead of Chicago even though HE does have connectivity to Global Crossing in Chicago.