[mythtv-users] MediaMVP and Myth

[Jeff volckaert]

> After a few days I figured out that with out using the Myth box as DHCP you
> can get into problems with the MediaMVP booting. Specifically the BOOTP
> protocol is implemented with the DHCP, thus if you have another box doing
> DHCP the mediaMVP will get IP address from DHCP sever and since it does not
> have a boot image it will then send a bootp request on port 16867, thus you
> have to implement a bootp server on the myth box which listens on port
> 16867. I have not figured out how to implement the bootp server quite yet,
> but did find some C code where others have written their own custom solution
> for this problem.
Why not just have the Myth box do DHCP for the network?  Below is the
config I use.

Jeff

# DHCP configuration generated by Firestarter
ddns-update-style interim;
ignore client-updates;

subnet 192.169.0.0 netmask 255.255.255.0 {
        option routers 192.169.0.1;
        option subnet-mask 255.255.255.0;
        option domain-name-servers 65.43.19.26,206.141.192.60;
        option ip-forwarding off;
        range dynamic-bootp 192.169.0.100 192.169.0.254;
        default-lease-time 21600;
        max-lease-time 43200;
}

group {
  next-server 192.169.0.1;          # IP address of your TFTP server

  host mvp {
           hardware ethernet  00:0d:fe:00:8a:81;
           fixed-address 192.169.0.40;
           filename "dongle.bin.mvpmc";
           option root-path "/home/mvp,rsize=4096,wsize=4096,nolock";
  }

}