Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: Odd Routing with Miami Tunnel Server  (Read 4335 times)

radicand

  • Newbie
  • *
  • Posts: 2
Odd Routing with Miami Tunnel Server
« on: June 12, 2008, 07:11:39 AM »

Hi there,

I saw the earlier post asking for a list of tunnel IPs, so I decided to ping a few to see if it was worthwhile to switch away from the NYC tunnel.  I live in Miami, so I was pleased to see a Miami one in the list, but its ping was twice that of the NYC tunnel.  Traceroute claims it's traveling through NYC then back down to FL.  I don't know if this is intended, but it seemed odd enough to bring up (as I'd imagine there should be relatively few hops if I'm in the same city).

traceroute to 209.51.161.58 (209.51.161.58), 30 hops max, 40 byte packets
 1  DD-WRT (192.168.1.252)  0.599 ms  1.586 ms  1.824 ms
 2  65.14.252.26 (65.14.252.26)  10.173 ms  13.120 ms  15.534 ms
 3  65.14.255.13 (65.14.255.13)  18.012 ms 70.151.249.5 (70.151.249.5)  20.795 ms 65.14.255.13 (65.14.255.13)  22.923 ms
 4  axr01mia-ge-2-1-4.bellsouth.net (65.83.237.36)  25.896 ms  37.706 ms  37.932 ms
 5  65.83.238.29 (65.83.238.29)  35.493 ms  36.947 ms  39.905 ms
 6  AXR01BCT-1-0-0.bellsouth.net (65.83.236.55)  42.632 ms  37.201 ms  40.368 ms
 7  65.83.238.64 (65.83.238.64)  58.463 ms  56.867 ms  58.182 ms
 8  pxr00chi-so-1-1-0.bellsouth.net (65.83.236.204)  124.911 ms  65.485 ms  54.553 ms
 9  gige-g2-8.core1.chi1.he.net (64.71.168.185)  50.644 ms  53.311 ms  55.327 ms
10  10gigabitethernet2-4.core1.nyc4.he.net (72.52.92.101)  79.893 ms  81.903 ms  84.328 ms
11  10gigabitethernet2-3.core1.ash1.he.net (72.52.92.86)  100.635 ms  101.419 ms  101.602 ms
12  10gigabitethernet1-1.core1.mia1.he.net (72.52.92.54)  128.903 ms  125.086 ms  127.741 ms
13  tserv12.mia1.ipv6.he.net (209.51.161.58)  130.435 ms  103.913 ms  104.629 ms
Logged

snarked

  • Hero Member
  • *****
  • Posts: 762
Re: Odd Routing with Miami Tunnel Server
« Reply #1 on: June 13, 2008, 11:11:39 AM »

Actually, it looks like Chicago is the farthest the path goes through.  Maybe HE can convince BellSouth to peer in Miami also....
Logged

avongauss

  • Newbie
  • *
  • Posts: 14
    • Home Page
Re: Odd Routing with Miami Tunnel Server
« Reply #2 on: June 13, 2008, 11:28:00 AM »

Similar routing is also seen from Comcast. 

traceroute to 209.51.161.58 (209.51.161.58), 30 hops max, 40 byte packets
 1  c-76-108-48-1.hsd1.fl.comcast.net (76.108.48.1)  9.267 ms  9.230 ms  9.080 ms
 2  ge-1-1-ur01.boynton.fl.pompano.comcast.net (68.85.230.145)  8.880 ms  8.808 ms  8.743 ms
 3  te-8-1-ur01.lakeworth.fl.pompano.comcast.net (68.86.165.174)  8.870 ms  9.312 ms  9.311 ms
 4  te-8-2-ur02.lakeworth.fl.pompano.comcast.net (68.86.165.178)  9.245 ms  9.180 ms  9.540 ms
 5  te-9-1-ur02.staterd7.fl.pompano.comcast.net (68.86.165.101)  9.605 ms  9.899 ms  9.868 ms
 6  te-9-4-ur01.staterd7.fl.pompano.comcast.net (68.86.165.93)  9.801 ms  17.683 ms  17.573 ms
 7  * * te-7-1-ar02.northdade.fl.pompano.comcast.net (68.86.91.82)  8.974 ms
 8  pos-0-7-0-0-cr01.miami.fl.ibone.comcast.net (68.86.85.194)  9.755 ms  9.983 ms  9.903 ms
 9  pos-0-11-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.85.193)  22.956 ms  25.558 ms  25.435 ms
10  TenGigabitethernet4-1.ar1.ATL2.gblx.net (146.82.35.121)  25.281 ms  25.273 ms  25.150 ms
11  HURRICANE-ELECTRIC-LLC-Ashburn.TenGigabitEthernet4-4.ar3.DCA3.gblx.net (64.214.121.170)  44.790 ms  41.514 ms  41.593 ms
12  10gigabitethernet1-1.core1.mia1.he.net (72.52.92.54)  66.595 ms  66.518 ms  66.439 ms
13  tserv12.mia1.ipv6.he.net (209.51.161.58)  66.432 ms  66.355 ms  66.653 ms
Logged