hdhomerun apps over vpn

[boingolover]

I have a wireguard vpn configured on my home router, and I have wireguard clients set up on my iPhone and my laptop. The ios and macos apps both appear to rely on broadcast traffic to discover hdhomerun tuners, which obviously isn't going to work since the wireguard subnet is different than the subnet where my hdhomerun tuner lives.

First off, why does this refuse to work if broadcast discovery fails? Why can't I specify the IP manually? Second, why not use something like mdns for discovery instead? Sorry if this has been covered before, but "broadcast" is unfortunately a very loaded search term on this forum, and i didn't see much relevant when I searched for "discovery".

Thanks in advance

[nickk]

Our focus is the best possible DVR within the home.

MDNS uses multicast - it most likely won't work via a VPN either.

The key concept is that you can have any number of HDHomeRun tuners, any number of HDHomeRun record/storage engines, and any number of clients... everything finds everything with zero configuration.

[boingolover]

mdns can be made to work across subnet boundaries, and my router vendor (mikrotik) implements configurable mdns repeaters in their dns implementation. mdns support would be a nice-to-have, but not at all a requirement. mostly I was just wonder though why you can't specify an IP address of a tuner in the app. Maybe some users don't know what the IP address of their hdhr is, but I think you'd be surprised at how many users do.

[boingolover]

for what it's worth, my laptop can resolve hdhomerun.local over the vpn. you seem to be using mdns already, just not relying on it for discovery in the apps.