Dave wrote: >>> This particular unit stopped booting after I edited the >>> /etc/udhcpc.config file via telnet. > >> I don't see how that could have a persistent effect. > > ...it seems like > prior settings were indeed saved because the device had been used on my > network previously and it worked without any special DHCP server setup > (until I edited that file).
Yes, it seems your observations do suggest that the boot server is being stored persistently. So you're saying before you started using mvpmc, you were using this same MVP on your LAN running SageTV provided firmware? Was the IP address that it used as a boot server the same as what you were initially used as an mvpmc boot server? That would explain how you were initially able to get it booting without a custom DHCP setup. I do buy the theory that the MVP rev. D hardware might store the boot server's IP address in Flash, and something might have happened to clear/change it, I just think it is unlikely that modifying the file in /etc itself caused the change. But who knows. > Is this config file anywhere close to being correct? I have questions about > > * domain-name-servers > * option root-path > * option broadcast-address > * option routers > > I'm not sure of the values that go in those options. I'll offer a few suggestions, but I don't use dhcpd, so I'll leave it to others to respond. The wiki does contain a few sample dhcpd configs, such as: http://mvpmc.wikispaces.com/dhcp > option domain-name "my-example.com <http://my-example.com>"; That should be set to the domain you use on your LAN, or "local." > #option domain-name-servers ????????????; #how do I assign my ISP's name > servers dynamically? Yeah, I'm not sure how that is done with dhcpd. With Dnsmasq, it has a default configuration to use itself as the DNS server (because it includes a DNS proxy), and in turn it gets your upstream DNS servers from the DHCP client running on the local server. > subnet 192.168.2.0 netmask 255.255.255.0 { > option domain-name "my-example.com <http://my-example.com>"; You can probably omit options like this that are the same as the global settings. > option broadcast-address 192.168.2.251; #my Netgear router The broadcast address is generally your subnet with .255 on the end, or 255.255.255.255. You can probably omit this and dhcpd or the client will fill in a reasonable default. The wiki example seems to omit this. > option root-path "/tftpboot,rsize=4096,wsize=4096,nolock"; #what > path goes here??? I think what you have is correct, if you pass /tftpboot/mvp.bin to a TFTP client running on another machine and it successfully retrieves the dongle. -Tom ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
