In order to get Arc working in 2022 I had to phone my ISP and ask them to turn off IPV6 as per this post
Does anyone know if I now have to phone them up and ask them to reverse this and allow IPV6 or just leave well enough alone.
This must be one of the most user unfriendly notices from Roon possibly ever, it reads more as an It to IT communication.
.sjb
Hi, If you use your Virgin Media Ireland Router in āModem Modeā and bypass all the router & firewall functionality, it can be IPv4 only.
āModem Modeā is a much better option, as the router, firewall and WAP of the CSP equipment is quite poor, much better to provide your own WAN Router/Firewall and separate WAP.
But IPv4 only, but a good WAN router will allow the port based routing for Roon ARC, etc.
Hope you can clarify, because the info from roon on the upcoming change was confusing.
My local audio network is 100% ethernet. My iMac where both roon and HQP are hosted, is configured for IPv4. The IPv6 connectivity test scored 10/10.
Should I feel good about this or not?
Thank you.
Simple IPv4 governs IP addresses IPv4 has limited number of addresses and is fast running out.
IPv6 will provide an almost limitless number pu.
Indeed. My ISP has allocated me a fixed /56 prefix which means I have just ~4,700,000,000,000,000,000,000 IPv6 addresses available for my local network.
In IPv6, the smallest sub-net that allows autoconfiguration is a /64 sub-net with ~18,000,000,000,000,000,000 IP addresses. I can configure up to 256 such subnets within my allocated IPv6 address space.
I think that this should be enough for me - at least for now 
Interestingly, even the smaller of these two numbers is far in excess of the ~4,200,000,000 ipv4 addresses that can exist in total (without taking reserved and special purpose ranges into account). Thus a local IPv6 sub-net will support more devices than the entirety of the IPv4 network (without NAT).
2 posts were split to a new topic: This issue has now reappeared for me
Iām finding the ipv6 test results on my āRoon remotesā confusing (iPhone 12Pro and iPad 10th Gen, both running current iOS). Sometimes I get a 10/10, and sometimes 9/10 with the message ā Your DNS server (possibly run by your ISP) appears to have no access to the IPv6 Internet, or is not configured to use it. This may in the future restrict your ability to reach IPv6-only sites.ā
Does this mean I may have an issue when Roon makes the change?
Iām trying to be proactive as best as my limited knowledge allows in hope to avoid a nasty surprise when Roon makes its change.
Iāve confirmed that our internet provider supports ipv6.
Roonās message mentions concerns about āolder devicesā. Is my Salkstream III from 2016, which runs Roonserver on Arch Linux OS (OS is up to date), considered a older device? On the Arch Wiki page I found a command line to test if the Salkstream is compatible with ipv6, and it appeared to pass.
Will my old Logitech Squeezebox Touch being used as a Roon endpoint still work after the change?
I really hate this feeling that Roon has users (itās a mystery to me which usersā¦am I one?) counting down to see if they will be adversely affected or not.
I would suggest you leave it as is. If you have now got Arc working and a near flawless Roon experience, then let it be.
If things break (which never happens with Roon 
) then you might need to speak to them.
I think communication by Roon on this matter is totally inadequate. Iām under the impression that lots of people here have no idea what to expect or what to do.
And what about the users that do not participate on this forum? How many of them will be affected?
Wouldnāt it be possible for Roon to run some sort of testing script within a new release of Roon Server that sends a message to every individual user that states whether they will be affected and what to do?
This is solely to benefit Roon Labs trying to get Arc more reliable. Forget (other) longstanding issues.
From what I understand at the time of Arc being tested, it was advised by users they shouldnāt go down the road of port forwarding etc.
Look at all the issues revolving around that with CG-NAT and some users with less network knowledge than others.
I feel this move is in hope that itāll fix the issues.
Well, I feel not, as some ISPs donāt offer IPv6 but do use CG-NAT. A small portion maybe, might not be using Rock and the built-in Tailscale VPN. So this will not help a number of folks. How many? No idea.
Roon should, need to implement a similar method to that of Plex. The Plex relay feature simplifies remote access without port forwarding.
In their message they mention Roon Remotes and how these communicate with Roon Server. āRemotesā is an outdated term, yet they use this in their communication. That is confusing.
I would say itās not up to users of this forum to perform some sort of exegesis. Roon should be using clear terms that can be understood by every user.
Iāll add that my comment is my view only 
Users with an ISP that doesnāt support IPv6, but runs Roon Server or Client, or both on Windows may need to look at their network settings as I believe by default IPv6 is enabled. Could be wrong, I am occasionally 
Iām sure Roon will test this thoroughly before itās pushed out. They do normally 
Yet, their message is about network discoverabily, so I think it is a broader change to their infratructure ā¦ which is why thereās a rolling change.
I imagine Roon Server, Roon āRemoteā clients, and ARC have already recieved changes related to this.
For the most part, things should improve (assuming it goes to plan), but some including those with double-NAT, VLANs etc. may experience issues. Likewise, if your ISP only supports (or hasnāt enabled*) IPV6 or your router only has IPV4 enabled, no change.
Whatās not particularly clear is the language around an IPV6 enabled ISP or router. Does āaffectedā simply mean you benefit from the changes, or it could break something?
This seems to contradict the reason for the improvement, i.e., Roon no longer ignores IPV6.
*Some UK ISPs, e.g., City Fibre/Zen, offer IPV6, but you may need to request this.
Whatās unclear here: is this 1 and 2 and 3 that apply? Or is it 1 or 2 or 3?
My cable ISP does not support IPv6 yet, although they are in the process to do so. My mobile ISP does support IPv6.
My router is IPv6 ready, although the setting is off.
Roon Server runs on a Sonicorbiter 2.8 platform. I donāt know if this supports IPv6 and I do not know how I can test this.
My Roon Remotes and ARC run on an iPad and a Samsung phone that both are IPv6 ready. Sometimes I also use a laptop with Windows 11 that probably also supports IPv6.
Am I safe because my routerās IPv6 setting is off?
I assume youāre being facetious. So, yes, this and the following text is confusing. Why introduce IPV6 and then state that it should be turned off.
Now, it may simply mean that IPV6 will work, but not when a Roon Ready device or bridge only supports IPV4. But why not say that?
Yes, this is my interpretation, which is my current setup.
The first time I read Roonās message, I interpreted it as ā1 or 2 or 3āā¦ and I found it very confusing. I now assume they mean ā1 and 2 and 3ā.
Thanks 
So much confusion and so many questions, yet nothing from Roon providing any clarification. 
Nobody asked them to until I did earlier today, but itās only been 5 hours
I am looking forward to whatever changes come along, iām hoping that they will ensure a stronger and rock solid experience.
Viva la Roon!