[mythtv-users] Mythtv and Jellyfin on same backend

[Klaas de Waal]

On Thu, 19 Oct 2023 at 11:17, Mike Perkins <mikep at randomtraveller.org.uk>
wrote:

> On 19/10/2023 03:53, Stephen Worthington wrote:
> > On Wed, 18 Oct 2023 23:10:58 +0100, you wrote:
> >
> >> On 18/10/2023 18:16, Ian Evans wrote:
> >>> Stephen,
> >>>
> >>> Just circling back to one point:
> > [snip]
> >>> (Reminder that my current home networking experience is limited to
> plugging
> >>> into a consumer router and setting up some static assignments.)
> >>>
> >>> Do you only need to set up the DHCP server on the second port of the
> >>> backend if you're doing the "plug the homeruns into a small switch and
> plug
> >>> that into port #2 of the backend" option? Does it still have to be
> done if
> >>> using the second option, which was "plug everything into a managed
> switch
> >>> and create an HDHomerun VLAN and have that go to port #2 of the
> backend"?
> >>>
> >>> Also why would the backend require its own DHCP server as opposed to
> the
> >>> router's?
> >>>
> >> In general the DHCP server has to be on the same subnet as that of the
> hosts that require
> >> addresses[1]. This is what you would get naturally for your option 1
> above.
> >
> > This is the problem - the DHCP server needs to be run on the new
> > subnet you are creating.  Even when the subnet is using VLANs on the
> > switch, it is using the VLAN headers to isolate the new VLAN from the
> > rest of the traffic on the switch, so it has no connection to the
> > router where your main DHCP server is.  And you do not want to use a
> > VLAN (in a different way to using VLANs on the switch, where the VLAN
> > headers are added outside the switch) to connect the new subnet to the
> > router, as that would be sending all the broadcast traffic on the new
> > subnet over the existing Ethernet connection between the backend and
> > the router, increasing the traffic.  It is best to just run a DHCP
> > server on the backend box, only talking to the new subnet on the
> > second Ethernet port.
> >
> Agree completely, but with one caveat: the HDHR traffic is /not/
> broadcast, it is standard TCP.
> Therefore, although (on mine) it does go to my router, because it it not
> addressed to anything on a
> different subnet it is immediately dropped at low cost to the router.
>
> --
>
> Mike Perkins
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org


I have on my production mythbackend a dedicated network card connected to
one HDHomeRun with only a cable. This then autoconfigures itself and it
just works.
No manual configuration required at all.
This is on Fedora 38 but I have it like this already for years.

Klaas.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20231019/bda83355/attachment.htm>