Unable to find Tuner if not on the same Vlan as TV - walkerx

[walkerx]

I'm experiencing a similar issue, where all media devices are on their own vlan, but the server running the software and the hdhomeruns (2 x quatro) are on a different vlan.

I can access the tuners using emby or channels without any issues, but the hdhomerun software on appletv or firecube won't see the devices, yet sees the dvr server which is on the same vlan as the quatro's so there should be no reason for it not to work.

[jasonl]

What are the IPv4 and IPv6 addresses of the Apple TV and Fire Cube?

[walkerx]

they are on a 192.168.13.xxx range with hdhomerun stuff on 192.168.80.xxx range

the dvr service (also the channels dvr service and emby server) is on a pc on 192.168.80.xxx range

if i open channels app on apple tv or emby i can view the guide and pick live tv without any problems

if i open hdhomerun app, it reports it can't find the devices and gives option to continue, retry or exit. if you continue it shows the recordings that have taken place and stored on the server and allows you to play them. so why can't the app link into the service which in turn links in the tuners, if the other 3rd party apps can do it, then why can't the app from the manufacturer/provider do the same thing?

It would make users wonder if they should stop paying for the service via silicondust and just stick with 3rd party solutions

[jasonl]

The reason I asked about IPv6 is that it appears your DVR PC is accessible on multiple different subnets, like you might have a /56 from your ISP and are running a different /64 on each VLAN, but the PC is on 2-3 different ones simultaneously, which is why the app finds the DVR but not the devices. Multi-VLAN operation is possible using IPv6 if the switch/router forwards multicast between the different VLANs. The discovery uses the IPv6 multicast range intended for site-local functions, so it should work correctly provided the switch/router handles that correctly.

[walkerx]

my ips provides

ND Prefix: xxxx:xxxx:xxxx:xxx::/64
PD Prefix: xxxx:xxxx:xxxx::/48

I allow the Apple TV and FireCube to talk across the vlans to my server

Multicast DNS is enabled (https://help.ui.com/hc/en-us/articles/1 ... mDNS-Proxy)

[rikd]

How is your IPv6 managed in the vlans?
Currently the tuners only support SLAAC while the DVR service on a server will support whatever the server supports (SLAAC, dhcpv6, etc.)
Since the app on your devices can see the DVR it looks like site multicast is working (is our own service not mDNS) across the VLANs which is great.
but since you don't see tuners am guessing you are using DHCPv6 so the DVR is seen, but the tuners are not since likely the RA is not providing them a prefix to use when choosing an IP, (might even just be setting link local) and thus they don't look like they are part of the same site to your router. configure the router to allow for a mix of SLAAC and DHCP with the RA sending the prefix and it should (big asterisk as ever in anything IPv6 and routers here) then allow the multicast with the tuners.

[walkerx]

I've updated all my IPv6 to use SLAAC (was using a mixture as my ISP supports both SLAAC and DHCPv6)

The tuners are receiving an IPv6 address and Link-Local address as well as their IPv4 address

I've allowed inter vlan connections from vlan 68 and 3 (Apple TV/FireCube to Server and HDHR Tuners) - setup the ports to allow both vlans and also allowed traffic to transverse for the tv side

I've setup the RA to low on the vlans, tried with and without IGMP Snooping and still no go

Not sure if this is a unifi thing or how the hd tuners are broadcasting, ie are they using the standard 239.255.255.250:1900 and 224.0.0.252:5353 ips and ports?

[rikd]

I've updated all my IPv6 to use SLAAC (was using a mixture as my ISP supports both SLAAC and DHCPv6)

The tuners are receiving an IPv6 address and Link-Local address as well as their IPv4 address

And the IPv6 matches the IPv6 prefix expected for that VLAN segment?

I've allowed inter vlan connections from vlan 68 and 3 (Apple TV/FireCube to Server and HDHR Tuners) - setup the ports to allow both vlans and also allowed traffic to transverse for the tv side

By ports I assume you mean the physical ports?
Fwiw - that shouldn't be needed. because they are on separate networks they will request the router to move the data between the networks, and the router will apply the correct VLAN tag as needed.

I've setup the RA to low on the vlans,

Do you mean router priority in the RA? All that does is allow the devices to select a higher priority router if available. If you have 1 router - it won't matter.

tried with and without IGMP Snooping and still no go

IGMP Snooping is kinda the right thing here.. For IPv6 it's called MLD rather than IGMP, and is a set of services within ICMPv6, but the same premise is likely required.
By default if a switch receives a multicast packet on one port it sends that packet on all ports. This becomes a nightmare if one device suddenly dumps a lot of packets down that link.
So many switches (particularly more expensive ones ) will not do that and will BLOCK multicast downstream unless a devices has subscribed to it. That's where IGMP/MLD snooping comes in to monitor the listeners..
Check if your router/switches also allow for MLD snooping, or if IGMP covers both. Also check what the default action for multicast handling is.
Also you may have to check every switch from tuner to the player to ensure it's not blocking multicast.

Not sure if this is a unifi thing or how the hd tuners are broadcasting, ie are they using the standard 239.255.255.250:1900 and 224.0.0.252:5353 ips and ports?

Broadcast doesn't exist in IPv6.
for IPV4 it is always within the network and a router will not propagate out to the other networks.. This is the discovery mechanism we use for IPv4.
For multicast we're talking IPv6 - so those 239... (this is actually SSDP/UPNP) and 224... (mDNS) addresses are meaningless here (but useful for other things )
Instead we have a scope of addressing - ff02:: or ff05:: and some defined addresses for different services with ff0x::176 registered for HDHomeRun
you can see registered addresses here https://www.iana.org/assignments/ipv6-m ... -addresses
So you should be seeing for discovery packets to/from ff05::176