Tom Metro wrote:
> JP Vossen wrote:
>> The Hauppauge boot loader *is* getting the correct DHCP address (as 
>> confirmed by the firmware network info menu above, the tftp of the 
>> dongle.bin, and Wireshark).  Per the wiki and your comments above, 
>> between the 7th and 8th square, *mvpmc* is supposed to DHCP again, and 
>> I don't see that.
> 
> OK, well I'd ignore everything else and focus on resolving that, because 
> if it fails, the rest is irrelevant.

Good point.


> Are you sure the 2nd DHCP request isn't happening? Have you confirmed 
> that with your DHCP server logs?

I have now:

$ tail -f dhcpd.log | grep -i '00:0D:FE:22:5E:A2'
# Firmware boot:
Oct 31 18:24:35 drake dhcpd: DHCPDISCOVER from 00:0d:fe:22:5e:a2 via eth0
Oct 31 18:24:35 drake dhcpd: DHCPOFFER on 192.168.xx.92 to 
00:0d:fe:22:5e:a2 via eth0
Oct 31 18:24:35 drake dhcpd: DHCPREQUEST for 192.168.xx.92 
(192.168.99.11) from 00:0d:fe:22:5e:a2 via eth0
Oct 31 18:24:35 drake dhcpd: DHCPACK on 192.168.xx.92 to 
00:0d:fe:22:5e:a2 via eth0
# mvpmc boot = nothing...  :-(


>> I did a Wireshark capture (filter: host 192.168.xx.92) of the whole 
>> thing via a hub and see...
> 
> Remember, the DHCP request won't necessarily originate from the MVP's IP 
> address if it has already relinquished the lease. Also, the destination 
> will be a broadcast address. So your Wireshark filter may be too 
> restrictive to see the DHCP requests.

Yup.  Changed to "port 68 or port 68 or host 192.168.xx.92".  Same deal, 
though I get some other DHCP at the end since this is the regular LAN 
DHCPD too.


> The 2nd DHCP request might be getting sent, but your DHCP server may be 
> failing to respond in an expected way, or may be assigning an unexpected 
> IP address.

Not finding it in the DHCPD logs or Wireshark.  :-(


> Anything change in your DHCP server setup since your last working cold 
> boot?

Not that I recall.  It works for the firmware request and it should be 
getting the same thing for the mvpmc request, except I'm not even seeing 
that.  And it works for the rest of the machines on the LAN, and has 
been working for years.  It's the stock ISC DHCP in Debian Etch.

Thanks,
JP
----------------------------|:::======|-------------------------------
JP Vossen, CISSP            |:::======|        jp{at}jpsdomain{dot}org
My Account, My Opinions     |=========|      http://www.jpsdomain.org/
----------------------------|=========|-------------------------------
"Microsoft Tax" = the additional hardware & yearly fees for the add-on
software required to protect Windows from its own poorly designed and
implemented self, while the overhead incidentally flattens Moore's Law.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/

Reply via email to