Enable IPv6

So, it's been a while since I've done an "IPv6 Around the World" post... just over a year and four months... and it looks like lots of growth has gone on in that time in many countries.

The US is up to 34% of users using IPv6, 97M users
Canada is nearing 19%, 6M users
Germany is up to 36% of users using IPv6, 26M users
Belgium is just over 50% of users using IPv6, 5M users
France added another 50% from my last number, to bring them over 21%, 12M users
The UK has increased up to 20% of users using IPv6, 12M users
The Netherlands added over 50% of their previous number, now at almost 13%, 2M users
Ireland has doubled the percentage of their users using IPv6, over 16%
Sweden has more than doubled their user count, up to 6.8%

In fact, Europe in general has seen some pretty big growth in IPv6 over the past 16 months... some countries I didn't even put numbers down for previously now seem to have some pretty significant deployments. Norway and Finland I didn't even list before, and they're at 14% and almost 20% respectively... Poland is at over 8%... Hungary is almost at 12%... and back to list form for other parts of the world. :)

India has almost doubled their IPv6 user percentage in the past year and a half... they're at 26% now (over 125M users!)
Japan is over 24% now, over 28M people
China's percentage seems low, but almost 3.6% of their population is using IPv6, meaning over 26M people
Malaysia has doubled their IPv6 user percentage, now over 25%, 5.5M users
Saudi Arabia is just shy of doubling their number over the past 16 months... 10.2% now, 2.2M users
Down under, Australia and New Zealand are at 14% and 16% (~3M and 675K users) respectively
Brazil has more than doubled their IPv6 user reach, now over 24% (34M users)
Peru and Ecuador are at over 15% and 20% (2M and 1.4M users) respectively.

Visit the Cisco 6Lab for maps, charts, and more... http://6lab.cisco.com/stats
And see if you might be using IPv6 and didn't even know it... http://www.test-ipv6.com

I can do IPv4, anything I need done with it is easy and painless.

IPv6 has eaten hundreds of hours of my time and a lot of time from support folks too, just trying to get a bit beyond the very basic stuff up and running. Reserved IP addresses via DHCP6 in particular has been bringing me to tears. The best suggestions for tracking down systems involve WireShark and additional subnets on my router to try to isolate the suspects. I've gotten about 1/3 tracked and assigned but that last big batch just aren't cooperating.

If you just want to grab a consumer grade router and user device and slap them on the net IPv6 is pretty much invisible but going beyond that is not an easy task.

A landmark statistic was reached yesterday for a large and well-known site that uses IPv6. Obviously this statistic is limited to users of this particular site, but it's a pretty far-reaching site. 🙂

Yesterday (May 27), for the first time, over 50% of US Facebook users (50.75%) were connecting to the site over IPv6.

Just a couple of additional numbers...
49.99% of Facebook users in India were using IPv6 two days ago.
41.76% of Facebook users in Germany (5/1; 41.66% 5/27)...
54.8% of Facebook users in Belgium (5/21; 54.4% 5/27)...

Source: Facebook IPv6 Statistics

Stanley, regarding DHCPv6, you're right that it's not anywhere near as easy to set up as DHCPv4 is... send me a PM and I'll see if I can help you out with it. That's kinda off-topic here. 🙂

I just checked the ifconfig output from both of my new One units, and they're reporting addresses from the LL and my ULA and Global prefixes on their br0 interfaces. The ULA and Global host suffixes are basic universal EUI-64 derived addresses.

The HTTP daemon doesn't appear to be listening on any v6 address; at least on ports 80, 443 and 1400. The global address responds to ICMPv6 echo requests. A simple nmap scan doesn't reveal anything interesting.

They're not doing anything via DHCPv6, and the RA daemon is ignoring my RDNSS headers (/etc/resolv.conf only includes the v4 resolver addresses from DHCP).

The /tools.htm page also includes fields for ping6 and traceroute6.

At a minimum, I'd expect the EUI-64 host suffix for global prefixes to be disabled and replaced with a RFC 4941 privacy address.

Well that's a positive development here... I have to wonder if maybe Google might be behind a push for IPv6 support... Google makes big use of IPv6, and with Google Assistant support coming later this year... :)

Hopefully, though, Sonos doesn't take the Google/Android approach to IPv6 and leave out support for DHCPv6 in the end. I don't run SLAAC on my main network (too messy with all the random "privacy" addresses - they still know your devices are all coming from the same network), and such a decision might also further impair business use of Sonos (businesses like control over what's on their network).

Interesting, I just looked through my gear and am seeing IPv6 addresses for my fairly new Play 1s and my Play 5 gen2 but not my older Zone Player 80s, Boost, Play 3s or my gen 1 Play 5s.

That also answers some of my issues with strange stuff IPv6 stuff showing up on my LAN.

It could have something to do with Airplay maybe... because only my Sonos One speakers have IPv6 addresses (though only link-local, as I mentioned before that I'm using DHCPv6)... and my other speakers, which are known to not support Airplay, don't have IPv6 addresses.

I'm seeing this from my Gen 2 Play 5 and similar from my two new Play 1 speakers, not the fancy Ones.

ath0 inet6 addr: fe80::XXXX:fef8:b31f/64 Scope:Link

br0 inet6 addr: fe80::XXXX:fef8:b31e/64 Scope:Link
inet6 addr: 2600:XXXX:5701:5eaa:fdff:fef8:b31e/64 Scope:Global

Unlike IPv4, IPv6 interfaces can, and will typically, have multiple addresses configured.

IPv6 addresses beginning with:

• FE80: are Link Local (LL). Every interface configured for IPv6 will have at least one.
• FDxx: are Unique Local Addresses (ULA), and are loosely analogous with RFC1918 IPv4 private address ranges (10/8, 172.16/12 and 192.168/16). They're designed to be routable within an organisation, but must be filtered by gateways connecting to the outside.
• 2xxx: or 3xxx: are globally routable. These addresses allow end-to-end connectivity. across the internet. This will be expanded if the 2000:/3 range is exhausted.

The br0 addresses are the ones that matter, at least in a SonosNet system. It's possible that in a non-SonosNet setup the ath0 interface could have a global address instead, since it would only be using the WiFi connection... that might explain why it also has a link-local address.

Interesting though that you're seeing it on a newer Play:1 (which I completely missed earlier)... guess that blows away my theory on it being for Airplay.