<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jan 2, 2023 at 7:30 PM Bill Meek <<a href="mailto:keemllib@gmail.com">keemllib@gmail.com</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 1/2/23 18:18, James Abernathy wrote:<br>
> <br>
> <br>
> On Mon, Jan 2, 2023 at 7:05 PM Bill Meek <<a href="mailto:keemllib@gmail.com" target="_blank">keemllib@gmail.com</a> <mailto:<a href="mailto:keemllib@gmail.com" target="_blank">keemllib@gmail.com</a>>> wrote:<br>
> <br>
> On 1/2/23 17:51, James Abernathy wrote:<br>
> ><br>
> ><br>
> > On Mon, Jan 2, 2023 at 6:44 PM Bill Meek <<a href="mailto:keemllib@gmail.com" target="_blank">keemllib@gmail.com</a> <mailto:<a href="mailto:keemllib@gmail.com" target="_blank">keemllib@gmail.com</a>> <mailto:<a href="mailto:keemllib@gmail.com" target="_blank">keemllib@gmail.com</a><br>
> <mailto:<a href="mailto:keemllib@gmail.com" target="_blank">keemllib@gmail.com</a>>>> wrote:<br>
> ><br>
> > On 1/2/23 16:55, James Abernathy wrote:<br>
> > ><br>
> > ><br>
> > > On Mon, Jan 2, 2023 at 5:42 PM James <<a href="mailto:jam@tigger.ws" target="_blank">jam@tigger.ws</a> <mailto:<a href="mailto:jam@tigger.ws" target="_blank">jam@tigger.ws</a>> <mailto:<a href="mailto:jam@tigger.ws" target="_blank">jam@tigger.ws</a> <mailto:<a href="mailto:jam@tigger.ws" target="_blank">jam@tigger.ws</a>>><br>
> <mailto:<a href="mailto:jam@tigger.ws" target="_blank">jam@tigger.ws</a> <mailto:<a href="mailto:jam@tigger.ws" target="_blank">jam@tigger.ws</a>> <mailto:<a href="mailto:jam@tigger.ws" target="_blank">jam@tigger.ws</a> <mailto:<a href="mailto:jam@tigger.ws" target="_blank">jam@tigger.ws</a>>>>> wrote:<br>
> > ><br>
> > ><br>
> > ><br>
> > > > On 3 Jan 2023, at 6:27 am, James Abernathy <<a href="mailto:jfabernathy@gmail.com" target="_blank">jfabernathy@gmail.com</a> <mailto:<a href="mailto:jfabernathy@gmail.com" target="_blank">jfabernathy@gmail.com</a>><br>
> <mailto:<a href="mailto:jfabernathy@gmail.com" target="_blank">jfabernathy@gmail.com</a> <mailto:<a href="mailto:jfabernathy@gmail.com" target="_blank">jfabernathy@gmail.com</a>>> <mailto:<a href="mailto:jfabernathy@gmail.com" target="_blank">jfabernathy@gmail.com</a> <mailto:<a href="mailto:jfabernathy@gmail.com" target="_blank">jfabernathy@gmail.com</a>><br>
> > <mailto:<a href="mailto:jfabernathy@gmail.com" target="_blank">jfabernathy@gmail.com</a> <mailto:<a href="mailto:jfabernathy@gmail.com" target="_blank">jfabernathy@gmail.com</a>>>>> wrote:<br>
> > > ><br>
> > > > When I have my HDHR Quatro tuner connected to my router I'd just use a local-network-pingable service to wait until the<br>
> tuners were<br>
> > > pingable.<br>
> > > > That works, but to reduce a lot of the network errors I was getting with the HDHR tuners I've been directly connecting them.<br>
> > That's been<br>
> > > working great with no errors due to the connection. But I've been restarting the backend manually to make sure the tuners were up.<br>
> > > ><br>
> > > > You can't use the pingable method of delaying the backend because the 169.254.x.x IP of the HDHR changes every boot. This<br>
> doesn't<br>
> > affect<br>
> > > mythtv-backend because it uses the tuner ID so I need a new method of waiting on the tuners.<br>
> > ><br>
> > > Jim I don't know how you do DNS. I use dnsmasq but every router/modem I've seen also allows you to assign a mac address to an<br>
> IP so you<br>
> > > always get the same IP on the same device<br>
> > > James<br>
> > ><br>
> > > If I was connected to a router that is what I do. In this case I'm directly connecting the HDHR tuner to a 2nd port on my NUC PC. In<br>
> > that case<br>
> > > the HDHR will assign itself an IP of 169.254.x.x randomly on the x's. I just set up my PC port to a static IP of 169.254.0.1 with a<br>
> > subnet mask<br>
> > > of 255.255.0.0. That all works, it is just the delaying function that is killing me. I guess I could do a delay on the<br>
> mythtv-backend to<br>
> > wait<br>
> > > for a mythtv-backend.timer to start 1 minute after boot. But who wants to introduce a race condition.<br>
> > IPv4 Link Local on the host shouldn't have an address assigned either.<br>
> > The two ends will figure their addresses out. Link Local should be an<br>
> > option if you're setting the NIC up with some tool.<br>
> ><br>
> > I DON'T think this is the issue, but it's the right thing to do.<br>
> ><br>
> > Try:<br>
> ><br>
> > hdhomerun_config 1074C841 get /tuner0/status<br>
> ><br>
> > the above after a restart and successful MANUAL discover command.<br>
> ><br>
> > I'd disable backend startup to test ideas that prove tuners are<br>
> > available (which is what the backend log is complaining about:<br>
> ><br>
> > ... Added 0 devices from 1074C841 ...<br>
> ><br>
> ><br>
> ><br>
> > Bill<br>
> ><br>
> ><br>
> > Thanks, that will give me some stuff to try. I did play with the hdhomerun_check.py program. After it had a successful "hdhomefun_config<br>
> > discover" command I tried different sleep delays until I found what worked. 10 seconds allowed the backend to connect with 2 tuners and 20<br>
> > seconds found all 4.<br>
> ><br>
> > I'll try working on some of your suggestions.<br>
> <br>
> The additional delay is interesting. I'd start with the Link Local fix.<br>
> Here's what NIC's settings look like:<br>
> <br>
> [802-3-ethernet]<br>
> duplex=full<br>
> mac-address=00:AB:CD:EF:00:11<br>
> <br>
> [connection]<br>
> id=eth1<br>
> uuid=very long hex string here<br>
> type=802-3-ethernet<br>
> timestamp=1386355229<br>
> <br>
> [ipv6]<br>
> method=ignore<br>
> <br>
> [ipv4]<br>
> method=link-local<br>
> dhcp-send-hostname=false<br>
> <br>
> -- <br>
> Bill<br>
> <br>
> <br>
> Thanks, the Direct connection is set to local-link and works.<br>
> <br>
> With the mythtv-backend disabled at boot, I logged in and opened a terminal then did:<br>
> [jim@den-pc ~]$ hdhomerun_config 1074c841 get /tuner0/status<br>
> unable to connect to device<br>
> [jim@den-pc ~]$ hdhomerun_config 1074c841 get /tuner0/status<br>
> unable to connect to device<br>
> [jim@den-pc ~]$ hdhomerun_config 1074c841 get /tuner0/status<br>
> unable to connect to device<br>
> [jim@den-pc ~]$ hdhomerun_config 1074c841 get /tuner0/status<br>
> ch=none lock=none ss=0 snq=0 seq=0 bps=0 pps=0<br>
> [jim@den-pc ~]$ hdhomerun_config discover<br>
> hdhomerun device 1074C841 found at fe80::218:ddff:fe07:4c84%2<br>
> hdhomerun device 1074C841 found at 169.254.208.100<br>
> <br>
> As you can see even after all that time it still has problems getting status. Maybe I should use the get status command in the <br>
> hdhomerun_check.py command as a test?<br>
> <br>
> Jim A<br>
<br>
In the configuration for the NIC, can you set IPv6 to off?<br>
I've never used mine with it. An IPv6 address starting with<br>
fe80:: is also for Link Local.<br>
<br>
If you added the get /tuner/status to the script, you'd need to<br>
capture the 1074C841 from its output. Or [ugh!] hard code it.<br>
<br>
IPv6 can be turned off for eth0 with sysctl. Yours must be on<br>
<br>
sysctl --all --pattern net.ipv6.conf.eth0.disable_ipv6<br>
<br>
<br>
-- <br>
Bill<br><br></blockquote><div><br></div><div>Under /etc/NetworkManager/system-connections I have one file for each NIC. The one for direct connection to the HDHR is call:</div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0)">'Direct HDHR connection.nmconnection' and contains:</span><br></span></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0)">[connection]
</span><br>id=Direct HDHR connection
<br>uuid=b33af363-242f-4e2a-921e-3e445bb93369
<br>type=ethernet
<br>
<br>[ethernet]
<br>auto-negotiate=true
<br>mac-address=A8:A1:59:6B:0A:44
<br>
<br>[ipv4]
<br>may-fail=false
<br>method=link-local
<br>
<br>[ipv6]
<br>method=ignore
<br>
<br>[proxy]<br>
<br></span></div><div><span style="font-family:monospace">I tried </span></div><div># sysctl --all --pattern net.ipv6.conf.eno1.disable_ipv6</div><div class="gmail_quote">it returned: net.ipv6.conf.eno1.disable_ipv6 = 0</div><div class="gmail_quote"><br></div><div class="gmail_quote">The discover still show both:</div><div class="gmail_quote"><span style="font-family:monospace"><span style="color:rgb(0,0,0)">hdhomerun device 1074C841 found at fe80::218:ddff:fe07:4c84%2
</span><br>hdhomerun device 1074C841 found at 169.254.208.100<br>
<br></span></div><div class="gmail_quote"><span style="font-family:monospace">Thanks for all your help. I got something to work with now. Just need to modify the code for the delay.</span></div><div class="gmail_quote"><span style="font-family:monospace"><br></span></div><div class="gmail_quote"><span style="font-family:monospace">Jim A</span></div><div class="gmail_quote"><span style="font-family:monospace"><br></span></div></div></div>