So I installed Roon Server on my Qnap, installed and enabled the Roon Bridge in my RPI Volumio… installed the Android Roon Remote App…
The Android Roon Remote connects to the Qnap NAS (When I enter the IP, if not, spinning its head of).
RS on Qnap seems OK, has a directory with files etc. Ive also linked up my Tidal account.
Problem is - how can I tell the server where to find the RPI Bridge? My network is not a flat RFC1918/24 setup, but multiple RFC1918 networks…
Can I somhow tell the core that the bridge is on IP: x.y.z.n ???
Plz advice, my 14 day trail is running
Welcome to the community,
All Roon devices need to be on the same subnet.
The Android Roon Remote, you can manually enter an IP. My Android phone is on a WiFi with one subnet, the Roon Server on another. So that works. No need for the same subnet!
Then why should one not be able to tell the server to scan IP x.y.z.n to find a bridge
I can probably make an ssh tunnel from the RPI-Volumio to a host in the Qnap-Roon-Server subnet, that would work, but I would rather not!
See the following post. I can move the thread to
# if you like since this isn’t a supported configuration but there are some who have got it working. tinkering
I have moved this thread over to "Tinkering’ since as I have previously mentioned, Roon is designed to only support a single subnet for both control and audio streaming. There may be some users who have gotten their setup working on two subnets but we do not officially support multiple subnets and I am not familiar how stable it would be or what exact steps you would have to take to get it working. Some other threads that might pique your interest in subnet configurations…
Welcome to the forum. As
@Martin_Webster mentioned, we can only support Roon when Core, Remotes and Endpoints are on the same subnet. Since you have multiple subnets set up, you are in # territory, and I have moved your post over to this sub-section. tinkering
There are a few threads on the forum of users who managed to get Roon working on a non-flat network if you search around, but as I mentioned, these are not officially supported and you’ll have to try and see what works yourself.
Roon uses multicast for endpoint device discovery, and remote to Core connections, so a few have mentioned the need for an mDNS reflector:
I’ve spent the past few days trying to play around with the interfaces between VLANS to support the core. My setup consists of three VLANS: one that contains the core, one with the remotes (my trusted network), and the third with end points (sonos speakers).
I have a MDNS repeater turned on between the VLANS on in the router to support multicasting and I have the router explicitly relaying the the UDP and TCP traffic on ports 9003 and 9100-9200 across all the VLANS, but that hasn’t seemed to he…
Continuing the discussion from
Remote control from another LAN:
As I mentioned in the linked topic, I did some experiments with airplay on my receiver and Roon.
The setup is Roon Core running on a computer (iMac) within its own VLAN, and the rest of my home network in another VLAN. Both VLANs are connected to a ubiquity router without any firewalling/NATTing between them
I configured the router to work as an MDNS reflector (ships mDNS packets form one VLAN to the other, in both direction…