noris
July 25, 2018, 4:45pm
4
Hello @stongelidis ,
As @Geoff_Coupe mentioned, we do not support Roon running on different subnets since our multicast protocols used for discovery only work on one subnet. You can read more about this discussion in the following threads:
So far the answer seems to be yes. I have two subnets and when I start up remote on the non-core subnet the remote doesn’t connect.
Hi – Installed Roon Core x64 on Ubuntu 17.04 last night on my home LAN; current versions of everything. My Roon remotes work great when located on the same LAN. However, I can’t get the Roon remote to connect from any network outside my LAN, on a different subnet, connected through an “allow all” VPN.
Home LAN1: 172.16.0.0/16
Remote LAN2: 10.0.0.0/16
I’m able to ping the Roon Core server from the remote LAN, and ports 9100/9101 appear open when I run nmap. No ports are blocked. I’ve tried sev…
(Just found this post while researching a problem I’m having)
I’ll echo this request. My use case is a work network that blocks multicast for security reasons. I can connect my Raspberry Pi with Roon Bridge to the network just fine, but my Roon Core on my laptop can’t discover it. With direct IP configurability (like exists for HQPlayer, which doesn’t have native discoverability) I could manually add the Roon Bridge as an end point.
All that being said, I don’t know if the actual audio stre…
Thanks,
Noris