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

[Stephen Worthington]

On Sun, 28 Apr 2013 14:00:32 +1200, you wrote:

>
>>
>> Well, it worked on my laptop, so there must be something different on
>> your system.  I have been presuming that your WiFi port was getting
>> its IP address by DHCP either from your WiFi router or your Internet
>> router (if they are not one and the same thing).  Is that true?  That
>> was the setup I was running with my laptop.  That config should have
>> had no affect whatsoever on the WiFi interface - are you sure you set
>> the INTERFACE="eth0" in the /etc/default-isc-dhcp-server file?
>>
>> We need quite a bit more information to work out what went wrong. What
>> does ifconfig show?  What does dhcpd -t show?  What does grep -i dhcp
>> /var/log/syslog show (just the bits for the latest boot)?
>>
>> And there was nothing in that config that should have changed the IPv6
>> operation either.  The ip6 message may be a red herring - it could
>> well have been occurring before.  Please check back in the logs before
>> the change of config to see.
>>
>INTERFACE="eth0" was set as requested
>
>ifconfig:
>
>  ifconfig
>eth0      Link encap:Ethernet  HWaddr 14:da:e9:dc:51:a1
>           inet addr:10.99.0.1  Bcast:10.99.0.255  Mask:255.255.255.0
>           inet6 addr: fe80::16da:e9ff:fedc:51a1/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:15 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:154 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:4566 (4.5 KB)  TX bytes:22070 (22.0 KB)
>           Interrupt:47 Base address:0xc000
>
>lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:639 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:639 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:70477 (70.4 KB)  TX bytes:70477 (70.4 KB)
>
>wlan2     Link encap:Ethernet  HWaddr f8:d1:11:10:e6:76
>           inet addr:192.168.2.2  Bcast:192.168.2.255  Mask:255.255.255.0
>           inet6 addr: fe80::fad1:11ff:fe10:e676/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:38 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:119 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:5996 (5.9 KB)  TX bytes:20130 (20.1 KB)

This is strange - why is your WiFi interface coming up as wlan2 ? Does
that PC have multiple WiFi cards?  It should be wlan0 !

The syslogdhcp file shows wlan2 getting its IP address correctly from
the DHCP server on the WiFi connection, and the above shows a good
IPv4 configuration, so it should work as long as wlan2 is the correct
interface name.  Can you ping anything (eg 192.168.2.1) over the WiFi
connection using IP addresses rather than names?  What does the
"route" command report?

>dhcpd -t gives the output:
>
>dhcpd -t
>drop_privileges: could not set group id: Operation not permitted
>
>so I tried sudo:
>
>myth at myth:~$ sudo dhcpd -t
>[sudo] password for myth:
>
>Internet Systems Consortium DHCP Server 4.1-ESV-R4
>Copyright 2004-2011 Internet Systems Consortium.
>All rights reserved.
>For info, please visit https://www.isc.org/software/dhcp/

Ah, yes, I always run from root unless I really need to be running
from a different login, so I often forget to tell people to do sudo.

>grep -i dhcp /var/log/syslog  output text file attached   System rebooted  
>at 13:42
>
>Paul

The syslogdhcp file clearly shows that the config for dhcpd is mangled
somehow.  The dhcpd server is not seeing the setup for eth0.  Googling
the "No subnet declaration for eth0 (no IPv4 addresses)" message shows
that is usually caused by the /etc/default-isc-dhcp-server file not
having been set up, and the second most common problem was a syntax
error in /etc/dhcp/dhcpd.conf.  Please post both of these files and I
will try running the exact files on my laptop to see if anything shows
up.