World IPv6 Day: Most-watched Tech Event Since Y2K
alphadogg wrote in with a fairly extreme bit of hyperbole saying "The nation's largest telecom carriers, content providers, hardware suppliers and software vendors will be on the edge of their seats today for World IPv6 Day, which is the most-anticipated 24 hours the tech industry has seen since fears of the Y2K bug dominated New Year's Eve in 1999. More than 400 organizations are participating in World IPv6 Day, a large-scale experiment aimed at identifying problems associated with IPv6, an upgrade to the Internet's main communications protocol, IPv4. Sponsored by the Internet Society, World IPv6 Day runs from 8 p.m. EST Tuesday until 7:59 p.m. EST Wednesday. The IT departments in the participating organizations have spent the last five months preparing their websites for an anticipated rise in IPv6-based traffic, more tech support calls and possible hacking attacks prompted by this largest-ever trial of IPv6."
I haven't gotten much use my well-stocked bomb shelter since Y2K. Sure, religious types keep predicting the end of the world, and guessing wrong every time. And bad predictions aren't going to justify the money I've put into this goddamn thing. Did you know that a generator's gaskets will dry-rot over time, even if you don't use it? Well guess what, they will--and that shit is expensive to fix too.
Man, if only we could have one nuclear war. Then the neighbors might finally stop laughing at me.
SJW: Someone who has run out of real oppression, and has to fake it.
Big names like Google are:
But one tech website you'd expect to want to dabble in the new and good for some reason isn't:
Well, of course!
You are not alone. This is not normal. None of this is normal.
This event had been very unpublicized for this to be the most-anticipated 24 hours in tech industry for the last 10 years.
I was happy to see xkcd, Google, Yahoo, Facebook, and Plurk turn on their IPv6 capabilities, but I was quite sad that Slashdot didn't take part in the World IPv6 Day.
The only reason why Y2K /wasn't/ a disaster was because people worked their asses off for it to not happen.
Idiots everywhere...
--
BMO
That's my question.
- Spryguy
There are three kinds of people in this world: those that can count and those that can't
I've seen a few already today!
www.facebook.com has IPv6 address 2620:0:1c18:0:face:b00c::
cisco.v6day.akadns.net has IPv6 address 2001:420:80:1:c:15c0:d06:f00d
www.luns.net.uk has IPv6 address 2a01:8900:0:1::b00b:1e5
www.bbc.net.uk has IPv6 address 2001:4b10:bbc::1
Does v6 kick off 'IP addresses as a marketing tool'? :)
So all this proves is these sites are capable of running both protocols simultaneously and while there is a DNS record that resolves to an ipv6 address, is anybody able to browse to these sites using ipv6 all the way through?
4,294,967,296 should be enough addresses for any internet
With Google pushing this so hard, why didn't they change the logo? They should have had one for the IPv6 crowd different from the IPv4....
Wiki is your friend.
tl;dr;
They skipped 5 to avoid confusion with the Internet Stream Protocol.
I work at a sort of small ISP and we've done testing, implementation, published our website with an AAAA record and put some information on the site for everyone to see.
We've gotten exactly one call (this morning) on IPv6 that I can remember. We published information and started doing some obvious IPv6 things, but no one cares. The group of dual-stack test accounts is pretty small, but they have not even seemed to care or notice. I'd put anyone that asks on a list for testing so they can use IPv6 at home. No one has asked. I guess I could put a big(er) banner on the page.. but really I don't think it would matter much.. and probably scare people.
All in all I will say the experience has been pretty anti-climatic. It was not that difficult to implement. There were bugs of course, (Fedora 13+14 blocking DHCPv6 client traffic, and other NetworkManager bugs) the Cisco CMTS and it's weird detection of static IPv4 only clients... duplicate address detection madness, incomplete support of DHCPv6 + SLAAC in routers (D-Link DIR-615..) but it was just me working on it and I did not have that difficult a time getting our network to route, connect and answer to IPv6. Most of the problems I dealt with were incomparable hardware. Routers and DOCSIS 2.0 + IPv6 modems which are pretty much non existent with the exception of one EMTA I've tested. You have to shell out the bucks for a DOCSIS 3.0 modem evidentially.
Of the D-Link routers I've tested the DIR-825 is the star. It was dead easy to configure. DD-WRT and Open-WRT are not easy and probably there is no build for your router if it only has 4Mb of flash.
Have Google modify their page rank algorithm to give any website accessible through IPV6 a slight boost. The power they hold over website revenues is so huge the SEO industry would go nuts over this and you'll see adoption rates explode.
Open Source Time and Attendance, Job Costing a
[Disclaimer: I am a pfSense developer, so I'm a bit biased. For those of you who don't know what pfSense is, it's a BSD-based firewall distribution.]
pfSense 2.0 won't officially support IPv6, but there is a branch available that does IPv6 which will later become 2.1. I'm running it on my home router with a GIF tunnel to Hurricane Electric ( http://he.net/ http://tunnelbroker.net/) to get IPv6 even though my ISPs do not have any native IPv6 support yet. The IPv6 support is a work in progress but is complete enough that it will do what most people want/need.
Instructions for the setup and more info can be found on the pfSense IPv6 board here: http://forum.pfsense.org/index.php/board,52.0.html
I get a 10/10 on the IPv6 tests from http://test-ipv6.com/ on all my PCs as well as my Droid X running 2.3.3. If you're already using pfSense 2.0, give the IPv6 code a try, setup a tunnel to he.net, and enjoy. Doesn't take too long at all to setup.