As long as it is a non CG NAT public IP address you should be fine. Check your wan interface IP and do a “what’s my IP” google search and compare the two, are they the same all should be fine. As for the dynamic part it all comes down to lease time and how your port forwardings source IP imay be configured.
With my current ISP architecture (in Thailand), I unfortunately cannot use the Roon ARC either. Anyway it’s a good feature and I’m looking forward to solutions the Roon dev team will bring about. I understand that you are working on the ipv6 support?
In the mean time, is it possible for Roon ARC app to have a setting for us to manually enter a domain name and port for connecting back to Roon Core ourself? The ISP let me configure this kind of dns/port forwarding on its web. And I’m using this mechanism to connect back to my home camera and also to my ebook library (Calibre) successfully.
Been through all of the help and troubleshooting, and my findings are my ISP is using NAT IP, seems to be a common thread.
I work in IT and tracing all of the settings to get this far is not easy at all. Asking people to go to into their routers advanced config and having to ask ISP’s for a private IP to get your new feature to work is pretty poor form Roon. My ISP charges $10/month for a private IP, which is an additional $120/year on top of the cost of Roon, yeah nah bro.
I’d rather not have an option than one that makes my music life feel like I’m back at work. I hope you’ve hired an extra 5 support staff for all of the support tickets you’ll get from this.
Roon ARC app deleted, Tidal app working first try.