Hi @Peter_Gallagher,
Thanks for the update and my apologies for the delayed acknowledgment here. I appreciate you keeping us posted on the workaround you’ve been able to work out.
To clarify where we stand for other users with Starlink who are encountering their blanket carrier-grade NAT:
At this time, Roon ARC requires an external (WAN) IPv4 address. Similarly, Roon requires the Core to have an address in the IPv4 format, as Roon doesn’t support IPv6 at this time. For networks that have implemented a layer of network address translation at the ISP-level (aka carrier-grade NAT, CG-NAT), your router will generally have an IPv6 address or a dynamically assigned IPv4 address within a range. The latter case (dynamic IPv4) sometimes allows for port forwarding via the configurations we’ve designed for ARC. Dedicated or dynamic IPv6 configurations will not work with ARC. Starlink has fully implemented IPv6 for their residential-tier accounts, at least in cases we’ve encounter here on Roon Community.
Rest assured that port forwarding with IPv4 support is only the initial implementation of Roon ARC, and we are actively researching several workarounds that will hopefully allow for more of our users to access the mobile streaming features offered through ARC as part of Roon 2.0. At this time, however, offline download playback or home Wi-Fi use will be the limits of ARC use for users with IPv6-assigned Starlink accounts.
That said, there are several VPN and proxy-server solutions in the #roon and #tinkering sections that users have configured as workarounds. @Peter_Gallagher has mentioned one above. Common solutions include NordVPN or other common VPNs, and Tailscale. Note that the support team will be unable to assist with VPN configuration, but we can help guide you to popular threads with solutions other users have found for their own use cases.