Enable IPv6
in 2013 it is way time to add IPv6 support to every things we connect to the Internet.
This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.
Page 3 / 3
I was wondering what the status is of Sonos supporting IP v6.
"Starting June 1, 2016 all apps submitted to the App Store must support IPv6-only networking."
https://developer.apple.com/news/?id=05042016a
What does this mean for updates to the official Sonos App? Probably Apple will reject it? It depends on how hard coded IPv4 is implemented.
(and this goes for all the 3rd party apps such as my little project SonoControls https://itunes.apple.com/app/sonocontrols-controller-widget/id1082647737?mt=8). After all, the only way 3rd party apps can connect to Sonos devices is with a fixed IPv4 address.
Also, there is a risk that IoT apps / universal remote Apps that now support Sonos, will drop Sonos support as soon as they find out that Apple rejects their App updates for using fixed IPv4 addresses.
Again, not sure how strict Apple will be with this, but the Apple documentation link I posted suggests this will probably be reason for rejection.
Apple will not remove apps, but will reject App updates in such cases.
"Starting June 1, 2016 all apps submitted to the App Store must support IPv6-only networking."
https://developer.apple.com/news/?id=05042016a
What does this mean for updates to the official Sonos App? Probably Apple will reject it? It depends on how hard coded IPv4 is implemented.
(and this goes for all the 3rd party apps such as my little project SonoControls https://itunes.apple.com/app/sonocontrols-controller-widget/id1082647737?mt=8). After all, the only way 3rd party apps can connect to Sonos devices is with a fixed IPv4 address.
Also, there is a risk that IoT apps / universal remote Apps that now support Sonos, will drop Sonos support as soon as they find out that Apple rejects their App updates for using fixed IPv4 addresses.
Again, not sure how strict Apple will be with this, but the Apple documentation link I posted suggests this will probably be reason for rejection.
Apple will not remove apps, but will reject App updates in such cases.
Although I'm all in favor of IPv6 support, having IPv6 connectivity to internet doesn't restrict you from using IPv4 locally. I would assume that the Apple rules applies primarily for internet facing network traffic, and not necessarily for local traffic.
However, with that setup (having only IPv6 as internet connectivity), streaming services would probably struggle to function, since there are no IPv6 stack on the players. That will be a much bigger problem for Sonos. Having to rely on v4->v6 bridging in a local router or with your ISP is not a pleasant situation to be in.
However, with that setup (having only IPv6 as internet connectivity), streaming services would probably struggle to function, since there are no IPv6 stack on the players. That will be a much bigger problem for Sonos. Having to rely on v4->v6 bridging in a local router or with your ISP is not a pleasant situation to be in.
My experience with Apple and App Store guidelines: they have rules and there is no room for "but surely you see my situation is just a bit different" arguments. You either stick to Apple's rules or get rejected. But then again, if a lot of big brands are not ready for IPv6 only, Apple might be more flexible. We will have to wait and see.
Perhaps this is something the Sonos iOS app team knows more about...?
Updated. From https://developer.apple.com/library/ios/documentation/NetworkingInternetWeb/Conceptual/NetworkingOverview/UnderstandingandPreparingfortheIPv6Transition/UnderstandingandPreparingfortheIPv6Transition.html
"Some apps also pass the SCNetworkReachabilityCreateWithAddress method an IPv4 address of 169.254.0.0, a self-assigned link-local address, to check for an active Wi-Fi connection. To check for Wi-Fi or cellular connectivity, look for the network reachability flag kSCNetworkReachabilityFlagsIsWWAN instead."
To me this reads as: "if you are using a fixed IPv4 address, even only to check something on your local network: too bad, you have to fix this as well.". We'll see.
Userlevel 7
+21
Halfway through the year... some updates on deployment around the world over the past 6 months...
- The US is up to just shy of 29% of users using IPv6. Of the top 500 sites in the US as per Alexa, 56 are now using IPv6 (up 10), with another 6 under construction/testing.
- Canada has moved up almost 2% to 8.8% of users using it.
- Germany has moved up almost 4% to 23.7% of users.
- Belgium is up to 43.4% of users...
- The Netherlands has moved up about 2.5% to 6.3% of users.
- Portugal has increased almost 2% to 21.7%.
- The UK has made a BIG jump of over 10%, with almost 13% of users using IPv6.
- Norway's at about 7% of users with IPv6.
- France has over 11% of users with IPv6.
- Ireland has 7.25%...
- Greece continues its roll with over 4% growth to 23.4%
- Japan's up over 2.5% to 11.6%...
Not sure how many Sonos customers there might be in Saudi Arabia, Oman, India, and Pakistan, but over 70% of the transit networks in those countries have IPv6 in place, meaning big jumps in user counts could be coming. A good many European countries have already passed this point (some at 80% or higher even!) so growth in IPv6 use is not slowing down at all. BTW, for comparison, the US has about 65% of its transit networks supporting IPv6. Of course, keep in mind how many providers and networks there are in the US versus the rest of the world.
- The US is up to just shy of 29% of users using IPv6. Of the top 500 sites in the US as per Alexa, 56 are now using IPv6 (up 10), with another 6 under construction/testing.
- Canada has moved up almost 2% to 8.8% of users using it.
- Germany has moved up almost 4% to 23.7% of users.
- Belgium is up to 43.4% of users...
- The Netherlands has moved up about 2.5% to 6.3% of users.
- Portugal has increased almost 2% to 21.7%.
- The UK has made a BIG jump of over 10%, with almost 13% of users using IPv6.
- Norway's at about 7% of users with IPv6.
- France has over 11% of users with IPv6.
- Ireland has 7.25%...
- Greece continues its roll with over 4% growth to 23.4%
- Japan's up over 2.5% to 11.6%...
Not sure how many Sonos customers there might be in Saudi Arabia, Oman, India, and Pakistan, but over 70% of the transit networks in those countries have IPv6 in place, meaning big jumps in user counts could be coming. A good many European countries have already passed this point (some at 80% or higher even!) so growth in IPv6 use is not slowing down at all. BTW, for comparison, the US has about 65% of its transit networks supporting IPv6. Of course, keep in mind how many providers and networks there are in the US versus the rest of the world.
I am looking to replace my current Squeezebox setup, as that ship has sailed. However, I have an IPv6-only CIFS share over the Internet. It does have IPv4, but it is not reachable over IPv4 publicly. So I need the Sonos to be able to connect to IPv6 for CIFS. I dont care so much about IPv6 audio streams.
I dont fully understand how Sonos works (eg. what is the CIFS client, is it the Sonos device, or is it the App controlling it?). Can someone tell me if he CIFS client supports IPv6?
If not, any ideas on when this will be supported? Sonos would be useless for me until that time.
I dont fully understand how Sonos works (eg. what is the CIFS client, is it the Sonos device, or is it the App controlling it?). Can someone tell me if he CIFS client supports IPv6?
If not, any ideas on when this will be supported? Sonos would be useless for me until that time.
Userlevel 7
+21
The CIFS device would be the actual Sonos speaker/player, not the controller. Sonos speakers/players do not currently support IPv6. Sonos has made no indication of plans to support IPv6 at this time.
That is just sad 😞
IPv6 is faster than IPv4 (mostly because your carrier isn't intercepting your traffic and violating your privacy).
https://labs.ripe.net/Members/gih/examining-ipv6-performance
https://labs.ripe.net/Members/gih/examining-ipv6-performance
https://labs.ripe.net/Members/gih/examining-ipv6-performance
Whether or not ISPs intercept, that piece hardly bears out the 'IPv6 is faster than IPv4' claim:
Conclusion
What can we conclude about relative performance of IPv6 to IPv4 from these measurements?
These measurements show that in a large set of 1:1 individual comparisons where the IPv4 and IPv6 paths between the same two dual stack endpoints are compared, the two protocols, as measured by the TCP SYN round trip time, are roughly equivalent. The measurements are within 10ms of each other 60% of the time.
While the connection performance is roughly equivalent once the connection is established, the probability of establishing the connection is not the same. The current connection failure rate for IPv4 connections was seen to be some 0.2% of all connection attempts, while the equivalent connection failure rate for unicast IPv6 is nine times higher, at 1.8% of all connection attempts.
There is still some scope for improvement here.
My own experience of running a dual stack for the last couple of years is that there is no obvious performance difference (approximately 25% of my Internet traffic is now IPv6). Part of that, of course, is that unlike most consumer routers my router is quite pokey and can handle IPv4 NAT without impacting performance much.
At some point in the future, as IPv4 becomes more scarce and hosting sites increasingly can only get IPv6 addresses, it's likely that IPv4 traffic will continues to be supported using proxy/nat devices (either in the ISP network or on the customer router). At this point, it's entirely possible that IPv4 will start to become significantly slower than IPv6.
It is very important to note that I'm talking specifically about Internet traffic here, not about private network traffic. It is fully possible to continue to use IPv4 within your home/office network for the foreseeable future even if your Internet service becomes IPv6 only. In this case your gateway router would continue to perform IPv4 to IPv6 NAT. Of course there some disadvantages to this: NAT breaks many protocols, increases latency and limits throughput. Especially on typical home routers (which are almost always underpowered) IPv4 to IPv6 NAT will start to become a limitation.
This will take time and mainstream networks and services are not at that stage yet. Realistically it's likely to be years away. However, I would personally prefer Sonos address this sooner rather than later as I reckon there's a lot of problems that need to be identified and ironed out, and I'm sure most of the IPv6 early adopters would be keen to help debug some of these scenarios.
Part of the problem, I suspect, is I don't think there are currently many (if any) Music Services which support IPv6 and, as this is likely to be the first major IPv6 issue Sonos has to solve, it's a bit of a chicken-and-egg situation as there is nothing for Sonos to do tests against.
Cheers,
Keith
At some point in the future, as IPv4 becomes more scarce and hosting sites increasingly can only get IPv6 addresses, it's likely that IPv4 traffic will continues to be supported using proxy/nat devices (either in the ISP network or on the customer router). At this point, it's entirely possible that IPv4 will start to become significantly slower than IPv6.
It is very important to note that I'm talking specifically about Internet traffic here, not about private network traffic. It is fully possible to continue to use IPv4 within your home/office network for the foreseeable future even if your Internet service becomes IPv6 only. In this case your gateway router would continue to perform IPv4 to IPv6 NAT. Of course there some disadvantages to this: NAT breaks many protocols, increases latency and limits throughput. Especially on typical home routers (which are almost always underpowered) IPv4 to IPv6 NAT will start to become a limitation.
This will take time and mainstream networks and services are not at that stage yet. Realistically it's likely to be years away. However, I would personally prefer Sonos address this sooner rather than later as I reckon there's a lot of problems that need to be identified and ironed out, and I'm sure most of the IPv6 early adopters would be keen to help debug some of these scenarios.
Part of the problem, I suspect, is I don't think there are currently many (if any) Music Services which support IPv6 and, as this is likely to be the first major IPv6 issue Sonos has to solve, it's a bit of a chicken-and-egg situation as there is nothing for Sonos to do tests against.
Cheers,
Keith
Userlevel 7
+21
SOO... a post over in the Plex forum for Sonos just made an AWESOME case for IPv6 on Sonos...
Right now, in order for Plex and Sonos to work, it needs to use a port forward in the router, which allows Plex's cloud servers to make a connection back to the Plex server on your LAN. The problem is that with IPv4, those Plex servers are telling Sonos to play music from your router's WAN address, and some routers don't handle that kind of request - a WAN address request from a LAN device - gracefully, causing no connection to be made and no music to be played.
BUT... if Sonos supported IPv6 and were connected to an IPv6 network... instead of a port forward, just a firewall rule would be needed to allow the Plex cloud servers to talk to the Plex server, and Sonos and the local Plex server would be able to communicate directly since the Plex server's direct global IPv6 address would be given to Sonos instead of the WAN address of the router. Both devices are on the same network, communicating directly with each other without needing to go out to the router, then back into the LAN.
Now, I know Plex is an unusual circumstance since it's a media server running on a local network, and data about that server needs to be retrieved by Sonos from Plex's cloud servers in order for the connection to be made... but it's just another example of how IPv6 could be beneficial.
Oh... and while I'm here... I did some looking at the IPv6 numbers since my last update at the beginning of July... this is definitely the year of IPv6 growth so far. I won't update anything now... my next post for that will be in late December... but I'm really happy to see the levels of growth around the world that are being seen!
Right now, in order for Plex and Sonos to work, it needs to use a port forward in the router, which allows Plex's cloud servers to make a connection back to the Plex server on your LAN. The problem is that with IPv4, those Plex servers are telling Sonos to play music from your router's WAN address, and some routers don't handle that kind of request - a WAN address request from a LAN device - gracefully, causing no connection to be made and no music to be played.
BUT... if Sonos supported IPv6 and were connected to an IPv6 network... instead of a port forward, just a firewall rule would be needed to allow the Plex cloud servers to talk to the Plex server, and Sonos and the local Plex server would be able to communicate directly since the Plex server's direct global IPv6 address would be given to Sonos instead of the WAN address of the router. Both devices are on the same network, communicating directly with each other without needing to go out to the router, then back into the LAN.
Now, I know Plex is an unusual circumstance since it's a media server running on a local network, and data about that server needs to be retrieved by Sonos from Plex's cloud servers in order for the connection to be made... but it's just another example of how IPv6 could be beneficial.
Oh... and while I'm here... I did some looking at the IPv6 numbers since my last update at the beginning of July... this is definitely the year of IPv6 growth so far. I won't update anything now... my next post for that will be in late December... but I'm really happy to see the levels of growth around the world that are being seen!
Userlevel 7
+21
While it's on my mind... A tweet last night from Comcast's VP of internet service about Sky's IPv6 rollout in the UK caught my eye. Apparently Sky is 90% complete upgrading customers' gateways to support IPv6, allowing millions in the UK to now access sites and services with the new protocol from their home broadband connections.
Coincidentally, since my last check in July, the percentage of UK users using IPv6 has increased 50% over where it was just 2 months ago (yeah, I'm gonna make you do some work and go back to page 2 to see where it was then, so you can figure out where it is now)! 😃
Coincidentally, since my last check in July, the percentage of UK users using IPv6 has increased 50% over where it was just 2 months ago (yeah, I'm gonna make you do some work and go back to page 2 to see where it was then, so you can figure out where it is now)! 😃
IPv6 is only 20 years old, why would Sonos need to support it? My ISP (Comcast) reports that over 50% of its traffic is IPv6. Most people who have it don't even know it is there because "it just works". Meanwhile Chromecast Audio and Google Home supports IPv6 just fine and is quickly catching up to Sonos in terms of services offered.
Userlevel 4
Your local network will remain on IPv4, as the home is never going to have enough devices that you need to go to IPv6. Again, the players will continue to function perfectly fine.
Wrong wrong wrong. My new home network was built IP6 native. v4 devices are in an translation ghetto.
Welcome to 2016.
Userlevel 7
+21
So yes, it's the end of the year... time for another look at how IPv6 use around the world continues to grow. As in the past, these numbers are based on the percentage of traffic to Google and its various services that is handled over IPv6.
- The US saw IPv6 use finish this year at just over 31%.
- Germany is finishing this year with over 27% of traffic using IPv6.
- Belgium IPv6 use grew almost 25% this year and is now over 48%.
- Japan is finishing 2016 with about 14.3%, almost 50% growth over the course of the year.
- Greece continues to significantly increase IPv6 use... up to 29.5% now, also growing about 50%.
- Switzerland is now over 30%.
- Sweden continues its slow climb with now over 3.2% of traffic using IPv6.
- Canadian IPv6 use more than doubled over the year, now up to about 16.3%.
- The Netherlands doubled their IPv6 use over the course of this year, going from 3.8% to over 8%!
- Brazil almost doubled their IPv6 use as well... going from 6.5% to 11.8%!
- But the BIG winner this year is the UK! They started 2016 at about 2.5%... but a major push by some ISPs there to get IPv6 going has resulted in an increase slightly over 680% this year, bringing them to just over 17%!
Other countries with growing IPv6 use include France (14.21%, up from 11% in June), Estonia (16.3%), Ireland (8%), Hungary (7.5%), Romania (7%), Czech Republic (10.8%), India (14%), Saudi Arabia (5.25%), Malaysia (12.3%), Ecuador (18.6%), Peru (15.8%).
A sure sign that IPv4's useful life is growing shorter is that the number of transactions involving transfer of addresses between companies has significantly increased, as companies look to offload the IPv4 addresses they no longer need and make some money from their sale to companies that are slow to adopt IPv6 and thus still need those IPv4 addresses to do business. There are actually companies dedicated to the IPv4 transfer market now, brokering deals between sellers and buyers!
It's time for Sonos to get into the 21st century of the internet and add IPv6 support!
- The US saw IPv6 use finish this year at just over 31%.
- Germany is finishing this year with over 27% of traffic using IPv6.
- Belgium IPv6 use grew almost 25% this year and is now over 48%.
- Japan is finishing 2016 with about 14.3%, almost 50% growth over the course of the year.
- Greece continues to significantly increase IPv6 use... up to 29.5% now, also growing about 50%.
- Switzerland is now over 30%.
- Sweden continues its slow climb with now over 3.2% of traffic using IPv6.
- Canadian IPv6 use more than doubled over the year, now up to about 16.3%.
- The Netherlands doubled their IPv6 use over the course of this year, going from 3.8% to over 8%!
- Brazil almost doubled their IPv6 use as well... going from 6.5% to 11.8%!
- But the BIG winner this year is the UK! They started 2016 at about 2.5%... but a major push by some ISPs there to get IPv6 going has resulted in an increase slightly over 680% this year, bringing them to just over 17%!
Other countries with growing IPv6 use include France (14.21%, up from 11% in June), Estonia (16.3%), Ireland (8%), Hungary (7.5%), Romania (7%), Czech Republic (10.8%), India (14%), Saudi Arabia (5.25%), Malaysia (12.3%), Ecuador (18.6%), Peru (15.8%).
A sure sign that IPv4's useful life is growing shorter is that the number of transactions involving transfer of addresses between companies has significantly increased, as companies look to offload the IPv4 addresses they no longer need and make some money from their sale to companies that are slow to adopt IPv6 and thus still need those IPv4 addresses to do business. There are actually companies dedicated to the IPv4 transfer market now, brokering deals between sellers and buyers!
It's time for Sonos to get into the 21st century of the internet and add IPv6 support!
ignore! 😃
Userlevel 7
+21
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
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
Userlevel 7
+21
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. 🙂
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.
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.
Userlevel 7
+21
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).
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).
Userlevel 7
+22
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.
That also answers some of my issues with strange stuff IPv6 stuff showing up on my LAN.
Page 3 / 3
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.