Hi @Dean_Kimball,
Thanks for posting - we’re following up in our Early Access thread here: ARC Connectivity Issues
@outsidenwnc, thanks for volunteering. We’re happy to answer any questions.
Good Day,
Here is my setup
Starlink ISP - router in passthrough mode.
Unifi UDM Pro - IPv6 , DHCP6, Prefix Delegation 56- ipv6-test.com pass 20/20
Unifi Managed Switch
Hard Wired ethernet connection
Roon Server/Mac mini M2 16GB Ram Ventura 13.5.1
Iphone 13 Pro/ ATT Wireless ( 4G LTE in my area)
My observations:
When I check the Roon ARC section in settings, it fails, I check the IPv6 address Roon is using and port I’ve selected and add that to my Internet V6 Firewall rules in Unifi Network. The current IPv6 addresses I have do not have leading 0’s.
Then Roon ARC comes back as connected. I can take my iPhone off my network on AT&T LTE and it works! Great!
However after some period of time it stops working. I go to settings and Roon Arc is using a different IPv6 address than I have previously put in the firewall setting so it is not working.
The specific IPv6 address I used earlier after a couple days is no longer assigned to my interface on the Mac mini. It runs headless 24/7. In IPv6 you can have multiple IPv6 addresses assigned to your interface. Starlink experienced a short outage during this period it may have been assigned new addresses when it reconnected.
I changed my firewall rule to use my IPv6 subnet instead of a specific IP address and it works, so instead of opening a pinhole I have to open door.
So this seems like something Starlink customers may have to deal with not an issue with Roon.
Thanks for your support.
1 Like
I have this working with TailScale (both ARC and the regular Roon client work perfectly). I’ve also discovered the wonderful smart downloads feature so I’ve loaded up my phone and run ARC offline when I’m out and about locally as our mobile signal is shocking. Given how easy the TailScale stuff is and the fact that it’s free I don’t see me needing to connect direct any time in the immediate future.
Update- After studying this for awhile I have discovered something of note for Unifi Network configuration.
On my Roon server I had one local link IPv6 address, and external IPv6 address assigned by my UDM Pro, and several other external IPv6 addresses one of which Roon was selecting for ARC that always seemed to disappear after awhile.
In Unifi Network my Internet or WAN network is set to IPv6 DHCPV6. Local network set to DHCPV6 and there is an additional setting for ‘Allow SLAAC’ that is selected by default.
This 'Allow SLAAC ’ setting is causing the additional IPv6 addresses being assigned to my NIC. Once I turn this off I was left with one internal IPv6 address, one external IPv6 address assigned by my UDM Pro ( which has many leading zeroes within it). Roon allows selects one external address now, I can narrow scope on my firewall. And Roon Arc reliably connects.
1 Like
Hi @outsidenwnc,
Thank you for taking the time to write out your experience in full detail. We’re certainly glad to hear that native IPv6 is now functional with your setup, although the dynamic address assignment component is certainly frustrating, we’re glad the UDM workaround seems to have resolved.
I’m going to pass this report up to both QA and Product, as we’re ingesting all the feedback we can with this new functionality.
Adding more precise language around IPv6 pinholing - not just port forwarding with IPv4 - is on the roadmap now that we’ve passed the first round of obstacles with IPv6.
Again, we really appreciate your time. Thank you for testing.
Hi Connor,
The ARC Connectivity Issues thread has been closed so I’m reporting this here. I don’t have much to go on yet but so far ARC has crashed twice on IPv6 and I know for sure the second time was right at a track change and I think the first one was as well. Here is what happens:
- A track finishes playing then the audio stops
- I look and Android Auto is back at the home screen
- Roon ARC is no longer running
- I restart Roon ARC and it returns to the previous track, not the next track
I’m going to guess that I’ve played perhaps 40-50 tracks in my Android Auto system since IPv6 was fixed so it’s something like 1 out of 20 or 25 tracks - an intermittent problem. However, you should probably log this in case you start getting similar reports from other users. If Roon ARC has the ability to report unexpected termination exceptions you may get some data about this from those.
Thanks,
Dean
Hi everyone,
We shipped several iterations of improvements for IPv6 handling with builds 1382 through 1401. There are additional improvements in the most recent build.
We’re closing this thread for now - please report any new issues in a dedicated topic thread and we’ll address them there. Thanks!
@Ian_Robson2, I’m late to respond here, but Tailscale is highly reliable and the most recommended workaround on this forum. There’s no reason to switch to native IPv6 if you’re not eager to tinker.