Re: Try getting IPv6 from any major ISP's.
IPv6 tunnels still work. I'm using one from he.net - but of course THOSE are given away for free by an ISP that's just being nice. there are other free tunnel services as well [captain obvious says: no need to thank me, I'm not being helpful] and so it's just a matter of setting one up, which requires following somewhat detailed instructions for your OS of choice.
now there ARE some *NEW* headaches that IPv6 is likely to cause:
1. Your windows machine NOW has a publically viewable IPv6 address, even though you were accustomed to being behind a Linux-based NAT firewall. This is a lot like leaving your bedroom window unlocked with the curtains drawn...
2. ANY IPv6-capable web site can discover your publically viewable IPv6 address, including rogue ad servers, CDN networks, Facebitch, and web servers with "invisible" gif images embedded into any web page.
3. tracking you via a FIXED IP ADDRESS is now "that much easier". Each IPv6 subscriber is likely to get a netblock of addresses. there are more than enough. That net block NOW identifies YOU. Even if the IPv6 changes, if only the last 8 to 16 bits are changing, it's still "you".
[yes I know all 3 already apply to me, but I've dealt with it]
Keep in mind that every windows version since XP has had "magic internal stuff" listening on well-known ports, every time you boot up. Try "netstat -an" in a CMD window some time, you'll see what I mean. Every one of those UDP ports marked '*:*', every one of those 'LISTENING' TCP ports, they're ALL open to being CRACKED. All you need is a pile of already-cracked machines [remember 'code red' ? win-nuke?] banging away against random IPv6 addresses, and you'll get infected or DoS'd, eventually, if you're running an unfirewalled windows machine.
The solution, of course, is to have a firewall that is INTELLIGENT enough to block these ports PROPERLY by default, and I'm not talking about the Windows firewall, I'm talking about a PROPER firewall, like a router running Linux. It also needs to properly support IPv6 routing, AND to be "shut offable" if you have something OTHER than "that box" doing the routing [which _I_ happen to have].
And that's another headache for the ISPs: dealing with customers that aren't using "their box", are using some form of 'bridge mode', already have an IPv6 tunnel, and somehow PROTECTING all of those clueless windows users from getting their machines cracked because they're NOW publically visible. And if it has an easily guessed user/pass, you now have remote access capability.
maybe the biggest problem in the way of IPv6 is MICRO-SHAFT and WINDOWS ???