I’ve noticed that it’s simply not possible to use Roon if the client and server are on different IP subnets (separate VLANs - Virtual LANs). There seems to be a total reliance on service discovery in order for the client to find Roon Core systems and no ability to specify the IP address or fully qualified domain name of the server.
Relying 100% on service discovery will not be sufficient as networks increase in complexity - IMHO.
My home network is a little more complex than most but the way I have things set up is becoming more common.
As long as the required port(s) are open on any router/firewall separating the two networks, there should be no reason as to why I can’t manually specify the IP address (ideally fully-qualified domain name) of the Roon Core systems.
Unfortunately, I’m left with three choices:
- Add a secondary network interface to my computer (physical or virtual - 802.1q VLAN tag) in order for it to be able to connect to the Roon Core on a different subnet
- Set up a separate Roon core (too expensive - and unnecessary)
- Not use Roon anymore
I keep all IoT (Internet of Things) devices on a completely different network than my home and work computers - primarily for security purposes. Also to keep down the amount of “noise” created by so many different products leveraging multicast & broadcast for service location (ahem! Roon…ahem!). The multicast & broadcast traffic consumes airtime on a wireless network. The more devices you have connected to your wireless network, the more contention for airtime. See where this is going?
Please…at least make it possible for someone to specify the address of the Roon Core server and don’t fail closed when service location doesn’t work.