After I switched ISP to one that supports native IPv6 (and generally is pure awesome), I noticed that my traffic at home went to about 50% IPv6, also thanks to YouTube supporting V6.
I also casually noticed that all but one address in my "Account Activity" view in Gmail are IPv6 addresses (ironically, the mobile phone got the one single IPv4 address in that list over 4G).
V6 works nicely and totally transparent causing zero trouble for me, even though there are some application protocols that don't handle V6 properly yet (Apple Remote Desktop and Air Video to give two examples).
One thing that's tricky about V6 is the fact that without NAT all your boxes are internet-reachable unless you have a firewall. That's easily added of course, but whereas we have protocols like upnp and nat-pmp to reconfigure NAT routers, there's nothing equivalent for various applications to tell the router to forward some V6 traffic.
So this is actually a step back what connectivity behind LANs is concerned.
I would love for applications to be able to ask the OS for their very own application specific v6 address. Then they could just listen on that instead of all interfaces (and listening on all interfaces would not include these application specific interfaces).
That way, I could theoretically get away without a restrictive firewall while still giving applications a way to be directly connected to. An attacker would have to scan a /48 (in my case) or a /64 (in the worst case) in order to find an open port given a known remote address.
I'd be very interested in knowing how these stats were calculated - 12% of the United States on IPv6 seems a bit high. Maybe what Google is saying is that "It's Available, but we're not saying people are using it." - For example, Comcast has had IPv6 widely deployed for at least a year, so most of their customer might be identified as "Available" - even if their browsers aren't doing a AAAA lookup for www.google.com.
In Austria not having IPV6 support is a feature, and I assume it's that way in many countries. If an ISP rolls out IPv6 for you here you lose your public IPv4 address (DS-Lite).
Out of curiosity (I live in the UK, a country that does not believe in adopting new technologies less than 5y after everyone else), with IPv6, there is no need for a NAT anymore. Will the local networks be directly on the WAN? Will be interesting from a security/privacy point of view. Unless routers act as firewall, in which case we are back to square 1...
Can somebody explain how Belgium achieved 28%? It's the only country that's colored bright green.
I've looked around and I can't find one ISP that "support" ipv6 in Sweden. The big ones alway replies with "We have enough ipv4 addresses for a long time forward, you don't have to worry."
I'm not worried, I just want to have ipv6 access.
IPv6 became available to me on my Comcast connection in the past six months, but I ended up disabling it at my local router. Unfortunately it seems in my area (North of Boston, MA) the IPv6 routing on Comcast's network is extremely spotty. Sometimes connections would time out on all different ports (22, 80, 443). This lead to a rather poor experience for members of my household. I ran into lots of issues with SSH. My wife ran into lots of issues using apps on her iPhone. She was switching to her mobile data connection on a regular basis to work around the issue. Since disabling IPv6 on our network, all of the issues have gone away.
I've been trying on and off to get IPv6 working at home, but the problem I keep running into is poor performance from tunnels. I have service via Wide Open West which is great for IPv4, but they have no plans to support IPv6. So, I try using a tunnel...
Both HE.net and SixXS are so incredibly slow that I get >1 second pings to something which is 30ms away via IPv4. The tunnel end point is only ~50ms away, so I can only see the latency as being within the tunnel provider...
I really, really wish that I had a native IPv6 connection at home, but I don't want to switch to Comcast, which is the only IPv6 option for me.
My ISP supports IPv6, but I deactivated it.
The reason: https://blog.dave.io/2011/06/vpn-ipv6-privacy/
It's kind of ironic that the graph about embracing future technology requires Flash Player.
How much time pressure are we under to replace IP4 with IP6? Is this something that has to be done in 2 years or 10 years?
Anyone know what that weird spike was in the first week of October 4?
I wouldn't be surprised if that 1.36% in Ireland was almost solely down to the hosting company I work for.
I really wish the hosting providers here would get their acts together when it comes to IPv6 deployment, but they're really dragging their heels on it. I recently got a VDSL connection from Magnet and while I've a static IPv4 address for the connection, no such luck for IPv6.
I'm curious about the peaks and troughs in the graph. It seems the graph reaches a peak every week, does anyone know a reason for this?
In Germany, Kabel Deutschland, no longer offers ipv4. At least, My router only gets an ipv6 one. (100/6Mb + phone line = 55 eur)
Can IPv6 become, ironically, the reason ipv4 never dies? Once a majority move to v6 wouldn't that mean a whole bunch of the ipv4 space is being free'd up.
This allows those who never update to actually never update.
Doesn't IPv6 also mean the permanent death of privacy? Think about it. IPv6 kills all the stupid NAT schemes IPv4 required. Everyone gets a permanent static IP address. Your browser delivers it to every site you visit. It's the ultimate permanent cookie. Of course Google is so happy for this.
How come some countries have a negative -10ms *latency?
Every time IPv6 comes up on HN, around 50% of the comments seem to be about how IPv6 doesn't do NAT and how now every device you have is suddenly directly exposed to the internet. Let's clarify this a bit instead of answering individual commenters:
In IPv6, just like in IPv4, you have a firewall. In Linux, you use ip6tables instead iptables, for example. This is what keeps your devices on your network safe. If you were to start from scratch to set up a router with an IPv6 firewall, you'd need just two rules: (1) allow packets in for already established connections and (2) drop every other incoming packet. If you know what you are doing, you can actually set this up yourself. I have, and while educational, it provided no real world benefit.
Most people don't want to bother with using iptables directly, so don't. Get a router that supports OpenWRT and flash it. For most of them, it's a really simple process (my TP-Link let me upload the binary to flash via the web GUI). Why OpenWRT? Well, it's secure and constantly updated, it supports IPv6 natively, and it comes with the IPv6 firewall that is configured in a fashion very similar to how you think of IPv4 (it even rate limits ping requests, etc.). As a bonus, if your ISP doesn't support IPv6, OpenWRT has an installable web GUI component for configuring an IPv6 tunnel. Lastly, even if you don't want IPv6 (yes, I see you there in the back, climbing back under your rock), still use OpenWRT. It seems to have a lot less bugs than commercial router firmware, and is a lot more stable and up to date than DD-WRT or Tomato.
Edit: One other misconception that comes up frequently is that IPv6 means that your privacy is at a more of a risk because your MAC address may be exposed. While in some configurations this can happen, IPv6 has what's called Privacy Extensions: in addition to your more permanent MAC-based IPv6 address (network prefix + munged MAC address), your OS will periodically generate a new random IPv6 address (network prefix + random number). This actually makes it marginally harder to track you since your exact IP address will change frequently, as seen by hosts you access. See http://en.wikipedia.org/wiki/IPv6#Privacy.