Another nail in IPv4’s coffin. And the article’s summary says:
[…] The U.S. and Canada? Our day of reckoning comes in August 2013.
I’ve been working on my communications code library recently, upgrading it to support proxies (which is a real pain in the tail when you don’t have a proper proxy to test things on, let me tell you!). While I was in there, I added some additional IPv6 support as well. When the time comes, my programs will be ready. 🙂
My dlink router isn’t IPv6 ready, but I like it’s performance and reliability a lot. Should I do something about it, HG?
You know the one I mean, it’s the same one you had, at least a while back.
No need. It’s pretty much only businesses (if they’re large enough to host their own websites) and ISP that have to worry about it right now. Your router will continue to work for a good long while, because your ISP will handle the translations and such for you. Even when sites start moving to IPv6-only, you should still be able to get to them through your ISP.
You’ll have plenty of warning before your router becomes obsolete, and no doubt you’ll have replaced it years if not decades before that warning arrives. 🙂
That’s nice to know, I like this router, although it’s no longer the best at speed, it’s still very good and enough to handle 100 megabit connections and more well unlike some popular consumer routers.
(I don’t plan on upgrading to 100 megabits until and if the price comes down, but I’ve had 50 in the past, though I recently downgraded when I noticed for most of my purposes it was indistinguishable from 15 megabits, although I can no longer run servers on my own computer without violating the TOS, unlike the 50 megabit service.)
I thought that would be appropos to this post.
Nice. Not that it would kill them to delay it a while longer, but the faster sites become IPv6-accessible, the faster end-users can move to it too.