| 1 |
On Mon, Mar 02, 2015 at 12:33:11AM +0000, Stroller wrote |
| 2 |
|
| 3 |
> About 10 days ago, Mick already suggested you configure you HDhomerun with a more appropriate IP address. |
| 4 |
> |
| 5 |
> http://archives.gentoo.org/gentoo-user/message/61171ddc1dfe80924ebc833060d06734 |
| 6 |
> |
| 7 |
> I have not seen you address this. I cannot comprehend why not. |
| 8 |
|
| 9 |
This is what I get for TTFM (Trusting The Fine Manual). I did Google |
| 10 |
and RTFM. Page 6 of the PDF document at the manufacturer's website... |
| 11 |
http://www.silicondust.com/hdhomerun/hdhomerun_tech.pdf lists the output |
| 12 |
from a "get help" command ***FOR CURRENT MODELS***. It includes, |
| 13 |
amongst other items... |
| 14 |
|
| 15 |
/sys/ipaddr dhcp|"<ip> <mask> <gw> <dns>" |
| 16 |
|
| 17 |
On my machine, "get help" produces... |
| 18 |
|
| 19 |
Supported configuration options: |
| 20 |
/ir/target <protocol>://<ip>:<port> |
| 21 |
/lineup/location <countrycode>:<postcode> |
| 22 |
/sys/copyright |
| 23 |
/sys/debug |
| 24 |
/sys/features |
| 25 |
/sys/hwmodel |
| 26 |
/sys/model |
| 27 |
/sys/restart <resource> |
| 28 |
/sys/version |
| 29 |
/tuner<n>/channel <modulation>:<freq|ch> |
| 30 |
/tuner<n>/channelmap <channelmap> |
| 31 |
/tuner<n>/debug |
| 32 |
/tuner<n>/filter "0x<nnnn>-0x<nnnn> [...]" |
| 33 |
/tuner<n>/lockkey |
| 34 |
/tuner<n>/program <program number> |
| 35 |
/tuner<n>/streaminfo |
| 36 |
/tuner<n>/status |
| 37 |
/tuner<n>/target <ip>:<port> |
| 38 |
|
| 39 |
There is no mention of "/sys/ipaddr" ***ON MY MACHINE***. I also |
| 40 |
remember various people asking on the HDHomerun support forum years ago |
| 41 |
about IP addresses, and hearing that this model did not have any other |
| 42 |
addressing options. One correction on the date of my machine. See |
| 43 |
https://www.youtube.com/watch?v=JXmi-6nVhCM which discusses the exact |
| 44 |
same model I have. I bought mine in 2010, but the reviewer notes that |
| 45 |
it won some award at CES2008. Consider it a 2008 model. |
| 46 |
|
| 47 |
Due to the documentation, and lack of mention of DHCP in "get help", I |
| 48 |
assumed it wouldn't work. However, just for ####s and giggles, I |
| 49 |
enabled the DHCP server on my router, set the DHCP address pool to |
| 50 |
192.168.123.241-to-192.168.123.247, and expanded my local LAN subnet |
| 51 |
from a /29 to a /28 like so... |
| 52 |
|
| 53 |
config_eth0=" |
| 54 |
192.168.123.251/28 broadcast 192.168.123.255" |
| 55 |
routes_eth0=" |
| 56 |
default via 192.168.123.254 metric 20 |
| 57 |
192.168.123.240/28 via 192.168.123.254 metric 0" |
| 58 |
|
| 59 |
Notice the lack of a 'modules=( "!iproute2" )' line. I installed the |
| 60 |
latest firmware update from the manufacturer's website... |
| 61 |
(hdhomerun_atsc_firmware_20141124.bin). Lo and behold, it actually |
| 62 |
works, coming up at 192.168.123.241. This is notwithstanding the |
| 63 |
documentation and "get help" output, which both say nothing about DHCP. |
| 64 |
Maybe this was a feature that was backported into a firmware update. |
| 65 |
Anyhow, I apologize for wasting peoples' time. |
| 66 |
|
| 67 |
-- |
| 68 |
Walter Dnes <waltdnes@××××××××.org> |
| 69 |
I don't run "desktop environments"; I run useful applications |
Archives