<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Dec 13, 2019 at 7:28 AM Stephen Worthington <<a href="mailto:stephen_agent@jsw.gen.nz" target="_blank">stephen_agent@jsw.gen.nz</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, 13 Dec 2019 09:51:00 -0500, you wrote:<br>
<br>
>On Fri, Dec 13, 2019 at 6:14 AM Stephen Worthington <<br>
><a href="mailto:stephen_agent@jsw.gen.nz" target="_blank">stephen_agent@jsw.gen.nz</a>> wrote:<br>
><br>
>> On Thu, 12 Dec 2019 16:31:02 -0500, you wrote:<br>
>><br>
>> >On Thu, Dec 12, 2019 at 1:45 PM Allen Edwards <<a href="mailto:allen.p.edwards@gmail.com" target="_blank">allen.p.edwards@gmail.com</a>><br>
>> >wrote:<br>
>> ><br>
>> >><br>
>> >><br>
>> >> On Thu, Dec 12, 2019, 10:29 AM Daryl McDonald <<a href="mailto:darylangela@gmail.com" target="_blank">darylangela@gmail.com</a>><br>
>> >> wrote:<br>
>> >><br>
>> >>><br>
>> >>><br>
>> >>> On Sat, Dec 7, 2019, 11:36 AM Allen Edwards <<a href="mailto:allen.p.edwards@gmail.com" target="_blank">allen.p.edwards@gmail.com</a><br>
>> ><br>
>> >>> wrote:<br>
>> >>><br>
>> >>>> I have no idea if this will be helpful but I had several issues<br>
>> getting<br>
>> >>>> my HDHR tuners to work. I provide these in case they might be useful.<br>
>> >>>><br>
>> >>>> Myth address is 192.168.1.111 and is static. I set it as reserved on<br>
>> the<br>
>> >>>> router. I also set the HDHR addresses as reserved.<br>
>> >>>><br>
>> >>>> I start the tuners from rc.local. Old school but works.<br>
>> >>>> Here is the code. I believe this was from the vendors website.<br>
>> >>>> hdhomerun_config 10137DC1 set /ir/target "<a href="http://192.168.1.111:5000" rel="noreferrer" target="_blank">192.168.1.111:5000</a><br>
>> no_clear"<br>
>> >>>> If you need to allow more time to go by, you can add a delay before<br>
>> this<br>
>> >>>> command.<br>
>> >>>><br>
>> >>> This part is outside my capabilities, probably would need more time if<br>
>> I<br>
>> >>> get the mobo to play nice with ACPI.<br>
>> >>><br>
>> >>>><br>
>> >>>> I had a power supply issue as well. The module that I bought with the<br>
>> >>>> HDHR did not put out enough current so I got ones rated for more<br>
>> current.<br>
>> >>>><br>
>> >>>> I also had random failures. The computer would lose contact with the<br>
>> >>>> turners every few weeks. I traced it to a linux problem as the tuners<br>
>> were<br>
>> >>>> still visible from a Windows computer on the same network. That<br>
>> >>>> troubleshooting tip was provided by Silicon Dust.<br>
>> >>>><br>
>> >>>> Here is the solution.<br>
>> >>>><br>
>> >>>> dad@NewMyth:~$ more /etc/network/interfaces<br>
>> >>>> # interfaces(5) file used by ifup(8) and ifdown(8)<br>
>> >>>> auto lo<br>
>> >>>> iface lo inet loopback<br>
>> >>>> auto enp2s0<br>
>> >>>> iface enp2s0 inet static<br>
>> >>>> address 192.168.1.111<br>
>> >>>> netmask 255.255.255.0<br>
>> >>>> gateway 192.168.1.1<br>
>> >>>> broadcast 192.168.1.255<br>
>> >>>> dns-nameservers 8.8.8.8 8.8.4.4<br>
>> >>>><br>
>> >>>> Hope this helps.<br>
>> >>>><br>
>> >>>> Allen<br>
>> >>>><br>
>> >>><br>
>> >>> I've set my FE/BE reserved to .210 and the HDHRs to .211, and .212, no<br>
>> >>> change to gateway and netmask, beyond this I need help.<br>
>><br>
>> >><br>
>> >> What you did is not enough. I did that from day 1 and had the problem.<br>
>> >> Perhaps you can ask a specific question based on the fix I posted.<br>
>> >><br>
>> >>><br>
>> >>> OK Allen I'm all in, this is my interfaces file now:<br>
>> > $ cat /etc/network/interfaces<br>
>> ># interfaces(5) file used by ifup(8) and ifdown(8)<br>
>> >auto lo<br>
>> >iface lo inet loopback<br>
>> >auto enp2s0<br>
>> >iface enp2s0 inet static<br>
>> > address 192.168.0.210<br>
>> > netmask 255.255.255.0<br>
>> > gateway 192.168.0.1<br>
>> > broadcast 192.168.0.255<br>
>> > dns-nameservers 8.8.8.8 8.8.4.4<br>
>> >My only question is, where did you get the dns-nameservers values from? Do<br>
>> >I need to edit these?<br>
>><br>
>> You would normally want to use the nameservers that your router should<br>
>> be getting from your ISP. Your router may be able to tell you what<br>
>> they are. Using Google's public nameservers as above should work for<br>
>> most things, but there can be some subtle problems (and benefits). For<br>
>> example, if your ISP runs local CDN servers (say Akamai servers), then<br>
>> anything you would normally have got from the local CDN servers will<br>
>> now be received from some global server somewhere much further away if<br>
>> you use Google DNS. And you may be unable to access ISP services that<br>
>> are provided only to your ISP's customers from this PC.<br>
>><br>
>> If you can find the correct ISP nameserver addresses from your router<br>
>> of maybe from a web page on your ISP's help pages, or by calling their<br>
>> helpdesk, then you can put them here. ISP nameserver addresses<br>
>> normally do not change, but it can happen if they have to reorganise<br>
>> their IP addresses (especially if someone takes them over), and if<br>
>> that happens, then the static IPs that you put here will need to be<br>
>> changed also. It is unlikely that your ISP will inform you if they<br>
>> change the addresses, as your router will normally pick up the new<br>
>> ones automatically. If you use Google's nameservers, then those<br>
>> addresses are extremely unlikely to change. And if they ever do, it<br>
>> will be big news on the Internet. But you are giving Google<br>
>> information about what DNS addresses you are using.<br>
>><br>
>> I think it may be possible to do partial DHCP, where you use a static<br>
>> IP address as above, but get things like the nameserver addresses<br>
>> using DHCP. I have never done that using the interfaces file, but it<br>
>> is probably possible using some scripting. Likely way beyond your<br>
>> capabilities.<br>
>><br>
>> Also, using /etc/network/interfaces on a system that is using<br>
>> NetworkManager as yours is, there can be lots of complications. I<br>
>> found I had to disable NetworkManager to get some things to work, and<br>
>> that may have included the "dns-nameservers" options. It is a very<br>
>> long time ago that I did this, so my recollection is cloudy. So<br>
>> overall I would recommend not doing static IP addresses this way<br>
>> without removing NetworkManager. It gets too complicated.<br>
>><br>
>> Instead, I would recommend that you use the NetworkManager GUI to set<br>
>> a "Manual" IP address. "Manual" is NetworkManager's name for<br>
>> "Static". You can then set the DNS options on the same screen to<br>
>> "Automatic" and that will get the DNS server addresses using DHCP, but<br>
>> have a static IP address. The best of both worlds, unless it was a<br>
>> NetworkManager bug that was causing Allen's problems.<br>
>><br>
>> Click on the NetworkManager icon, usually at the top of the screen,<br>
>> often on the right somewhere. Mine looks like a little white box with<br>
>> a line dropping down to two more little white boxes below it. Click<br>
>> on the cogwheel icon to open the settings for the Ethernet card, then<br>
>> on the "IPv4" tab. Select "IPv4 Method" "Manual" and fill in the<br>
>> "Address" field with the static IP address you want. The "Netmask"<br>
>> field should normally be set to "255.255.255.0" and the "Gateway" to<br>
>> the IPv4 address of your router. Leave the "DNS" and "Routes" options<br>
>> set to "Automatic". Click "Apply".<br>
>> _________________________________________<br>
>><br>
><br>
>I understand what you are saying Stephen, but I have a couple questions. If<br>
>I go the manual method, would I first have to revert my<br>
>"/etc/network/interfaces" file to original state? (I did get successful<br>
>News and NFL recordings on HDHR last night) Secondly, I've employed a fix,<br>
>recommended by this site "<br>
><a href="https://datawookie.netlify.com/blog/2018/10/dns-on-ubuntu-18.04/" rel="noreferrer" target="_blank">https://datawookie.netlify.com/blog/2018/10/dns-on-ubuntu-18.04/</a>" to<br>
>insure that nameserver settings required for my VPN survive a reboot. I<br>
>assume this should be taken into account when using your's or Allen's fix,<br>
>right?<br>
>I just checked and the change to /etc/network/interfaces (Allen's fix) has<br>
>not harmed my VPN usage.<br>
<br>
OK, having set up those DNS settings for the VPN does change things.<br>
You are already using non-ISP DNS servers, and what that fix does, in<br>
a NetworkManager environment, likely overrides any "dns-nameservers"<br>
lines in the interfaces file, if they were not already being ignored<br>
by NetworkManager. So there is no need to change anything from what<br>
you have. You might like to delete or comment out the<br>
"dns-nameservers" line so that it does not fool you at some later date<br>
into thinking that is the right place to change the nameserver<br>
addresses.<br>
<br>
Just be aware that if, at some later time, you want to use something<br>
like an ISP provided multimedia service that is not available outside<br>
the ISP network, it may not work on that PC with the non-ISP DNS<br>
servers being used.<br>
_______________________________________________<br><br></blockquote><div>Daryl, Good to hear you got it working. Stephen brings up some interesting points. A little history. I got this fix from a combination of comments to posts here by Ian Cameron, a bug report on Linux <a href="https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528" target="_blank">https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528</a>, and an article I can't find. Stephen was also helpful in troubleshooting and in particular eliminating the IPv6 issue as a possible cause. I reviewed the thread and see that without the name servers the system appeared to work but was not getting Schedules Direct data so after 2 seeks my recordings stopped. I cannot find the article that suggested adding the name servers but I am pretty sure I got it from a Google search. It did not come from this group. I have static addresses or reserved addresses on the Linux box and the HDHRs. I changed that as an experiment lately and it did not work.</div></div></div>