Live data from Hacker News

IPv6 Adoption Statistics

google.com

51–60 of 134 posts

Re: IPv6 Adoption Statistics

#51
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.

Re: IPv6 Adoption Statistics

#52

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.

Unlikely. It's difficult to remove the last v4-only device from a network. Much easier to just leave the migration at 90, 95 or 99% complete and keep the v4 addresses.

Re: IPv6 Adoption Statistics

#53

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.

That's why OSes use privacy addresses.

Re: IPv6 Adoption Statistics

#54
post #41

Earlier quoted context omitted.

Isn't it easy enough to just have a local firewall on each machine where you open up ports for the apps you want to be public?

The firewall on a local machine might suffer from exploits, thus still allowing access. Or I might want some services open to my lan and only a smaller subset opened to the public (something the personal firewalls built into many OSes can't do)

> The firewall on a local machine might suffer from exploits, thus still allowing access.

Is a updated firewall from Apple, Microsoft or ipfw more or less likely to suffer from exploits than a cut-rate device from ASUS, Netgear or Linksys that hasn't been updated in years?

> Or I might want some services open to my lan and only a smaller subset opened to the public (something the personal firewalls built into many OSes can't do)

That may be fair enough but that's just a reason to improve the firewalls in the OSes. As soon as you tether to your phone or use public WiFi you're going to want a solid local firewall anyhow.

Re: IPv6 Adoption Statistics

#55

My ISP supports IPv6, but I deactivated it. The reason: https://blog.dave.io/2011/06/vpn-ipv6-privacy/

Leaks are a problem and people are working on it[1] but you could reconfigure your VPN to carry IPv6 traffic, too. At least OpenVPN is capable of it[2].

It's also a bit of an edge case. Browser-level proxying (Tor, SOCKS proxies) shouldn't leak whereas for p2p/torrent it makes more sense to run the client itself on a remote server rather than route traffic through it.

[1] https://leap.se/en/services/eip

[2] https://community.openvpn.net/openvpn/wiki/IPv6#ProvidingIPv...

Re: IPv6 Adoption Statistics

#56

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.

Not in the least. For all their atrocities, Comcast was one of the early IPv6 adopters and has rolled it out to their entire residential customer base (people with older modems/routers that don't support IPv6 obviously won't pull an IPv6 IP address). That's EASILY 11% of US internet traffic.

Re: IPv6 Adoption Statistics

#57

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.

http://en.wikipedia.org/wiki/IPv6#Privacy

  When privacy extensions are enabled, the operating system 
  generates random host identifiers to combine with the 
  assigned network prefix


  Privacy extensions are enabled by default in Windows 
  (since XP SP1), OS X (since 10.7), and iOS (since version 
  4.3).[32][33] Some Linux distributions have enabled 
  privacy extensions as well.[34]

Re: IPv6 Adoption Statistics

#58
post #53

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.

That's why OSes use privacy addresses.

Privacy addresses still come from the same /64 which works a lot like a single IPv4 for home deployments. So from the privacy perspective IPv6 is like giving every home router a static IPv4 address.

Of course, there is no technical requirement to make those addresses static. It's just how they're usually assigned because it's more convenient.

Re: IPv6 Adoption Statistics

#59

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.

No, you don't get a permanent static IP address. That depends on the ISP. And even if your ISP hands out permanent addresses, your devices can change addresses often. Most of my devices do change addresses, and I didn't have to turn it on.

Both v6 and the linux stack are privacy-friendly.

Re: IPv6 Adoption Statistics

#60
post #42

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…

I found that switching to googles DNS fixed those issues for me (I'm on the south shore).

There is still the occasional delay, but its similar to the ipv4 service from Comcast.

Post reply on HN