Dave wrote: > ...it looks like the problem is dhcp related. Agreed.
> Here's the logs: > > Dec 6 21:47:00 myMythBE dhcpd: DHCPDISCOVER from 00:0d:fe:00:xx:xx via > eth0 > Dec 6 21:47:00 myMythBE dhcpd: DHCPOFFER on 192.168.2.203 to > 00:0d:fe:00:xx:xx via > eth0 > Dec 6 21:47:18 myMythBE dhcpd: DHCPDISCOVER from 00:0d:fe:00:xx:xx via > eth0 > Dec 6 21:47:18 myMythBE dhcpd: DHCPOFFER on 192.168.2.203 to > 00:0d:fe:00:xx:xx via > eth0 It appears to be cycling between discover/offer, and never completing the DHCP transaction. A normal DHCP transaction involves the exchange of 4 packets: 1. Client sends a discover broadcast. 2. Any listening DHCP servers send back an offer packet. 3. The client picks an offer it likes, and responds to a specific DHCP server. 4. That DHCP server sends back an acknowledgment, which contains basically the same info as in the offer. (Check the list archives for log transcripts of a full successful exchange. A successful mvpmc boot will have two sets, as it also requests an IP via DHCP as part of its startup process.) The latter two packets don't appear to be showing up in your log. That seems to suggests that the MVP's bootloader firmware either doesn't like the offer, or it is accepting another DHCP server's offer, failing to find the dongle where expected, and restarting the boot sequence. You did turn off DHCP in your Netgear router, right? -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/
