[mythtv-users] HDHR prob with new wallwarts

[Stephen Worthington]

On Thu, 12 Dec 2019 16:31:02 -0500, you wrote:

>On Thu, Dec 12, 2019 at 1:45 PM Allen Edwards <allen.p.edwards at gmail.com>
>wrote:
>
>>
>>
>> On Thu, Dec 12, 2019, 10:29 AM Daryl McDonald <darylangela at gmail.com>
>> wrote:
>>
>>>
>>>
>>> On Sat, Dec 7, 2019, 11:36 AM Allen Edwards <allen.p.edwards at gmail.com>
>>> wrote:
>>>
>>>> I have no idea if this will be helpful but I had several issues getting
>>>> my HDHR tuners to work. I provide these in case they might be useful.
>>>>
>>>> Myth address is 192.168.1.111 and is static. I set it as reserved on the
>>>> router. I also set the HDHR addresses as reserved.
>>>>
>>>> I start the tuners from rc.local. Old school but works.
>>>> Here is the code. I believe this was from the vendors website.
>>>> hdhomerun_config 10137DC1 set /ir/target "192.168.1.111:5000 no_clear"
>>>> If you need to allow more time to go by, you can add a delay before this
>>>> command.
>>>>
>>> This part is outside my capabilities, probably would need more time if I
>>> get the mobo to play nice with ACPI.
>>>
>>>>
>>>> I had a power supply issue as well. The module that I bought with the
>>>> HDHR did not put out enough current so I got ones rated for more current.
>>>>
>>>> I also had random failures. The computer would lose contact with the
>>>> turners every few weeks. I traced it to a linux problem as the tuners were
>>>> still visible from a Windows computer on the same network. That
>>>> troubleshooting tip was provided by Silicon Dust.
>>>>
>>>> Here is the solution.
>>>>
>>>> dad at NewMyth:~$ more /etc/network/interfaces
>>>> # interfaces(5) file used by ifup(8) and ifdown(8)
>>>> auto lo
>>>> iface lo inet loopback
>>>> auto enp2s0
>>>> iface enp2s0 inet static
>>>>     address 192.168.1.111
>>>>     netmask 255.255.255.0
>>>>     gateway 192.168.1.1
>>>>     broadcast 192.168.1.255
>>>>     dns-nameservers 8.8.8.8   8.8.4.4
>>>>
>>>> Hope this helps.
>>>>
>>>> Allen
>>>>
>>>
>>> I've set my FE/BE reserved to .210 and the HDHRs to .211, and .212, no
>>> change to gateway and netmask, beyond this I need help.

>>
>> What you did is not enough. I did that from day 1 and had the problem.
>> Perhaps you can ask a specific question based on the fix I posted.
>>
>>>
>>> OK Allen I'm all in, this is my interfaces file now:
> $ cat /etc/network/interfaces
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>auto enp2s0
>iface enp2s0 inet static
>    address 192.168.0.210
>    netmask 255.255.255.0
>    gateway 192.168.0.1
>    broadcast 192.168.0.255
>    dns-nameservers 8.8.8.8   8.8.4.4
>My only question is, where did you get the dns-nameservers values from? Do
>I need to edit these?

You would normally want to use the nameservers that your router should
be getting from your ISP.  Your router may be able to tell you what
they are.  Using Google's public nameservers as above should work for
most things, but there can be some subtle problems (and benefits). For
example, if your ISP runs local CDN servers (say Akamai servers), then
anything you would normally have got from the local CDN servers will
now be received from some global server somewhere much further away if
you use Google DNS.  And you may be unable to access ISP services that
are provided only to your ISP's customers from this PC.

If you can find the correct ISP nameserver addresses from your router
of maybe from a web page on your ISP's help pages, or by calling their
helpdesk, then you can put them here.  ISP nameserver addresses
normally do not change, but it can happen if they have to reorganise
their IP addresses (especially if someone takes them over), and if
that happens, then the static IPs that you put here will need to be
changed also.  It is unlikely that your ISP will inform you if they
change the addresses, as your router will normally pick up the new
ones automatically.  If you use Google's nameservers, then those
addresses are extremely unlikely to change.  And if they ever do, it
will be big news on the Internet.  But you are giving Google
information about what DNS addresses you are using.

I think it may be possible to do partial DHCP, where you use a static
IP address as above, but get things like the nameserver addresses
using DHCP.  I have never done that using the interfaces file, but it
is probably possible using some scripting.  Likely way beyond your
capabilities.

Also, using /etc/network/interfaces on a system that is using
NetworkManager as yours is, there can be lots of complications.  I
found I had to disable NetworkManager to get some things to work, and
that may have included the "dns-nameservers" options.  It is a very
long time ago that I did this, so my recollection is cloudy.  So
overall I would recommend not doing static IP addresses this way
without removing NetworkManager.  It gets too complicated.

Instead, I would recommend that you use the NetworkManager GUI to set
a "Manual" IP address.  "Manual" is NetworkManager's name for
"Static".  You can then set the DNS options on the same screen to
"Automatic" and that will get the DNS server addresses using DHCP, but
have a static IP address.  The best of both worlds, unless it was a
NetworkManager bug that was causing Allen's problems.

Click on the NetworkManager icon, usually at the top of the screen,
often on the right somewhere.  Mine looks like a little white box with
a line dropping down to two more little white boxes below it.  Click
on the cogwheel icon to open the settings for the Ethernet card, then
on the "IPv4" tab.  Select "IPv4 Method" "Manual" and fill in the
"Address" field with the static IP address you want.  The "Netmask"
field should normally be set to "255.255.255.0" and the "Gateway" to
the IPv4 address of your router.  Leave the "DNS" and "Routes" options
set to "Automatic".  Click "Apply".