@Dennis_Mutsaers - assuming you tested ARC on your mobile phone, make sure your GSM provider enabled IPv6 for mobile Internet access (simple test - in a web-browser, open What is my IP on your mobile phone)
(i guess) there will be many Roon users in a situation similar to mine - my ISP uses DS-Lite so i can’t use IPv4 (but IPv6 works fine) and my GSM provider didn’t enable IPv6 (and is using IPv4 CG-NAT)
more validations you can run on your Roon Core (QNAP 251+) to make sure your Core is “ready”
check external IP address used by your QNAP / Roon Core
curl -4 icanhazip.com
curl -6 icanhazip.com
verify that Roon is listening on the TCP port assigned to ARC (change PORT number if you don’t use 55002); look for lines ending in (LISTEN); run “lsof” as admin
Both my ISP for fibre net at home and my mobile provider have fully implemented IPv6 and I see both my IP6 when using one of the IP checkers.
Any attempt to use IPv4 or opening ports for IPv4 has failed as my ISP uses some kind of CGNAT resulting in a “MultipleNAT” error in Roon regardless the port forwarding method. They told me that they do not deactivate this nor offer any IPv4 option in my contract (I do not want to upgrade to a business tariff).
Switching to Roon build 1257 early access as well as ARC beta and opening the port forwarding to IPv6-only seems to solve the problem as Roon is now showing as a result of the ARC test procedure “Your Core has been successfully configured and has confirmed to be securely accessible by Roon ARC”.
When running Roon ARC on my phone being connected to the very same network everything works. But from mobile network ARC app is showing notifications that it cannot reach the Roon core at all and that it is not properly configured for reaching it externally. The port seems to be visible and open to the Roon ARC check. If I do a port check from outside using my IPv6 of the Roon core and the port shown in ARC menu I get a reply that it is open as well.
I assume that some kind of firewall might be the reason. But I have no idea where. In my router’s menu I have opened the firewall for this port and my server seem not to offer any possibility to do that manually.
I tried all commands, the response is what you would expect and show that IPv6 is functional.
My mobile provider is the same as my fiber provider, both are full dual stack IPv4/IPv6.
@yo3fxy The link you provided says it’s blocked. However if I use IPv6 Open Port Checker Tools it’s open…
I’m inclined to believe IPv6 Open Port Checker Tools, every other port than the ports I opened are closed, according to IPv6 Open Port Checker Tools.
None of this change the fact that Roon ARC fails when it has an IPv6 connection available.
If I don’t open IPv6 ports manually (for Roon ARC) and use UPnP, only the IPv4 port will be opened.
update: Now both ports (IPv4/IPv6) are open, and Roon ARC seems to work. I assume on IPv4. Nothing has been changed, except a lot of reboots (and maybe Roon/Roon ARC updates that have been released up till now)
Can you run one of the IPv6 network checks and verify that when “mobile” you have an IPv6 address? Additionally, use one of the port checkers to identify if your ports are actually open.
There is a chance your ISP may block all unsolicited incoming connections which means it still won’t work.
Please look into the fact that users with IPv6 addresses that have leading zeros in one of the address segments are failing on Roon. If you look at the IPv6 addresses of the people having problems with Roon ARC you will find this is a common factor. I’m not sure if you have many IPv6 customers other than Starlink so this may be another factor. These addresses with leading zeros are generating errors in your logs and it appears they are causing Roon ARC to call the incorrect IPv6 address for the Roon Core.
Everything was solved by calling my ISP, explained the problem, they enabled CG-NAT Opt Out, and when i refreshed the Arc Connection it was ready to go for the first time in my ARC-history.
Call your ISP and ask for this, it might solve your issue.
Prior to this I tried EVERYTHING, port forwarding, enabling IPv4, nothing, still no ARC connection. Same error message with double NAT error.
My modem/router is in bridge mode, connected to a local Mesh Network using IPv6. Enabling IPv4 did not solve it.
After the ISP’s CG-NAT Opt Out, it works even with IPv4 disabled (as standard for my Mesh network).
Unfortunately this isn’t an option with Starlink unless you want to pay an additional $500/mo for a business account to get a static IPv4 address. The rest of us have to rely on Starlink’s IPv6 addresses which afaik are still not working on Roon ARC. If anyone has managed to make Starlink work over IPv6 please let the rest of us know how you did this.
