[mythtvnz] HDHomeRun discover not working

[Mark Kendall]

> So you had it on a dedicated local LAN segment that was isolated between
> the HDH and the Mythserver.
Yes, it was isolated so that only Mythserver & HDHomeRun was on it and the
subnet was set so that hdhomerun auto set it's own IP address (169...
something range I think, whatever SiliconDust specified)

>
> Now you've put the HDH on the main LAN and accessing it directly from
> other clients, but Mythtv can't find it?
Yet, it's now on the same LAN as the MythTV clients.  A VM running on the
Myth server can auto discover it, haven't tried from any other client as
not much else up and running yet and the VM test showed that the unit was
working.

>
> Sounds like you need to give the HDH a dedicated IP address, either on the
> device or by doign a DHCP reservation in your router.  Either is fine, as
> long as it means that your HDH is always at the same IP addresses.
>
Along with wiresharking that's what I was looking at doing next if I
couldn't get discovery to work but read that there is (or was at some
point) an issue if attempting to use multiple tuners

>
> Note it might have been using IPv6 addressing too - hard to know.
Pretty sure it was all IPv4 before, access at present is via IPv4 it just
seems as though it's the UDP discovery that's a problem and since it works
on another machine it all points to something different on the Ubuntu
17.10 server.

>
> And congrats on the house rebuild - that's truly terrifying.
Yes it was major, glad to have it (or at least the bulk of it) behind us.

>
>
> Mark Kendall wrote:
>> We've been without DVB-T for about a year and half due to house
>> re-build,
>> just got the aerial installed again and have found that a couple of
>> things
>> related to network and dual tuner hdhomerun don't work anymore.
>>
>> The server has had a lot of Mythbuntu/Ubuntu upgrades in the past 6 or
>> so
>> years and was updated from fully working (16.04 I think) to 17.10
>> earlier
>> in the year.
>> hdhomerun was previously plugged into a USB ethernet adapter that had a
>> udev
>> rule for it to always be eth1 and eth1 was also set for a static ip. 
>> With
>> the new 17.10 network setup the eth1 network works if I plug the USB
>> ethernet adapter into a network switch but can not be enabled if I plug
>> it
>> into the hdhomerun (also tried using cross over cables just in case but
>> still no joy).
>> So, I thought for the moment I'll just put the hdhomerun on the main
>> network
>> and use it there for now, unfortunately it doesn't auto discover when
>> there,
>> either on a basic POE switch nor on our ADSL modem/router/switch.
>> The hdhomerun is working, I can access it via webpage with IP address
>> and
>> can use hdhomerun_config if I specify IP address.  It'll also auto
>> discover
>> if I fire up an old VM on my server and attempt auto discovery from the
>> VM.
>> No iptables firewall settings are in place.
>> The main eth0 network adapter use to have a couple of IP addresses
>> associated with it, I've simplified this down to one address with a
>> standard 255.255.255.0 mask
>>
>> I may look at setting a fixed DHCP address for the hdhomerun and
>> specifying
>> the IP address in mythbuntu but I read somewhere that this may be an
>> issue
>> when using more than 1 tuner.
>>
>> Anyone out there have any thoughts on what else I can look into to get
>> the
>> auto discovery working again?
>>
>> Cheers
>> Mark
>>
>
>
> --
> Criggie
>
> http://criggie.org.nz/
>
>
>
>
> _______________________________________________
> mythtvnz mailing list
> mythtvnz at lists.ourshack.com
> https://lists.ourshack.com/mailman/listinfo/mythtvnz
> Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/
>