DVR can't see HDHR on separate Subnet

Channels DVR Server
#1

I was having trouble the other day while reconfiguring some things on my network. I am moving my Channels DVR (and some other equipment) to a different subnet. However, when I initially did it, the Channels DVR couldn’t find the HDHR any longer.

LAN1 - 10.0.1.0/24
2 ATVs
HDHR
Computer

LAN2 - 10.0.2.0/24
Server with Channels DVR

With the DVR on LAN 2, I am able to access it via the browser no problem, and my Apple TV’s on LAN1 discover it, and I can playback recordings as well as watch Live TV. But, on the settings page from the browser, it showed that there was no HDHR present. Thinking that maybe it just wasn’t discovering it, I tried typing in the IP address manually. It appeared to save it (no errors displayed), but still showed no tuner present. Everything is configured correctly on my network, and even have mDNS configured across subnets. Is there something with Channels DVR that is not allowing the HDHR to be on a different subnet from the DVR?

#2

The devs will be able to say for sure, but I don’t think the DVR will discover HDHomeruns on a different subnet. Have you tried adding the HDHR(s) manually by IP address?

#3

Yep…but it still doesn’t show up for some reason. Even though I can ping it from that subnet and everything. Seems to be something with the Channels DVR that doesn’t want to accept an IP on a different subnet?

#4

If all of the devices on both networks are intended to be able to communicate freely with one another, then what is the point in having separate subnets?

If the purpose is to reduce network congestion, maybe a better solution would be just use a single subnet and then plug the DVR, HDHR, and ATVs into the same network switch. This will isolate this traffic to the switch and won’t interfere with your computers on the internet.

#5

What platform is the DVR on?

#6

You might need to change your broadcast to /16 instead of /24

#7

I’m similar except I have the DVR in my IoT subnet with the HDHR and ATV. Everything works great. Those are all things I don’t want communicating with my PCs. Plus they all expect to use broadcast traffic that doesn’t route. Fortunately channels allows my iOS clients to have manually assigned addresses.

#8

Sorry for the delayed response…Its running on a Synology DS916+

And to clarify…Bonjour is working across subnets. But, even when I try to manually specify the IP address, it doesn’t seem to save the setting.

#9

Can you SSH into the NAS and ping your HDHR?

#10

Yep, and it responds to the ping just fine.

#11

I think it would be worth re-visiting this to make the Channels app behavior consistent.

I have a similar situation to @todom. The HDHR and Synology(DVR) are on a different subnet than the ATV. There is no firewall–ping/ssh work fine between all. The Channels auto-discovery mechanism appears to not cross L2 boundaries however my configuration crosses L2 boundaries and therefore L3 subnets.

The Channels app offers a workaround for the HDHR by specifying the IP, the feature request is to please have the same (specify DVR IP) for the DVR please. It also lends a level of security by allowing separation for those so inclined.

#12

The DVR uses Bonjour for discovery. If you have a complex network setup you can look into setting up a mdns repeater or proxy.