Configure local tvheadend process to subscribe over local igmpproxy instance

panuh

Hi, I'm having trouble finding the right words to describe my issue, therefor sorry in advance if this has been a discussed topic - I just couldn't find it. Thanks for your help in advance!

I need help understanding how TVH selects the network device over which it subscribes to UDP multicast addresses (and so to receive IPTV streams). I want to configure it to subscribe over eth1 or br-lan - not sure which yet, but I'd find out once I can control it at all.

What I am trying to do:
I am trying to run both TVH and igmpproxy on the same device (OpenWRT) for receiving IPTV (Magenta TV).
Each component for itself works well but on the same box, TVH won't connect over the correct route, I believe.

What works:
My setup works fine in my current setup when I run TVH on a LAN client connected to the router
TVH-RPi(192.168.3.X) -> OpenWRT(192.168.3.1) -> OpenWRT(igmpproxy) -> OpenWRT(pppoe-wan).
TVH worked on the OpenWRT router as well in my OLD setup, but only when the router was connected as a LAN client behind another router.
TVH-OpenWRT(192.168.0.X) -> ISProuter(192.168.0.1)

The problem:
When I run TVH on OpenWRT, it won't connect to br-lan (or eth1) where igmpproxy is listening but instead it will try eth0 directly. eth0 isn't in the routing table at all, the default route is over pppoe-wan.

So when I try to open a stream, I get the error:

 daemon.err tvheadend[5861]: iptv: rytecDE_Basic - ARTE HD in MagentaTV-rytecDE - cannot find ip address for interface eth0 [e=Address not available]

I've tried configuring the server bind address to the LAN IP instead of 0.0.0.0 but this had no effect. I assume this option only affects the web UI.

Context:
I have been happily running TVH on my OpenWRT router as a local-only device in a double NAT setup for a long time. Now, I've replaced the ISP router with a dedicated modem and the OpenWRT router connects to the internet directly.

For lots more context (routing table, igmpproxy config etc.) see my corresponding post on the OpenWRT forums where I asked for a generic solution to force a process to select a specific device:
https://forum.openwrt.org/t/local-service-process-not-connecting-to-igmpproxy/241338

davep

panuh I suspect this is Issue #1634. There seem to have been a couple of attempts at fixing this but more work is still needed.

Flole

Nope, tvheadend/tvheadend1634 is for something else. This is most likely a configuration error, I can't see any mentioning of assigning the mux to the correct interface in the post from @panuh , so I assume that was never done.

panuh

Flole

Thanks, that's exactly what I was looking for!

I'm marking this as solved because my question was about why the service selects eth0 as the network device and it was because eth0 was set as the interface for each mux. I had assumed that everything that applies to the individuall muxes must already be present in the network settings so I just overlooked it.

For others with the same problem:

Go to "Configuration -> DVB Inputs -> Muxes",
select all muxes imported from the "IPTV Automatic Network" that you've set up previously (if you see no muxes, then do that first)
hit "Edit",
choose the right interface from the Interface Drop-Down in the "Advanced" section and make sure to check the box next to it
set "Scan status in the same section to "PENDING"
Save

It still doesn't work for me, yet but the logs tell me that TVH chooses the interfaces that I've selected so I'm now facing another issue that I'll probably figure out later.

Flole

panuh I had assumed that everything that applies to the individuall muxes must already be present in the network settings so I just overlooked it.

It is at a weird location, I agree. It would make more sense to move it to the network level. Someone would have to take care of that though.... So it'll stay where it is 😉