Roon runs on my Synology NAS (latest DSM) and I have about a dozen audio devices. Everything works great.
I am about to completely redo my network which will change all the IP addresses. What will the impact on Roon be? Is there a way to tell Roon about the new IP addresses for, well, everything?
Not knowing your setup we can only guess at what will happen, however, if you did not set any “static IP addresses” on your devices then they “should” be assigned new addresses by your “new?” router. As long as all of the devices and the Roon Server are on the same subnet, once Roon is running properly on your NAS it “should” be able to see them. There may be some firewall rules or exceptions that may need to be updated on any Windows or MAC devices or the Synology to get it working on the new network?
I would suggest, before changing the network, make note of all the IPS and/or make sure all devices are using dynamic IPs.
If you used DHCP on the old network (as you normally should, and which is the default on the router and on every audio device) and you use DHCP on the new network, too, then the devices will get their IP addresses from the router automatically. Roon uses a network discovery protocol, so it should find the server and the endpoints automatically, too. (If you set up static addresses on the devices, see @bearFNF above)
Ensure that everything is on the same subnet in the new network (which is usually also the default, but some routers might by default put Ethernet and wifi into different subnets).
If you configured port forwarding for ARC manually, you will have to re-do the forwarding rule on the router. If port forwarding was auto-configured with UPnP, ensure that this is enabled on the new router.
On first start, the control app may ask you to “unauthorize” the old Roon server, in which case do this and then you can connect to your usual server again. (This happens when Roon thinks the server on the old network was a different one than the same server on the new network. As your license only allows one server, the license info must be transferred. This is safe)
Thank you for this. I was hoping Roon used DNS to find the devices, which will not be changing names. The IP’s are visible in the Roon app along with the names… hopefully that is updated.
I’m replacing a DECO-based system with Ubiquiti for more flexibility with VLAN’s, firewall rules, etc. I’ve also been searching the community for Ubiquiti best practices with Roon.
In terms of Roon discovery, as suggested above, you shouldn’t need to do anything, might be worth giving your Roon server a reboot to force everything to rediscover but that’s about it.
Where you might have issues is if you hard coded an IP address rather than a name for your NAS’s Music share / watched folders ie. smb://192.168.1.100/Music vs smb://NASNAME/Music (the latter is preferred).
But what jumped out at me and made me reply is you mention VLANs. Roon doesn’t work across VLANs. Your server, clients and audio devices all need to be on the same subnet.
Finally, pretty sure the out-of-the-box Unifi settings are good for Roon.
Don’t go checking / unchecking loads of checkboxes based on a bunch of potentially out of date, well meaning but wrong or irrelevant (to your setup) forum posts. If your network is stable with the default settings, leave them be, unless you really understand what they do and why they need to change. You’re not going to improve on working, but you are likely to cause problems elsewhere ie. you could mess up your Apple device discovery for example.
(yes, there are advanced ways to proxy Roon traffic across VLANs but unless you are well versed in networking and are up for maintaining third party services and scripts on your system it’s not something I’d recommend and another thing to go wrong which you’ll have to diagnose and fix yourself).
I tried to add to the original thread but I guess it closed…
Just wanted to let everyone know - I did the Deco → Ubiquiti switch today and it went without a hitch. And, best of all, Roon just WORKED! it found my NAS and all the audio devices with thier new IP addresses. Just like magic!
Thanks for everyone who chimed in!
1 Like
AceRimmer
(Smoke me a kipper, I'll be back for breakfast!)
10