I believe I might have a similar issue to amwdrizz's (http://"http://www.tunnelbroker.net/forums/index.php?topic=2755.0") with a VPS I'm renting (different provider though).
I'm not exactly sure how to ask this, so here's an information dump - I can clarify if needed!
The VPS' IP address is 2607:f3f0:2::a061:e2a4
Another IP in the same network (different server): 2607:f3f0:2::309b:a9b0
I'm unable to reach either of these address through my tunnelbroker or via a couple of HE looking glasses but I am able to on another provider with native IPv6.
Tunnel Area: SEA1
Traceroute from my tunnel to 2607:f3f0:2::a061:e2a4:
Quote
traceroute6 to 2607:f3f0:2::a061:e2a4 (2607:f3f0:2::a061:e2a4) from ~snip~, 64 hops max, 12 byte packets
1 ~snip~ 0.367 ms 0.518 ms 0.280 ms
2 ~snip~.sea1.ipv6.he.net 51.959 ms 54.459 ms 52.220 ms
3 gige-g2-6.core1.sea1.he.net 60.512 ms 55.741 ms 50.784 ms
4 10gigabitethernet3-1.core1.den1.he.net 87.815 ms 82.692 ms 86.843 ms
5 10gigabitethernet8-2.core1.chi1.he.net 105.280 ms 115.700 ms 116.990 ms
6 equinix-v6-exchange-chi.merit.edu 105.113 ms 106.446 ms 105.825 ms
7 * * *
8 * * *
9 * * *
10 * * *
Traceroute from my tunnel to 2607:f3f0:2::309b:a9b0
Quote
traceroute6 to 2607:f3f0:2::309b:a9b0 (2607:f3f0:2::309b:a9b0) from ~snip~, 64 hops max, 12 byte packets
1 ~snip~ 0.375 ms 0.402 ms 0.310 ms
2 ~snip~.sea1.ipv6.he.net 57.240 ms 54.814 ms 54.161 ms
3 gige-g2-6.core1.sea1.he.net 50.848 ms 59.121 ms 53.957 ms
4 10gigabitethernet3-1.core1.den1.he.net 88.289 ms 84.545 ms 88.539 ms
5 10gigabitethernet8-2.core1.chi1.he.net 109.538 ms 115.329 ms 105.200 ms
6 equinix-v6-exchange-chi.merit.edu 106.095 ms 108.261 ms 106.333 ms
7 * * *
Traceroute from native IPv6 (VPS with different provider) to 2607:f3f0:2::a061:e2a4:
Quote
traceroute to 2607:f3f0:2::a061:e2a4 (2607:f3f0:2::a061:e2a4), 30 hops max, 80 byte packets
1 ~snip~ (~snip~) 0.073 ms 0.019 ms 0.033 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * 2001:550::221 (2001:550::221) 515.383 ms
7 * * *
8 * * *
9 * * *
10 2001:550:2:62::1:1 (2001:550:2:62::1:1) 74.509 ms 74.468 ms 74.466 ms
11 2001:550:2:62::1:2 (2001:550:2:62::1:2) 74.826 ms 74.729 ms 74.695 ms
12 2607:f3f0:0:4:2d0:ff:fe9e:2400 (2607:f3f0:0:4:2d0:ff:fe9e:2400) 74.839 ms 74.761 ms 74.652 ms
13 2607:f3f0:0:e::5 (2607:f3f0:0:e::5) 74.235 ms 74.629 ms 74.383 ms
14 2607:f3f0:2::a061:e2a4 (2607:f3f0:2::a061:e2a4) 420.836 ms 420.090 ms 419.984 ms
Traceroute from native IPv6 (VPS with different provider) to 2607:f3f0:2::309b:a9b0
Quote
traceroute to 2607:f3f0:2::309b:a9b0 (2607:f3f0:2::309b:a9b0), 30 hops max, 80 byte packets
1 ~snip~ (~snip~) 0.056 ms 0.020 ms 0.028 ms
2 2607:f358:1a:4::1 (2607:f358:1a:4::1) 3.388 ms 3.407 ms 3.328 ms
3 2001:450:2002:4ad::1 (2001:450:2002:4ad::1) 3.833 ms 3.778 ms 3.713 ms
4 2001:450:2008:100::2e (2001:450:2008:100::2e) 52.839 ms 52.799 ms 52.746 ms
5 2001:550::202 (2001:550::202) 76.897 ms 76.873 ms 76.783 ms
6 2001:550::221 (2001:550::221) 76.711 ms 76.293 ms 76.183 ms
7 * * *
8 * * *
9 * * *
10 2001:550:2:62::1:1 (2001:550:2:62::1:1) 74.513 ms 76.117 ms 76.051 ms
11 2001:550:2:62::1:2 (2001:550:2:62::1:2) 75.980 ms 75.916 ms 75.759 ms
12 2607:f3f0:0:3:2d0:ff:fea7:f000 (2607:f3f0:0:3:2d0:ff:fea7:f000) 84.442 ms 84.285 ms 88.948 ms
13 2607:f3f0:0:e::5 (2607:f3f0:0:e::5) 74.238 ms 74.107 ms 73.996 ms
14 2607:f3f0:2::309b:a9b0 (2607:f3f0:2::309b:a9b0) 505.884 ms 505.826 ms 492.020 ms
Unsure why one produced more information than the other.
Here are a couple from the looking glass:
core1.dal1.he.net> traceroute ipv6 2607:f3f0:2::a061:e2a4
Quote
Tracing the route to IPv6 node 2607:f3f0:2::a061:e2a4 from 1 to 30 hops
1 31 ms 51 ms 24 ms 10gigabitethernet4-4.core1.chi1.he.net [2001:470:0:1bb::2]
2 32 ms 50 ms 23 ms equinix-V6-exchange-chi.merit.edu [2001:504:0:4::237:1]
3 * * * ?
4 * * * ?
5 * * * ?
6 * * * ?
IP: Errno( 8 ) Trace Route Failed, no response from target node.
core1.den1.he.net> traceroute ipv6 2607:f3f0:2::a061:e2a4
Quote
Tracing the route to IPv6 node 2607:f3f0:2::a061:e2a4 from 1 to 30 hops
1 23 ms 23 ms 23 ms 2001:470:0:1af::1
2 29 ms 30 ms 24 ms 2001:504:0:4::237:1
3 * * * ?
4 * * * ?
5 * * * ?
6 * * * ?
IP: Errno( 8 ) Trace Route Failed, no response from target node.
My provider isn't sure where they should go from the above as they don't peer with HE - could someone please point me in the right direction with what might be wrong?
Thanks in advance all!
I can reach your VPS IP (2607:f3f0:2::a061:e2a4) with my SixXS tunnel, but it takes many hops to reach the destination:
Quote
E:\>tracert -6 2607:f3f0:2::a061:e2a4
Tracing route to 2607:f3f0:2::a061:e2a4 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms ge-3.r03-pnh.tnc92.net [2401:e800:101:8000::1]
2 <1 ms <1 ms <1 ms ge-5.r02-pnh.tnc92.net [2401:e800:101:2002::1]
3 <1 ms <1 ms <1 ms ge-1.r05-pnh.tnc92.net [2401:e800:101:2004::2]
4 49 ms 46 ms 43 ms gw-15.han-01.vn.sixxs.net [2401:e800:100:e::1]
5 48 ms 49 ms 48 ms vnhan01.sixxs.net [2401:e800::4]
6 50 ms 49 ms 49 ms 2401:e800:3::1
7 49 ms 49 ms 54 ms 2001:7fa:6:1::3
8 196 ms 189 ms 187 ms 2001:2e0:5000:5000::11
9 190 ms 190 ms 184 ms 2001:2e0:1000:2000::d
10 193 ms 191 ms 191 ms 2001:2e0:1000:2000::11
11 191 ms 190 ms 193 ms ge-1-2-7.r21.newthk02.hk.bb.gin.ntt.net [2001:21
8:6000:5000::d]
12 281 ms 245 ms 237 ms as-1.r25.tokyjp01.jp.bb.gin.ntt.net [2001:218:0:
2000::13d]
13 246 ms 236 ms 240 ms ae-9.r20.tokyjp01.jp.bb.gin.ntt.net [2001:218:0:
2000::1c5]
14 336 ms 372 ms 349 ms as-1.r20.sttlwa01.us.bb.gin.ntt.net [2001:218:0:
2000::21]
15 354 ms 358 ms 344 ms ae-1.r05.sttlwa01.us.bb.gin.ntt.net [2001:418:0:
2000::305]
16 460 ms 421 ms 415 ms 2001:550:3::309
17 * * * Request timed out.
18 412 ms 418 ms 417 ms 2001:550::1091
19 * * * Request timed out.
20 426 ms 420 ms 425 ms 2001:550::190
21 * * * Request timed out.
22 431 ms 418 ms 423 ms 2001:550::213
23 * * * Request timed out.
24 423 ms 435 ms 439 ms 2001:550:2:62::1:1
25 428 ms 433 ms 432 ms 2001:550:2:62::1:2
26 439 ms 430 ms 428 ms 2607:f3f0:0:3:2d0:ff:fea7:f000
27 431 ms 436 ms 437 ms 2607:f3f0:0:e::5
28 1061 ms 420 ms 428 ms 2607:f3f0:2::12:0:1
29 423 ms 425 ms 416 ms 2607:f3f0:2::a061:e2a4
Trace complete.
Could you try traceroute from your VPS to your HE tunnel IP and see where the traffic being routed to?
Traceroutes from my VPS to 2607:f3f0:2::a061:e2a4
Using HE tunnel:
traceroute to 2607:f3f0:2::a061:e2a4 (2607:f3f0:2::a061:e2a4), 30 hops max, 80 byte packets
2 2001:470:25:4fa::1 18.603 ms 20.165 ms 21.632 ms
3 2001:470:0:11d::1 21.986 ms 13.515 ms 13.981 ms
4 2001:470:0:246::1 26.586 ms 27.068 ms 26.740 ms
5 2001:470:0:21e::1 42.486 ms 43.005 ms 42.802 ms
6 2001:470:0:128::1 102.033 ms 101.853 ms 101.548 ms
7 2001:470:0:1c6::2 119.427 ms 119.072 ms 120.132 ms
8 2001:504:0:4::237:1 120.422 ms 120.520 ms 120.712 ms
9 * * *
...
30 * * *
Using 6to4:
traceroute to 2607:f3f0:2::a061:e2a4 (2607:f3f0:2::a061:e2a4), 30 hops max, 80 byte packets
3 2a01:138:0:113::a 14.767 ms 14.209 ms 14.234 ms
4 2001:680:0:800f::51 14.345 ms 14.353 ms 14.350 ms
5 2001:680:0:134:222:230:240:2 49.894 ms 49.387 ms 49.429 ms
6 * * *
7 2001:978:3::12 26.357 ms 25.845 ms 25.873 ms
8 2001:978:3::11 53.384 ms 53.418 ms 53.233 ms
9 2001:978::19 156.043 ms 156.044 ms 156.078 ms
10 2001:550::105 155.758 ms 155.792 ms 155.793 ms
11 2001:550::26 153.086 ms 152.287 ms 152.293 ms
12 2001:550::76 152.886 ms 152.916 ms 152.057 ms
13 ::ffff:154.54.29.130 260.984 ms 158.300 ms 158.322 ms
14 ::ffff:154.54.29.138 223.286 ms 223.303 ms 223.281 ms
15 ::ffff:154.54.29.213 152.713 ms 152.702 ms 152.713 ms
16 2001:550:2:62::1:1 313.764 ms 313.767 ms 313.739 ms
17 2001:550:2:62::1:2 152.644 ms 152.656 ms 152.687 ms
18 2607:f3f0:0:3:2d0:ff:fea7:f000 155.939 ms 155.995 ms 156.011 ms
19 2607:f3f0:0:e::5 155.768 ms 155.412 ms 155.940 ms
20 2607:f3f0:2::12:0:1 152.715 ms 152.755 ms 151.717 ms
21 2607:f3f0:2::a061:e2a4 155.444 ms 155.732 ms 155.758 ms
Using native:
traceroute to 2607:f3f0:2::a061:e2a4 (2607:f3f0:2::a061:e2a4), 30 hops max, 80 byte packets
4 2a01:4f8:d16:2::1 4.668 ms 4.684 ms 4.642 ms
5 2a01:4f8:0:d1:3:0:10:2 1.063 ms 0.589 ms 0.603 ms
6 2a01:4f8:0:2::b:4 3.437 ms 3.449 ms 3.448 ms
7 2001:1620:1000::1a9 3.514 ms 3.338 ms 3.352 ms
8 2001:1620:2::f2 3.623 ms 3.647 ms 3.648 ms
9 2001:1620:2::101 6.610 ms 6.204 ms 6.216 ms
10 2001:1620:2::e1 17.284 ms 17.327 ms 17.425 ms
11 2001:1620:2::5 13.324 ms 13.278 ms 13.291 ms
12 2001:668:0:3::5000:11 13.144 ms 13.157 ms 13.614 ms
13 2001:668:0:2::1:13d2 17.644 ms 17.496 ms 2001:668:0:2::1:1d21 17.852 ms
14 2001:978:3::49 145.102 ms 145.112 ms 145.108 ms
15 2001:978::135 134.022 ms 133.819 ms 133.842 ms
16 2001:978::19 132.638 ms 132.676 ms 132.700 ms
17 2001:550::105 131.363 ms 131.206 ms 131.238 ms
18 2001:550::26 133.682 ms 133.705 ms 133.716 ms
19 2001:550::76 133.637 ms 133.194 ms 133.217 ms
20 * * *
21 * * *
22 * * *
23 2001:550:2:62::1:1 133.577 ms 133.011 ms 133.131 ms
24 2001:550:2:62::1:2 133.134 ms 133.061 ms 133.066 ms
25 2607:f3f0:0:3:2d0:ff:fea7:f000 133.088 ms 133.108 ms 133.146 ms
26 2607:f3f0:0:e::5 130.897 ms 130.927 ms 130.885 ms
27 2607:f3f0:2::12:0:1 131.441 ms 131.435 ms 131.478 ms
28 2607:f3f0:2::a061:e2a4 131.496 ms 131.514 ms 131.184 ms
Quote from: gawamakito on January 02, 2013, 06:58:55 AM
I can reach your VPS IP (2607:f3f0:2::a061:e2a4) with my SixXS tunnel, but it takes many hops to reach the destination:
Could you try traceroute from your VPS to your HE tunnel IP and see where the traffic being routed to?
Oops! I can't believe I forgot that! Here's the traceroute and a ping:
Quote
[2607:f3f0:2::a061:e2a4]:~$ traceroute6 ~tunnel IP~
traceroute to ~tunnel IP~, 30 hops max, 80 byte packets
1 2607:f3f0:2::12:0:1 (2607:f3f0:2::12:0:1) 0.512 ms 0.035 ms 0.032 ms
2 * * *
3 * * *
4 2607:f3f0:0:1:212:1ff:fea1:dac0 (2607:f3f0:0:1:212:1ff:fea1:dac0) 59.837 ms !N 59.961 ms !N 59.927 ms !N
Quote
[2607:f3f0:2::a061:e2a4]:~$ ping6 ~tunnel IP~
PING ~tunnel IP~ 56 data bytes
From ~tunnel IP~ icmp_seq=1 Destination unreachable: No route
From ~tunnel IP~ icmp_seq=2 Destination unreachable: No route
Here's a ping and traceroute to google for comparison:
Quote
[2607:f3f0:2::a061:e2a4]:~$ ping6 ipv6.google.com
PING ipv6.google.com(yyz06s07-in-x11.1e100.net) 56 data bytes
64 bytes from yyz06s07-in-x11.1e100.net: icmp_seq=1 ttl=47 time=194 ms
64 bytes from yyz06s07-in-x11.1e100.net: icmp_seq=2 ttl=47 time=48.6 ms
64 bytes from yyz06s07-in-x11.1e100.net: icmp_seq=3 ttl=47 time=48.6 ms
64 bytes from yyz06s07-in-x11.1e100.net: icmp_seq=4 ttl=47 time=48.5 ms
64 bytes from yyz06s07-in-x11.1e100.net: icmp_seq=5 ttl=47 time=48.6 ms
^C
--- ipv6.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 48.556/77.784/194.454/58.335 ms
Quote
[2607:f3f0:2::a061:e2a4]:~$ traceroute6 ipv6.google.com
traceroute to ipv6.google.com (2001:4860:4008:802::1011), 30 hops max, 80 byte packets
1 2607:f3f0:2::12:0:1 (2607:f3f0:2::12:0:1) 0.127 ms 0.035 ms 0.034 ms
2 2607:f3f0:0:e::1 (2607:f3f0:0:e::1) 0.848 ms 0.823 ms 0.789 ms
3 2607:f3f0:0:3:212:1ff:fec3:2540 (2607:f3f0:0:3:212:1ff:fec3:2540) 0.755 ms 1.002 ms 0.944 ms
4 2001:550:2:62::1:1 (2001:550:2:62::1:1) 0.518 ms 0.717 ms 0.680 ms
5 * * *
6 * * *
7 * * *
8 2001:550::221 (2001:550::221) 25.347 ms 25.888 ms 25.960 ms
9 2001:550::148 (2001:550::148) 25.779 ms 25.781 ms 25.671 ms
10 2001:550:4::3c (2001:550:4::3c) 25.710 ms 2001:550::194 (2001:550::194) 25.304 ms 2001:550:4::3c (2001:550:4::3c) 25.184 ms
11 2001:550:4::4a (2001:550:4::4a) 25.319 ms 25.347 ms 25.486 ms
12 2001:550:2:2f::d:2 (2001:550:2:2f::d:2) 24.866 ms 24.587 ms 24.625 ms
13 2001:4860::1:0:9ff (2001:4860::1:0:9ff) 26.072 ms 2001:4860::1:0:5dc (2001:4860::1:0:5dc) 27.240 ms 2001:4860::1:0:9ff (2001:4860::1:0:9ff) 25.960 ms
14 2001:4860::8:0:3cd9 (2001:4860::8:0:3cd9) 25.714 ms 25.836 ms 25.637 ms
15 2001:4860::8:0:2fc6 (2001:4860::8:0:2fc6) 84.241 ms 83.039 ms 83.000 ms
16 2001:4860::1:0:3be (2001:4860::1:0:3be) 44.081 ms 2001:4860::1:0:755 (2001:4860::1:0:755) 31.434 ms 31.559 ms
17 2001:4860::8:0:4398 (2001:4860::8:0:4398) 31.228 ms 31.260 ms 31.331 ms
18 2001:4860::1:0:28 (2001:4860::1:0:28) 48.535 ms 48.500 ms 48.416 ms
19 2001:4860:0:1::26e (2001:4860:0:1::26e) 48.381 ms 48.441 ms 48.523 ms
20 2001:4860:8000:9:92e6:baff:fe53:a7d2 (2001:4860:8000:9:92e6:baff:fe53:a7d2) 48.162 ms 48.294 ms 48.189 ms
Quote from: kasperd on January 02, 2013, 10:23:36 AM
Traceroutes from my VPS to 2607:f3f0:2::a061:e2a4
~snip~
Thanks! I'll pass those along
Your provider has some Level3 IPv6 connectivity, so they should know how to get to HE's IPv6: http://bgp.he.net/AS16724#_graph6
However it looks like they heavily use Cogent for all their IPv6 routes, so perhaps that L3 path is simply ignored. You won't get to HE via Cogent :)
Quote from: broquea on January 02, 2013, 05:30:49 PM
Your provider has some Level3 IPv6 connectivity, so they should know how to get to HE's IPv6: http://bgp.he.net/AS16724#_graph6
However it looks like they heavily use Cogent for all their IPv6 routes, so perhaps that L3 path is simply ignored. You won't get to HE via Cogent :)
Thanks! I've given them the link to this thread - I'll update again once they reply. :)