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

Is http://ipv6-test.com/ working?

Started by bimmerdriver, March 17, 2013, 11:04:41 AM

Previous topic - Next topic

bimmerdriver

I've been using a few ipv6 tests to verify that everything is working.

Currently, http://test-ipv6.com/ is working (10/10), but http://ipv6-test.com/ is not working. The latter says my connection is not ipv6 capable. I'm wondering if others are having the same problem. I can ping it with ipv4, but not with ipv6. tracert -4 reached it in 14 hops. tracert -6 started to time out on the 10th hop and maxed out at 30 hops. Is there a problem reaching this site?

kasperd

Quote from: bimmerdriver on March 17, 2013, 11:04:41 AMCurrently, http://test-ipv6.com/ is working (10/10), but http://ipv6-test.com/ is not working.
Same for me. My attempt at loading ipv6-test.com has been hanging for minutes now.

A few traceroute commands point at a problem on the network somewhere between HE and the network hosting ipv6-test.com. The route goes to 2001:470:0:213::2 and I get no replies beyond that. I see that through two different tunnel providers (yes ending at the same HE address even when using another tunnel provider).

If I do a traceroute from a VPS with native IPv6 connectivity the connection is working, I do get a result from 2001:41d0:1:d87c::7e57:1. If I ping the server over 6to4 it also works (tested through two different ISPs). So it isn't due to the server being down. I can't pinpoint the network problem more precisely.

Notice that since test-ipv6.com appears to be hosted on the HE network, it is no surprise it is still responding. You'd expect the connectivity between tunnelbroker.net users and test-ipv6.com being more stable with both ends being in the HE network.

I don't know if you have noticed it, but test-ipv6.com has a tab with reachability tests between your browser and a long list of IPv6 sites. about half the sites on that list are IPv6 test sites, one of them is hosted on my VPS.

bimmerdriver

Quote from: kasperd on March 17, 2013, 12:02:39 PM
Quote from: bimmerdriver on March 17, 2013, 11:04:41 AMCurrently, http://test-ipv6.com/ is working (10/10), but http://ipv6-test.com/ is not working.
Same for me. My attempt at loading ipv6-test.com has been hanging for minutes now.

A few traceroute commands point at a problem on the network somewhere between HE and the network hosting ipv6-test.com. The route goes to 2001:470:0:213::2 and I get no replies beyond that. I see that through two different tunnel providers (yes ending at the same HE address even when using another tunnel provider).

If I do a traceroute from a VPS with native IPv6 connectivity the connection is working, I do get a result from 2001:41d0:1:d87c::7e57:1. If I ping the server over 6to4 it also works (tested through two different ISPs). So it isn't due to the server being down. I can't pinpoint the network problem more precisely.

Notice that since test-ipv6.com appears to be hosted on the HE network, it is no surprise it is still responding. You'd expect the connectivity between tunnelbroker.net users and test-ipv6.com being more stable with both ends being in the HE network.

I don't know if you have noticed it, but test-ipv6.com has a tab with reachability tests between your browser and a long list of IPv6 sites. about half the sites on that list are IPv6 test sites, one of them is hosted on my VPS.
thanks for the reply. I figured the problem was with the site or the network, not my network. The only site on the list that I can't reach is test-ipv6.vyncke.org. It says I fail tests 2 and 5.

elc

Both test-ipv6.com and test-ipv6.vyncke.org are on the OVH network. The OVH IPv6 issues started shortly after 2013-03-15 21:30 UTC, when I noticed that I could not reach my OVH dedicated server from my tunnelbroker.net tunnel.
When I perform the test-ipv6 connectivity test from my OVH dedicated server, the following entries on the 'Other IPv6 Sites' tab fail:

kasperd

Quote from: elc on March 18, 2013, 04:10:48 AMThe OVH IPv6 issues started shortly after 2013-03-15 21:30 UTC, when I noticed that I could not reach my OVH dedicated server from my tunnelbroker.net tunnel.
You should try running a traceroute from each end of that connection. Additionally it would be useful to run a tcpdump at the other end of the tunnel to see if the packets make it through. When a traceroute command shows packet loss you cannot see if packets are being dropped in both directions only by looking at the output from traceroute.

elc

Quote from: kasperd on March 18, 2013, 07:06:49 AM
Quote from: elc on March 18, 2013, 04:10:48 AMThe OVH IPv6 issues started shortly after 2013-03-15 21:30 UTC, when I noticed that I could not reach my OVH dedicated server from my tunnelbroker.net tunnel.
You should try running a traceroute from each end of that connection. Additionally it would be useful to run a tcpdump at the other end of the tunnel to see if the packets make it through. When a traceroute command shows packet loss you cannot see if packets are being dropped in both directions only by looking at the output from traceroute.
I created a support ticket with traceroutes on Saturday. I hadn't though about running tcpdump and fortunately can't do that now, because they fixed it :-)
If someone is still interested in good / bad traceroutes,I can post them here (or in the other thread).

bimmerdriver