Do you have any additional network hardware, like additional routers or managed switches?
No, just a normal Switch
Does your network have any VPNs, proxy servers, or enterprise-grade security?
No
Connected Audio Devices
Airplay
USB connected Rotel RSP-1576
Description of Issue -
What is the exact port forwarding error message you see in the Roon Settings â ARC tab?
Does Roon server already supports natively IPV6?
I needed to get a DualStack connection from my ISP both with IPv4 and IPV6 address. With the previous DS-Lite configuration from the ISP I had no chance to get Roon ARC up and running. It always complained about MultipleNat due to the DS-Lite configuration. At the moment the public IPv4 address is for free, but Iâm afraid that they will charge me with an extra fee if I still run with software that doesnât support latest technology like IPV6. The macOs shows also a valid IPV6 address and the ARC configuration also shows the IPV6 address, but Iâm a little confused regarding the âoldâ port forwarding via IPv4.
Meanwhile I understand why a port is also necessary for ipv6, but the question is still there, why does Roon ARC not run with ipv6 natively? I have a lifetime subscription with the expectation, that Roon will be developed and kept up to date so that these kind of things wonât happen at all.
ARC does not require a port forward for IPv6 in a native IPv6 environment or a true dual-stack environment. Many network setups will still require a firewall pinhole for the IPv6 address assigned to RoonServer - this is a process akin to port forwarding in the IPv6 environment.
However, the vast majority of LANs in our user base are still IPv4 or in a dual-stack lite setup with severe limitations on IPv6.
So, IPv6-related problems ensnare a far, far smaller percentage of our users than multiple-NAT environments created by dual-router setup or ISP implementation in the IPv4 realm. In our releases of ARC so far, weâve targeted support language for IPv4 users. I understand thatâs confusing - weâre constantly working on improvements to the mobile connectivity onboarding process.
From your post, it sounds like youâre currently able to access ARC on the go via your existing external IPv4 address. If youâre in a true dual-stack account tier, you can likely disable IPv4 and rely on the internal/external IPv6 addresses in place.
Thx for the reply. I still have some questions though
Why does the automatic UPNP configuration for the router didnât worked in my case on the DS-Lite configuration? As far as I understand DS-Lite is transparent for IPV6, so it shouldâve worked out of the box, shouldnât it?
Why is the port forwarding option still available, if itâs not necessary on IPV6?
The error message I got was that there is a MultipleNat on the carrier level, and the documents of my router told me, that IPV4 forwarding is not possible on the DS-Lite configuration, which I got previously from my ISP. I think they call it CG-NAT.
So the overall picture is as follow:
DS-Lite does not work with port forwarding. Due to the fact, that DS-Lite supports IPV6, the suspicion is, that Roon Server only tried to use IPV4. If it would have been using IPV6 it should have worked. Is there a possibility to force Roon Server to use IPV6?
sorry, RTFM. As you stated I have to configure the router to enable IPV6 prefixes. The confusing part is, that the naming of different technologies vary, so itâs not always clear what function solves which kind of problem. Sometimes it takes a while to get all those naming convention to have a clear picture, especially when you have to deal with multiple languages (German and English in my case).
I have seen mention of an issue with Roon ARC Ipv6 support whereby ipv6 ip addresses with (non-zero) quads with leading zeros (explicit or implied) caused issues. e.g. a âquadâ of â9abâ (which has an implied leading 0 and so is equivatent to â09abâ as one of the quads would cause issues.
Last I read, Roon were working to fix this but I donât know the current status.
Edit: It looks like the ipv6 leading zero issue was not universal but restricted to one ISP: