IPv6 support

What current Sonos features should the Sonos programmers remove from the current software to make room for the IPv6 software stack to be added? Or should Sonos just stop supporting any older Sonos gear that doesn't have room for the IPv6 software to be added, like they just did to the CR-100?

What advantage do you see to having IPv6 available to the Sonos gear?

Yup, agree with Stanley_4 here. I recently went through IPv6 enablement on my local network and connection through to my ISP. Took a bit of work but I got there. But I don't have a problem with stuff still running on IPv4 locally if it needs to through NAT to the outside world.

The main benefit that I could see for IPv6 internally was that it potentially makes routing and firewall setup simpler. The reality was very different to be honest and it was hard work. I run Amigas on my local network which are never going to be IPv6 (or at least I doubt it). I suppose I can sort of see a point to it if they are the only thing left on your network that is IPv4 and the whole of the internet is IPv6 and so nothing is using IPv4 any more but isn't that a long, long way off?

Also, to my way of thinking (and probably not correct) but the whole argument that the world has run out of IPv4 is a bit of a non point really isn't it? After all, with all these people going IPv6 it should be freeing up a lot of IPv4, shouldn't it? I guess people aren't releasing their IPv4 blocks back to the wild when they go IPv6.

Not likely initially, because they'll want to maintain compatibility with IPv4 users, and because every IPv4 address is automatically an IPv6 address with the proper prefix.

What current Sonos features should the Sonos programmers remove from the current software to make room for the IPv6 software stack to be added?

I don't see a reason why they'd have to take out features to "make room". My guess is it is already in the network stack, but disabled.

I'm more curious how they are able to get into the iOS App Store since they require apps to work in an IPv6-only environment. I guess they use the excuse that the app works fine, even though the hardware is useless.

IPv6 is here to stay, people should get with the times rather than resist.

I don't think that IPv6 is included by default in the Linux 2.x that Sonos is running, it is really old, so old it is no longer maintained by the Linux folks and (I believe) Sonos is having to backport anything new they want in it. You can of course check this yourself from the Sonos GPL releases page. Even if it is there in the source, if it is disabled it isn't generating code, which comes back to having to make room if it is enabled.

Sonos devices, particularly the older ones have very limited flash and RAM, you want something new, well something that is there now has to go to make room. Only other option is to stop supporting older gear which will make a lot more folks mad than the CR-100 mass disable did.

I'm guessing the Sonos techs would prioritize SMB newer than v1 over IPv6 in any case, that is actively causing users trouble today versus IPv4 which is still working just fine and will be for the foreseeable future as folks return unused and unwanted address blocks.

Of course I could be wrong and the Sonos folks could be a crew of Dogbert clones jerking us around for their evil amusement. That would suck but be kind of funny too. Hmmm, maybe they have Catbert running the support phones and forums?

...versus IPv4 which is still working just fine and will be for the foreseeable future as folks return unused and unwanted address blocks.
IPv4 addresses aren't being "returned"... they're being bought and sold through private brokers, being sold by companies and ISPs that are implementing IPv6 and CGNAT (so they don't need as many IPv4 addresses as they used to) and bought by companies like Amazon, Google, Microsoft, and other cloud service providers that need them to provide their customers with IPv4 addresses, since they can't get them from the IP address registry services (i.e. ARIN, RIPE, APNIC, etc.). That lets companies that don't need their IPv4 blocks get a bit of return on their investment for implementing IPv6 too.

Is it a super-urgent critical issue that needs to be fixed ASAP? In a small part of the world, yes. For the majority, not at this point. But it's only going to be used more and more as time goes on. As IPv6 growth continues, IPv4 eventually becomes a second-class citizen... first on some ISP's, but over time, even in the transit networks that keep things moving. The core IPv6 protocol is 20 years old this year. Additional major RFCs for enhancements and other protocols that use IPv6 were finalized as recent as 12 years ago. Some countries have as many as 1/5 to 1/4 of their internet users able to use IPv6... some even as high as 1/3!

And since it's been almost a year and a half since my last "IPv6 around the world" post in the other IPv6 topic (Enable IPv6), I just made another of those posts. 🙂

Several ISPs in Germany are switching to DS-Lite, only offering IPv6 access, even on the LAN. Is Sonos using 2.6 kernel or even older than that?

Sonos removed user access to a lot of internal information a few releases back so trying to sort out just what they are doing is far harder than it used to be. You'd have to dig into the GPL sources to see which base kernel they are using and what has been back-ported from newer kernels.

Several ISPs in Germany are switching to DS-Lite, only offering IPv6 access, even on the LAN.
DS-Lite encapsulates IPv4 traffic within IPv6, so there's generally no limitation on having IPv4-only devices on the internal LAN.

IPv6 is far from "everywhere". It is certainly uncommon on home networks, which is what Sonos connects to.

Even at my work (many 100s of thousands of devices) we are not IPv6-only.