<html><body bgcolor="#FFFFFF"><div><span>Michael,</span><br><span></span><br><span>Thanks for the reply. I'll try those options. </span></div><div><br></div><div><span></span><span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); font-size: 15px; font-family: Calibri, sans-serif; ">I'm also trying to understand dhcp.h, and I am not very familiar with C. I'm not sure how to make it so that iPXE uses #define BOOTP_FL_BROADCAST 0x8000 in dhcp.h.<br><br>So how can I ensure that iPXE uses #define BOOTP_FL_BROADCAST 0x8000 when doing DHCP? I'm experimenting with a broadcast response instead of unicast, that's how my other PXE clients are set up.</span></div><div><font class="Apple-style-span" face="Calibri, sans-serif" size="4"><span class="Apple-style-span" style="font-size: 15px; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469);"><br></span></font></div><div><font class="Apple-style-span" face="Calibri, sans-serif" size="4"><span class="Apple-style-span" style="font-size: 15px; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469);">-Mike</span></font></div><div><span></span><br><span>On May 18, 2011, at 4:57 AM, Michael Brown <<a href="mailto:mbrown@fensystems.co.uk">mbrown@fensystems.co.uk</a>> wrote:</span><br><span></span><br><blockquote type="cite"><span>On Monday 16 May 2011 17:13:53 Michael Cirineo wrote:</span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>I'm able to get my iPXE client to complete a DHCP request and boot when it</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>is connected directly to my DHCP/boot server. It's only when I put the</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>network between them that the DHCP exchange fails. Wireshark tells me</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>everyone receives everything, but since the client sends out a second</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>DHCPREQUEST before the first DHCPOFFER reaches it, I'm thinking that the</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>DHCPREQUEST is timing out and resending, and invalidating any OFFERs that</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>come based on that first packet. Is that possible? Is there any way to</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>change the timeout time for a DHCPREQUEST?</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I think iPXE should accept a DHCPOFFER that comes even after it times out and </span><br></blockquote><blockquote type="cite"><span>retransmits a DHCPDISCOVER.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>You can use the "ifstat" command (<a href="http://ipxe.org/cmd/ifstat">http://ipxe.org/cmd/ifstat</a>) to see how many </span><br></blockquote><blockquote type="cite"><span>packets iPXE thinks it has received, and what errors (if any) it encountered </span><br></blockquote><blockquote type="cite"><span>in trying to process them.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>You can also use the "seconds elapsed" field in the DHCP packets transmitted by </span><br></blockquote><blockquote type="cite"><span>iPXE to see some metadata regarding the internal state of the DHCP client - </span><br></blockquote><blockquote type="cite"><span>see the DHCP "timed out" error page at <a href="http://ipxe.org/4c106035">http://ipxe.org/4c106035</a> for details.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>You can also build iPXE with DEBUG=dhcp to enable DHCP debugging.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Any of those may help.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Michael</span><br></blockquote></div><div><span></span></div></body></html>