[mythtv-users] directly connecting HDHR to spare LAN port

[Greg Oliver]

On Tue, Jun 21, 2022 at 2:16 AM Mike Perkins <mikep at randomtraveller.org.uk>
wrote:

> On 21/06/2022 02:41, Stephen Worthington wrote:
> > On Mon, 20 Jun 2022 19:30:49 -0400, you wrote:
> >
> >> On Mon, Jun 20, 2022, 1:59 PM Greg Oliver <oliver.greg at gmail.com>
> wrote:
> >>
> >>> On Tue, Jun 14, 2022 at 4:14 PM Bill Meek <keemllib at gmail.com> wrote:
> >>>
> >>>> On 6/14/22 08:52, Klaas de Waal wrote:
> >>>>> Hi Jim,
> >>>>>
> >>>>> On Mon, 13 Jun 2022 at 21:07, James Abernathy <jfabernathy at gmail.com
> >>>> <mailto:jfabernathy at gmail.com>> wrote:
> >>>>>
> >>>>>      I have a NUC with  2 RJ45 ports on the back. One is 2.5Gb and
> the
> >>>> other is 1Gb.  Is there a simple way to connect a HDHomeRun Connect
> tuner
> >>>>>      to one of these ports so it would work with Mythtv and eliminate
> >>>> any record problems that I'm having from being network related??
> >>>>>
> >>>>>
> >>>>> On my production system I have a separate network card with a direct
> >>>> cable connection to a HDHomeRun without any configuration whatsoever.
> No
> >>>>> fixed IP addresses, no DHCP, no routing, not anything and it just
> >>>> works. Of course, then the HDHomeRun cannot be accessed by anything
> else in
> >>>>> the network but that does definitely eliminate interference from
> other
> >>>> devices on the network.
> >>>>>
> >>>>> Klaas.
> >>>>
> >>>> I used the link local solution too. To get to my HDHR's web page, I
> have
> >>>> a function:
> >>>>
> >>>> function hdhr() {
> >>>>       HDHRIP=$(ssh yourbackendhostname "hdhomerun_config
> discover"|grep
> >>>> 169.254|cut -d' ' -f6)
> >>>>       echo -e "\nTo connect to the HDHR, use: http://localhost:8001
> \n"
> >>>>       ssh -L 8001:${HDHRIP}:80 yourbackendhostname
> >>>> }
> >>>>
> >>>>
> >>>> Typing: hdhr will print a link that can be opened.
> >>>>
> >>>> --
> >>>> Bill
> >>>>
> >>>> The simplest way to do it is just setup both ethernet ports into a
> bridge:
> >>>
> >>>
> >>> ip link add *br0* type bridge
> >>> ip link set *br0* up
> >>> ip link set eth0 up (or whatever your ifnames are)
> >>> ip link set eth1 up
> >>> ip link set eth0 master br0
> >>> ip link set eth1 master br0
> >>>
> >>> With this, both ethernet ports will get DHCP from your existing router.
> >>>
> >>> -Greg
> >>>
> >>>
> >> I like this solution. I understand bridges from using them with libvirt
> kvm.
> >>
> >> Thanks,
> >>
> >> Jim A
> >
> > The downside of bridging is that all the broadcast traffic is sent to
> > the new subnet.  That can be ok if you are not doing large amounts of
> > broadcast traffic, but if you do multimedia broadcasting (ie large
> > broadcast packets) it will use up significant bandwidth and defeat the
> > purpose of using a separate subnet for the network tuners.
>
> And of course the reverse is also true. All the HDHR traffic will go to
> the router, which has to
> process it even if it ultimately just ignores it.
>
> If you're going to add a software bridge that defeats the object. You
> might just as well plug the
> HDHR directly into the router.
>

All (most) home routers that run Linux (99% probably) LAN ports are already
software bridged using the exact same commands I just outlined anyway :)


> The only way I could see a case for using a software bridge is if you have
> capacity constraints: ie
> no more ports on the router or no way to run a cable between HDHR and
> router.
>
> --
>
> Mike Perkins\
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20220622/d686e58e/attachment.htm>