Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: Routing strangeness, New Tunnel page recommending the wrong server  (Read 2116 times)

RobinDaugherty

  • Newbie
  • *
  • Posts: 2

I'm located in Cincinnati, and my ISP (Insight Broadband) has told me that their main POP is in Atlanta.

I have a tunnel with the Chicago server, which had some trouble last week. So out of curiosity, I went to the "Setup Regular IPv6 Tunnel" page to see which server it would recommend. It recommends Miami.

So I pinged the two of them to verify a difference in speed, and found the following:

To get to the Chicago TunnelBroker server, goes to HE in Atlanta, and then goes through Ashburn and New York.
Code: [Select]
traceroute to 209.51.181.2 (209.51.181.2), 64 hops max, 52 byte packets
 1  192.168.240.1 (192.168.240.1)  0.732 ms  0.369 ms  0.413 ms
 2  192.168.241.1 (192.168.241.1)  1.491 ms  8.104 ms  1.029 ms
 3  10.117.176.1 (10.117.176.1)  17.497 ms  30.098 ms  19.939 ms
 4  74-128-19-189.dhcp.insightbb.com (74.128.19.189)  10.938 ms  16.620 ms  11.490 ms
 5  74-128-19-33.dhcp.insightbb.com (74.128.19.33)  21.893 ms  18.195 ms  35.192 ms
 6  74.128.9.233 (74.128.9.233)  18.940 ms  27.537 ms  12.447 ms
 7  xe-9-3-0.edge4.atlanta2.level3.net (4.59.12.61)  42.459 ms  34.460 ms  86.929 ms
 8  ae-17-51.car1.atlanta4.level3.net (4.68.103.12)  45.968 ms  34.053 ms  48.985 ms
 9  atl-bb1-link.telia.net (213.248.68.53)  39.986 ms  79.611 ms  54.710 ms
10  hurricane-ic-138358-atl-bb1.c.telia.net (213.248.71.66)  48.416 ms  55.002 ms  43.195 ms
11  10gigabitethernet6-4.core1.ash1.he.net (72.52.92.157)  62.684 ms  46.016 ms  51.191 ms
12  10gigabitethernet1-2.core1.nyc4.he.net (72.52.92.85)  61.941 ms  58.537 ms  47.695 ms
13  10gigabitethernet1-2.core1.chi1.he.net (72.52.92.102)  77.155 ms  48.493 ms  49.434 ms
14  tserv9.chi1.ipv6.he.net (209.51.181.2)  64.200 ms  125.806 ms  62.148 ms

To the Miami TunnelBroker server, goes to Chicago, and then gets handed to HE in Ashburn, then goes through Atlanta:
Code: [Select]
traceroute to 209.51.161.58 (209.51.161.58), 64 hops max, 52 byte packets
 1  192.168.240.1 (192.168.240.1)  0.855 ms  0.572 ms  0.414 ms
 2  192.168.241.1 (192.168.241.1)  1.532 ms  1.112 ms  8.245 ms
 3  10.117.176.1 (10.117.176.1)  17.498 ms  8.593 ms  12.989 ms
 4  74-128-19-189.dhcp.insightbb.com (74.128.19.189)  17.973 ms  9.189 ms  8.930 ms
 5  74-128-16-129.dhcp.insightbb.com (74.128.16.129)  13.722 ms  20.198 ms  22.005 ms
 6  74.128.8.241 (74.128.8.241)  20.468 ms  24.978 ms  18.439 ms
 7  4.71.250.29 (4.71.250.29)  21.973 ms  20.689 ms  37.486 ms
 8  vlan52.ebr2.chicago2.level3.net (4.69.138.190)  32.689 ms  38.481 ms  28.438 ms
 9  ae-5-5.ebr2.chicago1.level3.net (4.69.140.193)  27.769 ms  31.253 ms  36.206 ms
10  ae-23-52.car3.chicago1.level3.net (4.68.101.39)  23.745 ms  39.508 ms
    ae-13-55.car3.chicago1.level3.net (4.68.101.135)  33.687 ms
11  4.68.127.138 (4.68.127.138)  22.679 ms  29.984 ms  22.201 ms
12  nyk-bb1-link.telia.net (80.91.248.193)  55.441 ms  45.715 ms
    nyk-bb1-link.telia.net (80.91.246.167)  46.166 ms
13  ash-bb1-link.telia.net (80.91.245.110)  64.482 ms
    ash-bb1-link.telia.net (80.91.248.200)  50.965 ms  58.260 ms
14  hurricane-ic-138360-ash-bb1.c.telia.net (213.248.67.118)  54.697 ms  47.949 ms  61.681 ms
15  10gigabitethernet1-2.core1.atl1.he.net (72.52.92.158)  76.172 ms  62.727 ms  65.931 ms
16  10gigabitethernet3-2.core1.mia1.he.net (72.52.92.41)  72.662 ms  83.235 ms  71.921 ms
17  tserv12.mia1.ipv6.he.net (209.51.161.58)  80.181 ms  79.232 ms  90.174 ms

When I use the Looking Glass site to traceroute to my address, it goes directly to Insight in Chicago:
Code: [Select]
core1.chi1.he.net> traceroute 74.143.27.78 numeric
Hop Packet 1 Packet 2 Packet 3 Hostname
1 <1 ms <1 ms <1 ms chi-bb1-link.telia.net (213.248.104.213)
2 <1 ms <1 ms <1 ms te-8-4.car3.Chicago1.Level3.net (4.68.127.137)
3 6 ms <1 ms <1 ms ae-31-51.ebr1.Chicago1.Level3.net (4.68.101.30)
4 1 ms <1 ms 1 ms ae-6-6.ebr1.Chicago2.Level3.net (4.69.140.190)
5 <1 ms <1 ms <1 ms ae-1-51.edge2.Chicago2.Level3.net (4.69.138.131)
6 15 ms 9 ms 9 ms 4.71.250.2
7 12 ms 11 ms 10 ms 74.128.8.234
8 38 ms 37 ms 37 ms 74-128-16-130.dhcp.insightbb.com (74.128.16.130)
9 38 ms 39 ms 38 ms 74-128-19-190.dhcp.insightbb.com (74.128.19.190)
10 47 ms 48 ms 57 ms 74-143-27-78.static.insightbb.com (74.143.27.78)

And from Looking Glass' Miami server, it goes through Atlanta and Chicago to get to me.
Code: [Select]
core1.mia1.he.net> traceroute 74.143.27.78 numeric
Hop Packet 1 Packet 2 Packet 3 Hostname
1 <1 ms <1 ms <1 ms mai-b1-link.telia.net (213.248.83.193)
2 <1 ms <1 ms <1 ms level3-ic-132828-mai-b1.c.telia.net (213.248.73.22)
3 12 ms <1 ms <1 ms ae-32-52.ebr2.Miami1.Level3.net (4.69.138.126)
4 29 ms 18 ms 17 ms ae-2-2.ebr2.Atlanta2.Level3.net (4.69.140.142)
5 45 ms 53 ms 54 ms ae-3-3.ebr2.Chicago1.Level3.net (4.69.132.73)
6 45 ms 45 ms 45 ms ae-5-5.ebr2.Chicago2.Level3.net (4.69.140.194)
7 45 ms 45 ms 45 ms ae-2-52.edge2.Chicago2.Level3.net (4.69.138.163)
8 55 ms 54 ms 54 ms 4.71.250.30
9 56 ms 56 ms 55 ms 74.128.8.234
10 59 ms 58 ms 58 ms 74-128-16-130.dhcp.insightbb.com (74.128.16.130)
11 39 ms 39 ms 41 ms 74-128-19-190.dhcp.insightbb.com (74.128.19.190)
12 50 ms 55 ms 58 ms 74-143-27-78.static.insightbb.com (74.143.27.78)

Can anyone at HE tell me what I can do about that routing? Should I contact the ISP?

The weirdness of the routing aside, it doesn't seem to make sense that the TunnelBroker site would be recommending Miami to me.
Logged