3 ms·
World IPv6 Day: Solving the IP Address Chicken-and-Egg Challenge
- pohl 16y agoIt's wonderful to see some leadership here. Don't miss the IPv6 address they have... 2620:0:1cfe:face:b00c::3
- mike-cardwell 16y agoIPv6 really isn't that difficult. It only takes a few minutes to get a free IPv6 address from a tunnel broker and add it to your server. My websites and email were all dual stack less than 24 hours after I started looking into IPv6 for the first time. I wrote a blog post about it last year: https://secure.grepular.com/Setting_up_IPv6_is_Easier_Than_You_Think https://secure.grepular.com/Setting_up_IPv6_is_Easier_Than_Y... If you get a cert error it's because the certificate is signed by cacert.org and several major browser/os combos don't have their root yet.
- torme 16y agoThis seems very cool, neat that these companies are taking this upon themselves. That said, does anyone know the potential risks to these companies for this? I personally tried the facebook IPv6 site and it doesn't work. Are there going to be users who are unable to use these sites on this day?
- wmf 16y agoThe risk is that ~0.001% of computers won't be able to access Facebook or Google for one day because they think they have working IPv6 but they actually don't.
- torme 16y agoSince I can't access the v6 version of facebook, does that mean that I'm in the 0.001%?
- wmf 16y agoNot necessarily; if your computer doesn't have IPv6 and knows that it doesn't have IPv6 then you're going to be fine.
- zaphoyd 16y agoThe risk is much smaller today than it was when the ipv6 whitelists for google, etc were originally set up. All patched modern operating systems and browsers have corrected the behavior that originally caused this (preferring automatic v6 tunnels over native v4) so that the only brokenness remaining in theory is outdated software and improperly configured manual tunnels. See http://fud.no/ipv6/ http://fud.no/ipv6/ for more information on measurements of this issue as browsers and oses fixed this problem.
- loup-vaillant 16y agoFunny (though predictable) that they didn't explicitly state the number 1 downside of large scale NAT: the inability to have a server at home.