• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

Can't reach v6.testmyipv6.com with IPv6 tunnel

Started by PaulosV, June 05, 2013, 02:21:49 PM

Previous topic - Next topic

kasimir

I am having the same issue through all of my HE tunnels. From dual-homed hosts I can access v6.testmyipv6.com (2001:4830:2502:8002::ac10:a) just fine. Traceroutes are normal and it responds to pings.

However, from my two tunnels, I get the following:

traceroute to v6.testmyipv6.com (2001:4830:2502:8002::ac10:a) from 2001:470:67:6ef:1c69:a0ba:f826:d7d9, 30 hops max, 24 byte packets
1  ares.abq.siriuscloud.co (2001:470:67:6ef::1)  0.501 ms  0.429 ms  0.39 ms
2  kasimir-2.tunnel.tserv29.fmt1.ipv6.he.net (2001:470:66:6ef::1)  58.476 ms  57.894 ms  58.868 ms
3  ge5-1.core1.fmt1.he.net (2001:470:0:206::1)  56.388 ms  75.192 ms  65.816 ms
4  * * *
5  * * *
6  * * *
...


and

traceroute6 v6.testmyipv6.com
traceroute to v6.testmyipv6.com (2001:4830:2502:8002::ac10:a) from 2001:470:b:1e7::3010, 30 hops max, 24 byte packets
1  2001:470:b:1e7::2000 (2001:470:b:1e7::2000)  0.376 ms  0.358 ms  0.355 ms
2  kasimir-1.tunnel.tserv14.sea1.ipv6.he.net (2001:470:a:1e7::1)  22.611 ms  22.784 ms  22.614 ms
3  ge2-6.core1.sea1.he.net (2001:470:0:9b::1)  21.138 ms  21.334 ms  21.346 ms
4  * * *
5  * * *
6  * * *
...


This seems to impact much more than just testmyipv6.com. Any help would be appreciated.

broquea

TowardEX doesn't appear to be announcing the /32 or /48 the destination resides in to HE.NET (even though they appear to peer):

route-server> sh ipv6 bgp 2001:4830:2502:8002::ac10:a
% Network not in table
route-server> sh ipv6 bgp 2001:4830:2502::/48
% Network not in table
route-server> sh ipv6 bgp 2001:4830::/32
% Network not in table


This is something TowardEX fixes.