dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
2404
share rss forum feed

34764170

join:2007-09-06
Etobicoke, ON

2 edits
reply to spock

Re: IPv6 Vancouver

The comment was made regarding a specific issue as shown above regarding reaching Google; but it can vastly improve routing to many other networks. There is more than one issue at hand at the moment.

34764170

join:2007-09-06
Etobicoke, ON

2 edits
reply to martyb
said by martyb:

I won't argue that HE is well connected in the v6 world, however Peer1 is not so poorly connected that it must forward traffic to Europe. I would not assume however that HE == Best Route(tm) in all cases.

It's not so much about Peer 1 being so poorly connected although that is true to a certain extent; their transit and peering is very limited by comparison. Hurricane just has a hell of a lot more peering. They have thousands of peering sessions Peer 1 does not. I never claimed it would be the best route in all scenarios; but there is definitely room for improvement over the current setup with the single transit provider. The thousands of additional peering sessions result in additional routes that can provide a more direct and shorter path.

said by martyb:

I don't know how TSI has designed their network between Vancouver and Toronto, however my view would be that it would be better to peer IPv6 at TorIX with Google and forward traffic over TSI's backbone instead of handing it off to transit and letting the "best route" decide. I would hope they have better capacity and manageability on their backbone west-east.

There is no network between Vancouver and Toronto. They're two separate networks with different AS's. Peering with Google in Toronto and passing off traffic there would not be a very good route for traffic coming from Vancouver. It also doesn't make sense passing traffic coast to coast that can just go down through Seattle; much better performance and latency.

mactalla

join:2008-02-19
kudos:1
reply to martyb
said by martyb:

mactalla, what DNS servers are you using? Because you are resolving google somehow that is sending you over AMS-IX, the _amsterdam_ exchange....no wonder your latency is so damn high. Are you using open resolvers perhaps?

Good call. Here are some traces with a few DNS servers:

TSI (76.10.191.198)
$ traceroute6 ipv6.google.com
traceroute to ipv6.l.google.com (2607:f8b0:400e:c04::67) from 2607:c000:100:me::me, port 33434, from port 33714, 30 hops max, 60 bytes packets
 1  2607:c000:100:me::me (2607:c000:100:me::me)  0.418 ms  0.394 ms  0.366 ms 
 2  2607:c000:1::100 (2607:c000:1::100)  61.569 ms  11.449 ms  10.758 ms 
 3  2607:c000:1:1600::1 (2607:c000:1:1600::1)  9.576 ms  9.524 ms  9.127 ms 
 4  2001:1978:1100:1::1 (2001:1978:1100:1::1)  17.343 ms  9.228 ms  9.108 ms 
 5  2001:1978:2:5::51 (2001:1978:2:5::51)  9.751 ms  9.444 ms  10.837 ms 
 6  2001:1978:2:5::1 (2001:1978:2:5::1)  70.337 ms  69.765 ms  70.103 ms 
 7  2001:1978:2:5::5e (2001:1978:2:5::5e)  70.975 ms  70.218 ms  77.827 ms 
 8  2001:1978:2:5::d1 (2001:1978:2:5::d1)  82.544 ms  82.971 ms  81.644 ms 
 9  2001:1978:2:5::4e (2001:1978:2:5::4e)  164.237 ms  161.644 ms  161.819 ms 
10  2001:1978:2:5::85 (2001:1978:2:5::85)  88.568 ms  88.836 ms  86.712 ms 
11  core1.ams.net.google.com (2001:7f8:1::a501:5169:2)  182.808 ms  182.698 ms  182.333 ms 
12  2001:4860::1:0:8 (2001:4860::1:0:8)  182.762 ms  182.420 ms  182.061 ms 
13  2001:4860::8:0:519f (2001:4860::8:0:519f)  180.570 ms  180.370 ms  180.085 ms 
14  2001:4860::8:0:519f (2001:4860::8:0:519f)  192.034 ms  192.310 ms  192.169 ms 
15  2001:4860::8:0:3cd9 (2001:4860::8:0:3cd9)  175.906 ms  176.105 ms  176.625 ms 
16  2001:4860::8:0:2fe9 (2001:4860::8:0:2fe9)  166.660 ms  166.395 ms  166.126 ms 
17  2001:4860::8:0:281e (2001:4860::8:0:281e)  179.372 ms  178.702 ms  183.010 ms 
18  2001:4860::8:0:281e (2001:4860::8:0:281e)  186.578 ms  197.851 ms  188.025 ms 
19  2001:4860::8:0:252d (2001:4860::8:0:252d)  173.707 ms  171.694 ms  175.085 ms 
20  2001:4860::8:0:252d (2001:4860::8:0:252d)  178.796 ms  178.736 ms  178.876 ms 
21  2001:4860::2:0:ac (2001:4860::2:0:ac)  193.101 ms  210.150 ms  176.108 ms 
22  2001:4860::2:0:ac (2001:4860::2:0:ac)  210.214 ms  181.310 ms  181.337 ms 
23  pc-in-x67.1e100.net (2607:f8b0:400e:c04::67)  174.692 ms  174.405 ms  174.934 ms 
 

Google (8.8.8.8)
$ traceroute6 ipv6.google.com
traceroute to ipv6.l.google.com (2607:f8b0:400a:801::1011) from 2607:c000:100:me::me, port 33434, from port 33713, 30 hops max, 60 bytes packets
 1  2607:c000:100:me::me (2607:c000:100:me::me)  0.453 ms  0.423 ms  0.324 ms 
 2  2607:c000:1::100 (2607:c000:1::100)  10.604 ms  10.939 ms  10.370 ms 
 3  2607:c000:1:1600::1 (2607:c000:1:1600::1)  10.831 ms  9.562 ms  10.057 ms 
 4  2001:1978:1100:1::1 (2001:1978:1100:1::1)  34.068 ms  10.210 ms  9.946 ms 
 5  2001:1978:2:5::51 (2001:1978:2:5::51)  21.999 ms  10.696 ms  9.995 ms 
 6  2001:1978:2:5::1 (2001:1978:2:5::1)  70.246 ms  70.268 ms  70.174 ms 
 7  2001:1978:2:5::5e (2001:1978:2:5::5e)  70.640 ms  70.251 ms  71.324 ms 
 8  2001:1978:2:5::d1 (2001:1978:2:5::d1)  82.320 ms  81.646 ms  82.876 ms 
 9  2001:1978:2:5::4e (2001:1978:2:5::4e)  162.197 ms  162.072 ms  161.918 ms 
10  2001:1978:2:5::96 (2001:1978:2:5::96)  184.754 ms  184.793 ms  184.033 ms 
11  2001:1978:2:5::4a (2001:1978:2:5::4a)  189.865 ms  188.936 ms  189.544 ms 
12  2001:4860::1:0:8 (2001:4860::1:0:8)  182.030 ms  180.505 ms  179.726 ms 
13  2001:4860::8:0:51a0 (2001:4860::8:0:51a0)  172.768 ms  173.552 ms  173.230 ms 
14  2001:4860::8:0:2ddf (2001:4860::8:0:2ddf)  177.981 ms  177.774 ms  177.349 ms 
15  2001:4860::8:0:3cd9 (2001:4860::8:0:3cd9)  175.863 ms  176.200 ms  177.130 ms 
16  2001:4860::8:0:3cd9 (2001:4860::8:0:3cd9)  188.317 ms  188.779 ms  187.047 ms 
17  2001:4860::8:0:281d (2001:4860::8:0:281d)  188.832 ms  178.325 ms  240.236 ms 
18  2001:4860::8:0:281e (2001:4860::8:0:281e)  187.960 ms  190.291 ms  188.798 ms 
19  2001:4860::8:0:3427 (2001:4860::8:0:3427)  196.732 ms  197.228 ms  197.253 ms 
20  2001:4860::1:0:610 (2001:4860::1:0:610)  167.537 ms  168.072 ms  189.257 ms 
21  2001:4860::1:0:610 (2001:4860::1:0:610)  176.790 ms  176.153 ms  175.880 ms 
22  2001:4860:0:1::44c (2001:4860:0:1::44c)  177.828 ms  177.282 ms  177.032 ms 
23  2607:f8b0:400a:801::1d (2607:f8b0:400a:801::1d)  167.373 ms  167.344 ms  166.949 ms 
 

Google IPv6 DNS (2001:4860:4860::8888)
$ traceroute6 ipv6.google.com
traceroute to ipv6.l.google.com (2607:f8b0:400a:800::1010) from 2607:c000:100:me::me, port 33434, from port 33703, 30 hops max, 60 bytes packets
 1  2607:c000:100:me::me (2607:c000:100:me::me)  0.397 ms  0.380 ms  0.346 ms 
 2  2607:c000:1::100 (2607:c000:1::100)  11.524 ms  11.504 ms  12.379 ms 
 3  2607:c000:1:1600::1 (2607:c000:1:1600::1)  11.143 ms  9.667 ms  10.708 ms 
 4  2001:1978:1100:1::1 (2001:1978:1100:1::1)  9.784 ms  10.786 ms  8.754 ms 
 5  2001:1978:2:5::51 (2001:1978:2:5::51)  10.877 ms  8.838 ms  9.945 ms 
 6  2001:1978:2:5::1 (2001:1978:2:5::1)  70.179 ms  69.770 ms  69.465 ms 
 7  2001:1978:2:5::5e (2001:1978:2:5::5e)  70.116 ms  69.892 ms  69.767 ms 
 8  2001:1978:2:5::d1 (2001:1978:2:5::d1)  81.863 ms  83.998 ms  82.012 ms 
 9  2001:1978:2:5::4e (2001:1978:2:5::4e)  162.284 ms  162.214 ms  163.014 ms 
10  2001:1978:2:5::96 (2001:1978:2:5::96)  184.384 ms  185.390 ms  183.822 ms 
11  core1.ams.net.google.com (2001:7f8:1::a501:5169:2)  182.729 ms  180.943 ms  180.207 ms 
12  2001:4860::1:0:8 (2001:4860::1:0:8)  182.812 ms  182.895 ms  183.125 ms 
13  2001:4860::8:0:51a0 (2001:4860::8:0:51a0)  173.682 ms  173.507 ms  172.800 ms 
14  2001:4860::8:0:2ddf (2001:4860::8:0:2ddf)  178.550 ms  177.447 ms  228.749 ms 
15  2001:4860::8:0:2dde (2001:4860::8:0:2dde)  187.398 ms  186.715 ms  186.675 ms 
16  2001:4860::8:0:2fea (2001:4860::8:0:2fea)  169.031 ms  177.991 ms  168.879 ms 
17  2001:4860::8:0:281e (2001:4860::8:0:281e)  179.671 ms  180.201 ms  179.132 ms 
18  2001:4860::8:0:3426 (2001:4860::8:0:3426)  186.961 ms  189.905 ms  187.986 ms 
19  2001:4860::8:0:252d (2001:4860::8:0:252d)  167.776 ms  165.815 ms  166.011 ms 
20  2001:4860::8:0:252d (2001:4860::8:0:252d)  177.748 ms  174.654 ms  175.946 ms 
21  2001:4860:0:1::44a (2001:4860:0:1::44a)  169.469 ms  169.415 ms  171.179 ms 
22  2607:f8b0:400a:800::18 (2607:f8b0:400a:800::18)  165.778 ms  171.091 ms  169.284 ms 
 

OpenDNS (208.67.222.222)
$ traceroute6 ipv6.google.com
traceroute to ipv6.l.google.com (2607:f8b0:400a:801::1013) from 2607:c000:100:me::me, port 33434, from port 33697, 30 hops max, 60 bytes packets
 1  2607:c000:100:me::me (2607:c000:100:me::me)  0.461 ms  0.380 ms  0.336 ms 
 2  2607:c000:1::100 (2607:c000:1::100)  10.427 ms  10.489 ms  13.042 ms 
 3  2607:c000:1:1600::1 (2607:c000:1:1600::1)  9.187 ms  9.525 ms  19.993 ms 
 4  2001:1978:1100:1::1 (2001:1978:1100:1::1)  9.709 ms  10.027 ms  9.576 ms 
 5  2001:1978:2:5::51 (2001:1978:2:5::51)  10.421 ms  9.671 ms  9.015 ms 
 6  2001:1978:2:5::1 (2001:1978:2:5::1)  70.079 ms  69.766 ms  69.846 ms 
 7  2001:1978:2:5::5e (2001:1978:2:5::5e)  70.249 ms  70.246 ms  126.498 ms 
 8  2001:1978:2:5::6e (2001:1978:2:5::6e)  82.057 ms  81.289 ms  82.788 ms 
 9  2001:1978:2:5::4e (2001:1978:2:5::4e)  162.588 ms  162.287 ms  161.812 ms 
10  2001:1978:2:5::85 (2001:1978:2:5::85)  85.755 ms  85.074 ms  87.548 ms 
11  core1.ams.net.google.com (2001:7f8:1::a501:5169:2)  183.253 ms  182.300 ms  183.111 ms 
12  core1.ams.net.google.com (2001:7f8:1::a501:5169:2)  190.504 ms  191.068 ms  189.924 ms 
13  2001:4860::1:0:8 (2001:4860::1:0:8)  192.020 ms  192.244 ms  192.096 ms 
14  2001:4860::8:0:2ddf (2001:4860::8:0:2ddf)  178.054 ms  177.085 ms  176.731 ms 
15  2001:4860::8:0:2ddf (2001:4860::8:0:2ddf)  189.283 ms  189.152 ms  188.511 ms 
16  2001:4860::8:0:3cd9 (2001:4860::8:0:3cd9)  188.191 ms  187.044 ms  186.289 ms 
17  2001:4860::8:0:281e (2001:4860::8:0:281e)  182.103 ms  181.131 ms  180.074 ms 
18  2001:4860::8:0:281e (2001:4860::8:0:281e)  189.021 ms  188.737 ms  189.462 ms 
19  2001:4860::8:0:252d (2001:4860::8:0:252d)  166.123 ms  166.565 ms  181.378 ms 
20  2001:4860::1:0:610 (2001:4860::1:0:610)  167.966 ms  167.463 ms  168.616 ms 
21  2001:4860::1:0:610 (2001:4860::1:0:610)  179.329 ms  179.796 ms  178.819 ms 
22  2607:f8b0:400a:801::1d (2607:f8b0:400a:801::1d)  168.959 ms  166.845 ms  166.618 ms 
 

34764170

join:2007-09-06
Etobicoke, ON
reply to TSI Gabe
As shown below the path taken to get to a particular destination can vary by quite a bit and so does the latency. The lack of (enough) peering can result in some pretty poor paths.

Hurricane

1 13 ms 3 ms 3 ms 10gigabitethernet12-3.core1.sea1.he.net (2001:470:0:231::1)
2 15 ms 3 ms 3 ms google-as15169.gigabitethernet2-8.core1.sea1.he.net (2001:470:0:130::2)
3 53 ms 3 ms 20 ms 2001:4860::1:0:610
4 48 ms 4 ms 11 ms 2001:4860::8:0:252c
5 11 ms 11 ms 13 ms 2001:4860::8:0:467d
6 11 ms 13 ms 12 ms 2001:4860::2:0:ac
7 * * * ?
8 17 ms 12 ms 10 ms pc-in-x67.1e100.net (2607:f8b0:400e:c04::67)
 

Sprint

Tracing the route to pc-in-x67.1e100.net (2607:F8B0:400E:C04::67)
  1 sl-gw50-sea-xe-4-2-0.0.v6.sprintlink.net (2600:0:2:1239:144:232:3:124) 0 msec 0 msec 0 msec
  2 2001:4860:1:1:0:4D7:0:C 4 msec 0 msec 4 msec
  3 2001:4860::1:0:610 0 msec 0 msec 140 msec
  4 2001:4860::8:0:252C 0 msec 0 msec 0 msec
  5 2001:4860::8:0:467D 8 msec 8 msec
    2001:4860::8:0:2B60 8 msec
  6 2001:4860::2:0:AC 8 msec 8 msec 8 msec
  7  *  *  * 
  8 pc-in-x67.1e100.net (2607:F8B0:400E:C04::67) 8 msec 8 msec 4 msec
 

Level3

 1 vl-4040.edge2.SanJose1.Level3.net (2001:1900:4:1::4A) 16 msec 20 msec 16 msec
  2 vl-70.edge1.SanJose3.Level3.net (2001:1900:1A:6::11) 16 msec 16 msec
    vl-90.edge1.SanJose3.Level3.net (2001:1900:1A:8::11) 16 msec
  3 2001:4860:1:1:0:D1C:0:1 16 msec 20 msec 16 msec
  4 2001:4860::1:0:7EA 20 msec 20 msec
    2001:4860::1:0:21 16 msec
  5 2001:4860::8:0:2CB7 16 msec 80 msec 16 msec
  6 2001:4860::8:0:2BB6 36 msec 36 msec
    2001:4860::8:0:2BB7 32 msec
  7 2001:4860::8:0:467D 36 msec 36 msec 40 msec
  8 2001:4860::2:0:AC 36 msec 40 msec 36 msec
  9  *  *  *
 10 pc-in-x67.1e100.net (2607:F8B0:400E:C04::67) 36 msec 36 msec 36 msec
 

Telia

traceroute6 to 2607:f8b0:400e:c04::67 (2607:f8b0:400e:c04::67) from 2001:2000:3018:62::1, 64 hops max, 12 byte packets
 1  sjo-bb1-v6.telia.net (2001:2000:3018:15::1)  23.576 ms  19.864 ms  19.885 ms
 2  google-ic-133724-sjo-bb1.c.telia.net (2001:2000:3080:334::2)  21.712 ms  27.444 ms  22.011 ms
 3  2001:4860::1:0:7ea (2001:4860::1:0:7ea)  22.156 ms 2001:4860::1:0:21 (2001:4860::1:0:21)  65.021 ms  88.662 ms
 4  2001:4860::8:0:2cb7 (2001:4860::8:0:2cb7)  22.646 ms  24.325 ms  24.229 ms
 5  2001:4860::8:0:2bb6 (2001:4860::8:0:2bb6)  38.540 ms  35.990 ms 2001:4860::8:0:2bb7 (2001:4860::8:0:2bb7)  37.817 ms
 6  2001:4860::8:0:467d (2001:4860::8:0:467d)  48.077 ms 2001:4860::8:0:2b60 (2001:4860::8:0:2b60)  68.689 ms 2001:4860::8:0:467d (2001:4860::8:0:467d)  45.722 ms
 7  2001:4860::2:0:ac (2001:4860::2:0:ac)  39.115 ms  39.053 ms  40.608 ms
 

NTT

traceroute6 to 2607:f8b0:400e:c04::67 (2607:f8b0:400e:c04::67) from 2001:418:0:1000::4c, 64 hops max, 12 byte packets
 1  ae-0.r20.sttlwa01.us.bb.gin.ntt.net (2001:418:0:2000::e5)  0.384 ms  0.325 ms  0.271 ms
 2  ae-5.r21.snjsca04.us.bb.gin.ntt.net (2001:418:0:2000::112)  43.459 ms  26.152 ms  20.622 ms
 3  ae-2.r07.snjsca04.us.bb.gin.ntt.net (2001:418:0:2000::352)  20.188 ms  20.701 ms *
 4  eqixsjc-v6.google.com (2001:504:0:1:0:1:5169:1)  21.307 ms  38.812 ms  79.918 ms
 5  2001:4860::1:0:21 (2001:4860::1:0:21)  22.237 ms 2001:4860::1:0:7ea (2001:4860::1:0:7ea)  99.210 ms 2001:4860::1:0:21 (2001:4860::1:0:21)  64.371 ms
 6  2001:4860::8:0:2cb6 (2001:4860::8:0:2cb6)  22.530 ms  22.198 ms  21.790 ms
 7  2001:4860::8:0:2bb6 (2001:4860::8:0:2bb6)  37.754 ms  55.866 ms  63.509 ms
 8  2001:4860::8:0:467d (2001:4860::8:0:467d)  51.911 ms  41.883 ms  39.954 ms
 9  2001:4860::2:0:ac (2001:4860::2:0:ac)  40.486 ms  40.813 ms  55.288 ms
 

Inteliquent

traceroute6 to 2607:f8b0:400e:c04::67 (2607:f8b0:400e:c04::67) from 2001:668:0:1:213:200:87:20, 12 hops max, 12 byte packets
 1  xe-1-2-0.sjc10.ip6.tinet.net (2001:668:0:2::1:18a1)  54.005 ms xe-7-0-1.sjc10.ip6.tinet.net (2001:668:0:2::1:2731)  59.589 ms xe-5-0-0.sjc10.ip6.tinet.net (2001:668:0:2::1:15b1)  30.503 ms
 2  as15169.ip6.tinet.net (2001:668:0:3::8000:1422)  30.533 ms  38.406 ms  32.289 ms
 3  2001:4860::1:0:7ea (2001:4860::1:0:7ea)  52.157 ms  31.088 ms  35.101 ms
 4  2001:4860::8:0:2cb7 (2001:4860::8:0:2cb7)  40.946 ms 2001:4860::8:0:2cb6 (2001:4860::8:0:2cb6)  32.649 ms  32.722 ms
 5  2001:4860::8:0:2bb6 (2001:4860::8:0:2bb6)  47.900 ms 2001:4860::8:0:2bb7 (2001:4860::8:0:2bb7)  58.658 ms  48.021 ms
 6  2001:4860::8:0:467d (2001:4860::8:0:467d)  50.651 ms  50.750 ms  67.341 ms
 7  2001:4860::2:0:ac (2001:4860::2:0:ac)  50.404 ms  50.342 ms  80.850 ms
 8  * * *
 9  pc-in-x67.1e100.net (2607:f8b0:400e:c04::67)  49.586 ms  50.066 ms  49.361 ms
 

Cogent

traceroute to 2607:f8b0:400e:c04::67 (2607:f8b0:400e:c04::67), 30 hops max, 80 byte packets
 1  2001:550:1:31e::1 (2001:550:1:31e::1)  50.613 ms  50.614 ms
 2  2001:550::67:1110 (2001:550::67:1110)  56.292 ms 2001:550::67:1113 (2001:550::67:1113)  56.685 ms
 3  2001:550:4::40 (2001:550:4::40)  56.778 ms  56.753 ms
 4  2001:550::1091 (2001:550::1091)  56.589 ms  56.595 ms
 5  2001:550::20:88 (2001:550::20:88)  56.538 ms 2001:550::20:136 (2001:550::20:136)  56.277 ms
 6  2001:550::190 (2001:550::190)  56.726 ms 2001:550::24 (2001:550::24)  56.706 ms
 7  2001:550::201 (2001:550::201)  56.398 ms 2001:550::202 (2001:550::202)  56.446 ms
 8  2001:550:4::47 (2001:550:4::47)  56.693 ms  57.446 ms
 9  2001:550:2:2::1b:2 (2001:550:2:2::1b:2)  56.017 ms  56.012 ms
10  2001:4860::1:0:92e (2001:4860::1:0:92e)  56.352 ms 2001:4860::1:0:3f7 (2001:4860::1:0:3f7)  61.097 ms
11  2001:4860::8:0:2fea (2001:4860::8:0:2fea)  56.324 ms  56.296 ms
12  2001:4860::8:0:281d (2001:4860::8:0:281d)  66.918 ms  70.731 ms
13  2001:4860::8:0:3427 (2001:4860::8:0:3427)  79.888 ms 2001:4860::8:0:3426 (2001:4860::8:0:3426)  78.629 ms
14  2001:4860::8:0:252c (2001:4860::8:0:252c)  105.191 ms  105.167 ms
15  2001:4860::8:0:2b60 (2001:4860::8:0:2b60)  112.857 ms 2001:4860::8:0:467d (2001:4860::8:0:467d)  112.111 ms
16  2001:4860::2:0:ac (2001:4860::2:0:ac)  139.306 ms  142.362 ms
17  pc-in-x67.1e100.net (2607:f8b0:400e:c04::67)  112.147 ms  112.103 ms
 

TATA

Tracing the route to pc-in-x67.1e100.net (2607:F8B0:400E:C04::67)
 
  1 POS5-1-1.core1.00S-Seattle.ipv6.as6453.net (2001:5A0:3100:100::A) 188 msec 200 msec 12 msec
  2 if-xe-5-1-0.0.tcore2.CT8-Chicago.ipv6.as6453.net (2001:5A0:1F00:200::39) 200 msec 204 msec 204 msec
  3 if-ae22.2.tcore1.CT8-Chicago.ipv6.as6453.net (2001:5A0:40:300::2) 108 msec 160 msec 56 msec
  4 if-ae12.6.tcore2.NYY-NewYork.ipv6.as6453.net (2001:5A0:400:700::21) 204 msec 164 msec 80 msec
  5 if-ae11.2.tcore1.NYY-NewYork.ipv6.as6453.net (2001:5A0:400:700::2) 76 msec 76 msec 80 msec
  6 if-ae5.5.tcore1.NTO-NewYork.ipv6.as6453.net (2001:5A0:400:200::E) 108 msec 80 msec 76 msec
  7 if-ae8.2.tcore2.NTO-NewYork.ipv6.as6453.net (2001:5A0:12:100::2E) 80 msec 80 msec 76 msec
  8 2001:4860:1:1:0:1935:0:13 88 msec 92 msec 132 msec
  9 2001:4860::1:0:3BE 80 msec
    2001:4860::1:0:755 80 msec
    2001:4860::1:0:3BE 80 msec
 10 2001:4860::8:0:4397 76 msec
    2001:4860::8:0:4398 80 msec 76 msec
 11 2001:4860::8:0:2FEA 84 msec
    2001:4860::8:0:2FE9 84 msec 84 msec
 12 2001:4860::8:0:281D 96 msec
    2001:4860::8:0:281E 96 msec
    2001:4860::8:0:281D 100 msec
 13 2001:4860::8:0:3427 104 msec 104 msec
    2001:4860::8:0:3426 108 msec
 14 2001:4860::8:0:252C 84 msec 84 msec 80 msec
 15 2001:4860::8:0:467D 92 msec 88 msec 92 msec
 16 2001:4860::2:0:AC 92 msec 88 msec 88 msec
 17  *  *  * 
 18 pc-in-x67.1e100.net (2607:F8B0:400E:C04::67) 92 msec 88 msec 92 msec
 


martyb

join:2013-05-18
Wemindji, QC

3 edits
those HE and TATA traceroutes are super interesting. It seems TATA has to carry all the way to the east coast to get to 2607:F8B0:400E:C04::67.

Interestingly from a vantage point I have, either HE or TATA have about 10ms of latency difference, HE being 70ms to that destination and TATA being 80. I am on the east coast ;) I guess if its all about Google than the place to be is HE on the west coast :)

However, using sufficiently functional geolocated DNS, I resolve www.google.com to 2607:f8b0:400c:c03::67 instead, which is half that either by HE or TATA so it ends up being what you resolve as well.

if I try that IP from the HE looking glass in Seattle it is no longer 10ms to get to google ...

1 12 ms 23 ms 22 ms 10gigabitethernet12-3.core1.sea1.he.net (2001:470:0:231::1)
2 3 ms 3 ms 3 ms google-as15169.gigabitethernet2-8.core1.sea1.he.net (2001:470:0:130::2)
3 3 ms 11 ms 4 ms 2001:4860::1:0:795
4 3 ms 4 ms 12 ms 2001:4860::8:0:252c
5 50 ms 49 ms 60 ms 2001:4860::8:0:3426
6 49 ms 50 ms 48 ms 2001:4860::8:0:281e
7 49 ms 49 ms 49 ms 2001:4860::8:0:2fe9
8 75 ms 68 ms 70 ms 2001:4860::8:0:2f03
9 77 ms 77 ms 80 ms 2001:4860::8:0:33b3
10 77 ms 86 ms 77 ms 2001:4860::2:0:3a3
11 * * * ?
12 79 ms 77 ms 76 ms vc-in-x67.1e100.net (2607:f8b0:400c:c03::67)
 

mactalla, I would avoid using ipv6.google.com as a test since www.google.com is now replying with a AAAA it is probably best to use that as your benchmark.

mactalla

join:2008-02-19
kudos:1
reply to TSI Gabe
As an update to the original issue of having a working IPv6 setup in the West:

I've upgraded to Barrier Breaker (bleeding edge snapshot) and so far things pretty much Just Work. The PPPoE interface still picks up an address, but now it's no longer adding the broken route. Still using 6relayd to spread the IPv6 goodness to the LAN side. I'll run with this for a while and see how stable it is.


spock

join:2012-07-08
Reviews:
·Shaw
·TekSavvy DSL
Thanks for the effort Mactalla. I have received zero support in the direct forum or TSI directly. Heck all I was asking in the direct forum was what kind of configuration we should be running for TSI West customers. I was told to post that question in the beta forum. So far it looks like there are only 3-4 of us out west on this forum trying to make this work and non of us are having any real sort of luck besides hack together a work-around using 6relayd.

34764170

join:2007-09-06
Etobicoke, ON
reply to mactalla
said by mactalla:

As an update to the original issue of having a working IPv6 setup in the West:

I've upgraded to Barrier Breaker (bleeding edge snapshot) and so far things pretty much Just Work. The PPPoE interface still picks up an address, but now it's no longer adding the broken route. Still using 6relayd to spread the IPv6 goodness to the LAN side. I'll run with this for a while and see how stable it is.

Ya, if using OpenWRT don't bother with anything but trunk snapshots until they get around to rolling another stable release.