[mythtvnz] hdhomerun doesn't connect on restart when connected directly to the lan port

[Stephen Worthington]

On Fri, 26 Apr 2013 11:23:59 +1200, you wrote:

>On Thu, 25 Apr 2013 20:51:04 +1200, Nick Rout <nick.rout at gmail.com> wrote:
>
>>
>>
>> On Thu, Apr 25, 2013 at 4:21 PM, Stephen Worthington  
>> <stephen_agent at jsw.gen.nz> wrote:
>>> On Thu, 25 Apr 2013 13:23:01 +1200, you wrote:
>>>
>>>> On Thu, 25 Apr 2013 12:25:23 +1200, Steve Hodge <stevehodge at gmail.com>
>>>> wrote:
>>>>
>>>>> On Thu, Apr 25, 2013 at 11:23 AM, Paulgir <paulgir at gmail.com> wrote:
>>>>>> On Thu, 25 Apr 2013 08:59:50 +1200, Steve Hodge  
>>>>>> <stevehodge at gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> http://www.silicondust.com/hdhomerun/hdhomerun_tech.pdf
>>>>>>> Note that it states that the hdhomerun takes 20 seconds from link-up
>>>>>>> until it can be  addressed using a link-local address. >>>That's  
>>>>>>> what
>>>>>>> is causing the problems for Paul.
>>>>>>>
>>>>>>> I'd also recommend a static address or a DHCP server. Static  
>>>>>>> addresses
>>>>>>> can be assigned using hdhomerun_config. Get the >>>hdhomerun working
>>>>>>> using a link-local address then do:
>>>>>>> hdhomerun_config <old ip> set /sys/ipaddr “<new ip> <subnet>  
>>>>>>> <gateway>”
>>>>>>> e.g. hdhomerun_config 169.254.227.211 set /sys/ipaddr “10.99.0.2
>>>>>>> 255.255.0.0 10.99.0.1”
>>>>>>>
>>>>>>> To revert to DHCP/link-local addressing do:
>>>>>>> hdhomerun_config 10.99.0.2 set /sys/ipaddr dhcp
>>>>>>>
>>>>>> Thanks for that.
>>>>>> I used hdhomerun_config discover to find the current address,
>>>>>> Then ran: hdhomerun_config 169.254.131.162 set /sys/ipaddr "10.99.0.2
>>>>>> 255.255.255.0 10.99.0.1"
>>>>>> then I got this message: "ERROR: unknown getset variable"
>>>>> You can tryhdhomerun_config 169.254.131.162 get help
>>>>> to see if that sheds any light on it. I don't have one to test with
>>>>> sorry.
>>>>>
>>>>> Otherwise set up a dhcp server.
>>>>>
>>>>> Cheers,
>>>>> Steve
>>>>>
>>>> I've installed a dhcp server but I'm a bit lost on how to set it.
>>>> Do I use these values 169.254.131.162   255.255.255.0   10.99.0.1   ?
>>>>
>>>> Paul
>>>
>>> Presuming that you installed the usual isc-dhcp-server package, then
>>> this page looks like a good tutorial:
>>>
>>>
>>> http://www.cyberciti.biz/faq/howto-ubuntu-debian-squeeze-dhcp-server-setup-tutorial/
>>>
>>> Stop dhcpd if it is running:
>>>
>>>  service isc-dhcp-server stop
>>>
>>> Edit /etc/default/isc-dhcp-server and change the line:
>>>  INTERFACES=""
>>> to:
>>>  INTERFACES="eth0"
>>>
>>> Do an "ifconfig -a" command, and find the HWaddr value for the eth0
>>> interface.  Also find the IP address of your WiFi interface.  You will
>>> need these values later.
>>>
>>> Edit /etc/dhcp/dhcpd.conf.
>>>
>>> Change the "options domain-name" line to your domain name if you have
>>> one.  If not, I think you need to just comment out that line with a #
>>> in front.  It is possible you may need to use your ISP's domain name.
>>> I have my own domain so I have always just used that.
>>>
>>> Change the "options domain-name-server" line to the DNS server
>>> addresses you use.  If you run your own DNS servers like I do, then
>>> use their addresses.  Otherwise, find out the DNS servers that your
>>> ISP provides and use their addresses.  They will likely be stored in
>>> your Internet router somewhere, and your ISP can tell you if they do
>>> not have them listed on a web page.  You can easily find out the
>>> primary address by just doing a command like:
>>>
>>>  nslookup easynews.com
>>>
>>> The address in the "Server:" line of the response is the primary DNS
>>> server you have configured.  There will usually be at least two DNS
>>> servers though, so it is best to have both listed if possible.
>>>
>>> Note that the "options domain-name-server" line is not necessary for
>>> your HDHomerun as it does not do DNS lookups, so you could just
>>> comment out that line too.  But if you ever connect anything else to
>>> eth0 it would be good to have it configured so things work properly.
>>>
>>> Uncomment the "#authoritative;" line.
>>>
>>> Add the following host and subnet declarations to dhcp.conf:
>>>
>>> host <name of your MythTV PC with -eth0 on the end> {
>>>  hardware ethernet <your eth0 HWaddr>;
>>>  fixed-address 10.99.0.1;
>>> }
>>>
>>> subnet 10.99.0.0 netmask 255.255.255.0 {
>>>  range 10.99.0.50 10.99.0.250;
>>>  option subnet-mask 255.255.255.0;
>>>  option broadcast-address 10.99.0.255;
>>>  option routers <your MythTV box WiFi ip address>;
>>> }
>>>
>>> Note that the "option routers" line above is optional as your
>>> HDHomerun will not need it.  If it is assigned by a DHCP server
>>> somewhere, it may change and you should not put the "options routers"
>>> line until you have configured it also with a static IP address.
>>>
>>> Run:
>>>
>>>  dhcpd -t
>>>
>>> to check for any syntax errors in dhcpd.conf.
>>>
>>> Now start the DHCP server:
>>>
>>>  service isc-dhcp-server start
>>>
>>> (I think "start isc-dhcp-server" also works).
>>>
>>> Wait for a few seconds for the HDHomerun to get an address and try to
>>> talk to it.  It should now have an address in the range specified in
>>> the subnet declaration, likely 10.99.0.50.  You may need to disconnect
>>> it and reconnect it to force it to ask for a DHCP address again.  Or
>>> even cycle its power.
>>
>> I haven't read all this thread, and I am simply replying to the last  
>> message, but I don't think the HDHR does static IP. It >is link-local or  
>> dhcp. Hope that clears u a few misconceptions.
>>>
>>>
>Any need to include ' ddns-update-style none; ' or set lease time or  
>maximum lease time?
>
>Paul

The "ddns-update-style none;" looks like a good idea, but is
unnecessary for just an HDHomerun, which does not do DDNS.

Setting the lease times just affects how often the HDHomerun will need
to renew its lease.  The defaults are fine (every 2 hours), but if you
want to increase it, that works too.  I am not sure why that page is
recommending a one day timeout.  In a busy network, there are
tradeoffs between longer and shorter timeouts.  If there are devices
being connected and disconnected all the time (eg people walking
through a WiFi zone with cellphones and tablets with WiFi on), then
with a longer lease time you can run out of IP addresses as they will
hang around waiting for the device to reconnect again until the lease
expires.  But a shorter lease time increase the traffic a bit.