You are here: version6.ru » Welcome! » Your IPv6 is down
Differences
This shows you the differences between two versions of the page.
en:your-ipv6-is-down [2012-06-23 19:14 UTC] rm создано |
en:your-ipv6-is-down [2012-09-21 04:27 UTC] (current) rm |
||
---|---|---|---|
Line 2: | Line 2: | ||
<code>Hello! | <code>Hello! | ||
- | I have just visited your website, and a it took about 20 seconds to load for me. | + | I have just visited your website, and it took about 20 seconds to load (or didn't load at all). |
Already knowing what might be the reason, I checked if your domain has an AAAA-record. | Already knowing what might be the reason, I checked if your domain has an AAAA-record. | ||
- | And sure enough, it does. Pinging/tracing the actual IPv6 and also trying to fetch your | + | And sure enough, it does. Pinging/tracing the actual IPv6 and also trying to fetch your page |
- | page with ''curl'', I have found one or more of the following issues with your IPv6 connectivity: | + | with ''curl'', I have found one or more of the following issues with your IPv6 connectivity: |
[ ] Your HE.net tunnel is down; perhaps your v4 endpoint changed and you forgot to update it? | [ ] Your HE.net tunnel is down; perhaps your v4 endpoint changed and you forgot to update it? | ||
+ | [ ] Your 6to4 is down; did you allow protocol 41 only if it's coming from 192.88.99.1? DERP! | ||
[ ] You use an overly paranoid ip6tables ruleset, and didn't know that blocking ICMP will | [ ] You use an overly paranoid ip6tables ruleset, and didn't know that blocking ICMP will | ||
lead to MTU issues, causing inability to load anything longer than 1KB from your website | lead to MTU issues, causing inability to load anything longer than 1KB from your website | ||
Line 14: | Line 15: | ||
[ ] You use OVH and got bitten by their recent decision to turn off RAs. | [ ] You use OVH and got bitten by their recent decision to turn off RAs. | ||
- | I suspect one or more of the following might apply with regards to reason of why that is so: | + | I suspect one or more of the following might apply with regards to the reason of why that is so: |
[ ] You have configured IPv6 months ago by following a random howto on the Internet on | [ ] You have configured IPv6 months ago by following a random howto on the Internet on | ||
Line 28: | Line 29: | ||
which are still in a minority right now) have to endure 10 to 20 second delays before each and every | which are still in a minority right now) have to endure 10 to 20 second delays before each and every | ||
page load from your site, as their browser tries IPv6 and waits for a timeout until it fails. | page load from your site, as their browser tries IPv6 and waits for a timeout until it fails. | ||
+ | Which also means people using certain apps like the Squid proxy can't visit your website at all, | ||
+ | because those apps do not retry via IPv4 if they fail connecting over IPv6. | ||
- | So as some of the steps to the solution I recommend one or more of the following: | + | So as some of the steps to the solution, one or more of the following can be recommended: |
[ ] Gain IPv6 connectivity at your workplace and at home, use a tunnel if you have to, so that you | [ ] Gain IPv6 connectivity at your workplace and at home, use a tunnel if you have to, so that you | ||
Line 41: | Line 44: | ||
Adding broken IPv6 to a website does no good for IPv6 adoption. Please do IPv6 properly or do not | Adding broken IPv6 to a website does no good for IPv6 adoption. Please do IPv6 properly or do not | ||
do it at all. A half-assed approach only harms everybody.</code> | do it at all. A half-assed approach only harms everybody.</code> | ||
+ | Feel free to copy-paste to people :P or add new items to each of the lists, but since this is not a publicly editable wiki, mail them [[rm>contact|to me]]. | ||
+ | |||
+ | And yes, this text is in part inspired by and written in the style of the wonderful http://craphound.com/spamsolutions.txt |
en/your-ipv6-is-down.1340478861.txt.gz · Last modified: 2012-06-23 19:14 UTC by rm