[mythtv-users] HDHomeRun, 2nd NIC and dhcpd bootup issue
Michael Rice
mikerice1969 at gmail.com
Sun Nov 4 19:16:15 UTC 2007
On 11/4/07, Mitch Gore <mitchell.gore at gmail.com> wrote:
> I have a similar setup. I have two NICs in my BE and want to hook the HDHR
> directly to the BE. i have dhcpd installed but i am not sure what to use in
> the configuration file. My setup gives eth0 a connection to the network and
> then the internet. eth1 i want to hook directly to the HDHR.
>
> Initially i wanted to bridge the two cards so the HDHR would still get an
> address from my router. I couldnt figure that out so i moved to another
> dhcp server. After reading i thought i found something saying this couldn't
> be done.
>
> How did you do it? (could you post the .conf file) I think we need a wiki
> on this. If you could explain it to me then ill figure it out and publish
> the how to.
Ok here is what I did. It seems to be working though I cannot be 100%
sure after such a short time. My backend is running Fedora Core 6.
# yum install dhcp
# chkconfig dhcpd on
My /etc/dhcpd.conf:
ddns-update-style interim;
ignore client-updates;
subnet 192.168.2.0 netmask 255.255.255.0 {
range 192.168.2.20 192.168.2.30;
option broadcast-address 192.168.2.255;
option subnet-mask 255.255.255.0;
option ip-forwarding off;
}
My normal network is on eth0 192.168.1.* which I want to get addresses
from my router.
I setup eth1 with a static address: 192.168.2.10 which is attached to the HDHR.
After reboot I get this in /var/log/messages:
Nov 4 11:04:44 masterbackend dhcpd: Listening on
LPF/eth1/00:00:XX:XX:XX:XX/192.168.2/24
Nov 4 11:04:44 masterbackend dhcpd: Sending on
LPF/eth1/00:00:XX:XX:XX:XX/192.168.2/24
Nov 4 11:04:44 masterbackend dhcpd:
Nov 4 11:04:44 masterbackend dhcpd: No subnet declaration for eth0
(192.168.1.26).
Nov 4 11:04:44 masterbackend dhcpd: ** Ignoring requests on eth0. If
this is not what
Nov 4 11:04:44 masterbackend dhcpd: you want, please write a
subnet declaration
Nov 4 11:04:44 masterbackend dhcpd: in your dhcpd.conf file for
the network segment
Nov 4 11:04:44 masterbackend dhcpd: to which interface eth0 is attached. **
Nov 4 11:04:44 masterbackend dhcpd:
Nov 4 11:04:44 masterbackend dhcpd: Sending on Socket/fallback/fallback-net
Nov 4 11:04:44 masterbackend dhcpd: dhcpd startup succeeded
I think ignoring eth0 is what I want. Then:
Nov 4 11:04:45 masterbackend dhcpd: DHCPDISCOVER from
00:YY:YY:YY:YY:YY(HDHR-1011D84D) via eth1
Nov 4 11:04:46 masterbackend dhcpd: DHCPOFFER on 192.168.2.30 to
00:YY:YY:YY:YY:YY(HDHR-1011D84D) via eth1
Nov 4 11:04:47 masterbackend dhcpd: DHCPREQUEST for 192.168.2.30
(192.168.2.10) from 00:YY:YY:YY:YY:YY(HDHR-1011D84D) via eth1
Nov 4 11:04:47 masterbackend dhcpd: DHCPACK on 192.168.2.30 to
00:YY:YY:YY:YY:YY(HDHR-1011D84D) via eth1
Looks good.. check the mythbackend.log:
2007-11-04 11:04:51.922 HDHRChan(ffffffff/0): device found at address
192.168.2.30
2007-11-04 11:04:52.100 HDHRChan(ffffffff/1): device found at address
192.168.2.30
I will reply if I have any problems with this down the road.
More information about the mythtv-users
mailing list