Live data from Hacker News

More than 1/3 of all access to Google is now over IPv6

google.com

1–10 of 237 posts

Re: More than 1/3 of all access to Google is now over IPv6

#4
It's a perquisite for tagging individuals.

IPv4 not having enough addresses is a good thing.

With IPv6 identification (and therefore control) can be down to the person globally, but IPv4 forces NAT's. The inability to label all the things is a feature. NAT's are borders; they prevent fine grained censorship without larger consequences.

  $ zcat /proc/config.gz | grep -i ipv6
  # CONFIG_IPV6 is not set

Re: More than 1/3 of all access to Google is now over IPv6

#5
post #4

It's a perquisite for tagging individuals. IPv4 not having enough addresses is a good thing. With IPv6 identification (and therefore control) can be down to the person globally, but IPv4 forces NAT's. The inability to label all the things is a feature. NAT's are borders; they prevent fine grained censorship without larger consequences. $ zcat /proc/config.gz | grep -i ipv6 # CONFIG_IPV6 is not set

Not just tagging many ISPs especially FTTH/P don’t randomize IPv6 addresses so all the IP addresses in your town, neighborhood and even building share the same prefixes and they are hierarchical so by just knowing your IP address one could figure out where you live.

Re: More than 1/3 of all access to Google is now over IPv6

#6
post #4

It's a perquisite for tagging individuals. IPv4 not having enough addresses is a good thing. With IPv6 identification (and therefore control) can be down to the person globally, but IPv4 forces NAT's. The inability to label all the things is a feature. NAT's are borders; they prevent fine grained censorship without larger consequences. $ zcat /proc/config.gz | grep -i ipv6 # CONFIG_IPV6 is not set

IPv6 still has NAT. There's public and private IPv6 addresses, same as IPv4.

Google building their infrastructure around IPv6 does not have anything with tracking IPv6 users

Re: More than 1/3 of all access to Google is now over IPv6

#7
post #4

It's a perquisite for tagging individuals. IPv4 not having enough addresses is a good thing. With IPv6 identification (and therefore control) can be down to the person globally, but IPv4 forces NAT's. The inability to label all the things is a feature. NAT's are borders; they prevent fine grained censorship without larger consequences. $ zcat /proc/config.gz | grep -i ipv6 # CONFIG_IPV6 is not set

Nearly all modern operating systems use the IPv6 privacy extension, which creates random addresses periodically. Thus the tracking is randomized to the /64 (which is an end customer). This is more or less the same as with IPv4 (without CGNAT)

Re: More than 1/3 of all access to Google is now over IPv6

#8
The graph is interesting when you zoom in, much more IPv6 use over the holiday period and also recently during the period of lockdown measures. I would guess the majority of IPv6 traffic comes from devices on 4G networks. More devices are on 4G when visiting family and friends over the Christmas period and when working remotely.

Re: More than 1/3 of all access to Google is now over IPv6

#9
post #8

The graph is interesting when you zoom in, much more IPv6 use over the holiday period and also recently during the period of lockdown measures. I would guess the majority of IPv6 traffic comes from devices on 4G networks. More devices are on 4G when visiting family and friends over the Christmas period and when working remotely.

IPv6 is much less common on enterprise networks (old firewall which don't support v6 still).

Re: More than 1/3 of all access to Google is now over IPv6

#10
post #7
post #4

It's a perquisite for tagging individuals. IPv4 not having enough addresses is a good thing. With IPv6 identification (and therefore control) can be down to the person globally, but IPv4 forces NAT's. The inability to label all the things is a feature. NAT's are borders; they prevent fine grained censorship without larger consequences. $ zcat /proc/config.gz | grep -i ipv6 # CONFIG_IPV6 is not set

Nearly all modern operating systems use the IPv6 privacy extension, which creates random addresses periodically. Thus the tracking is randomized to the /64 (which is an end customer). This is more or less the same as with IPv4 (without CGNAT)

Irrelevant. It's within your subnet, and it's nowhere near 32b.

https://www.transtutors.com/questions/how-many-bits-are-need...

Post reply on HN