[mythtv-users] Delaying until HDHR tuners are up before starting mythtv-backend

James Abernathy jfabernathy at gmail.com
Tue Jan 3 03:30:54 UTC 2023

On Mon, Jan 2, 2023 at 9:48 PM Stephen Worthington <stephen_agent at jsw.gen.nz>

> What I would do with this sort of setup would be to not use link-local
> addressing as it is always a dodgy business with IPv4.  Especially
> when you want to use multiple network ports.  The right way to do this
> is to assign real IP addresses using one of the private address ranges
> (,,  Most home routers use a
> block of the range for their addresses, so you would
> normally use a different block in that range.  Say your router is
> using, then you could use for your HDHR
> subnet.  So you might set the Ethernet port to be a static address of
>, and then set up DHCP addressing for anything that
> connects to that Ethernet port to use addresses
>  And then find out the MAC addresses of
> your HDHR devices and manually assign them a DHCP address that is
> outside the automatic DHCP address range, so use,
> and so on.
> With all of that working, then you can just go back to using a ping of
> the HDHR IP address to delay mythbackend startup.  And it should be
> completely reliable.

Stephen,  In this case one ethernet port is connected to a router and has a
Reserved IP in that router so it's like a static ip.  The HDHR is connected
directly to the other ethernet port. The reason for this is the HDHR tuners
in my house do not play well with others and must be isolated somehow. I've
tried using name brand consumer switches and forming a logic tree with the
top switch connecting to the AP/router. I've heard the AP/routers don't
handle switching traffic between their lan ports well so I have the GbE
switches do that.  But with all that work I still get errors with my HDHR
tuners on recordings that don't get errors on a PCIe card tuner.

So I went down the path of directly connecting them and that works great.
I've never seen an error in a recording yet using this method.  I just need
the boot up timing issues to be resolved. Once I could get
"hdhomerun_config discover" on the local-link port connection to only
return the IPv4 address of the device, then I was set using
hdhomerun_check.py.  If the discover command returned 2 devices one IPv4
and one IPv6 for the same tuner, then it caused the mythbackend to fail.

I guess it would be possible for the PC with the 2 NICs to run bridge and
dhcp server for that 2nd port but I don't know how to do that if it's even

Jim A
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20230102/50543d0b/attachment.htm>

More information about the mythtv-users mailing list