• they are receiving no DHCP offers received or else get to the deploy image stage and freeze on a black screen with cursor flashing. It appears when the machines that aren’t working are trying to PXE boot they are using Intel Boot Agent Version 1.3.24 however the machines that are working and can deploy the image or get to PXE menu without any issues are using a Intel PXE boot agent?

    These machines are all on same IP range, under same scope with same boot options applied.

  • Developer

    Chad is on the right track I really seem to be slacking lately, normally I am the first one to recommend the DNSMasq, I have to use it here in my novell network because we use Netware 6.5 and it has a limited number of characters that can be supplied for the boot file name. DNSMasq allows me to circumvent the system and provide the correct boot file.

    You can use this guide here [url]http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/url]

    It will aid you in setting up DNSMasq, and of course if you have problems just come back and let us know.

  • Moderator

    DNSMasq is the package. It requires you to change a few pathways in the FOG setup and add an IP helper/relay to your router config if you have FOG clients on different subnets/vlans than your FOG server.

    I have no experience with FOG above 0.32 right now. So I can’t really help but with general knowledge and suggestions.

  • Thanks chad-bisd for the reply.

    How do we add a proxydhcp server on fog?

    Also after the update to fog 1.1.2 which no longer supports pxelinux.0 we are now using undionly.kpxe or ipxe.pxe.


  • Moderator

    I have 2 models of machines (out of about 20 different models) that will not PXE boot if the DHCP server is not the same machine as the PXE server. When we used Windows DHCP and FOG for PXE, these machines would not PXE boot. Research with WireShark showed that they failed to receive blocks 2 through N of the pxelinux.0 file.

    My solution was to implement a ProxyDHCP server on FOG, wherein FOG now listens for DHCP requests as well, and lets Windows DHCP give IP info, but responds to the clients with the PXE boot information. I modified my FOG server slightly and added an additional DHCP relay/DHCP helper to my main switch that handles VLAN traffic routing.

    If any of this sounds like what you need, I’ll be glad to help you as much as I can.

  • Developer

    Look into building a custom kernel, you need to supply your drivers fort the card to work.

  • Already tried a bios update and same issue.

    Network card in the machine is as follows: Intel® 82578DM Gigabit Network Connection

  • Developer

    Look for updated Bios /Firmware for the machines. It would be helpful to know the nic cards in the trouble machines, the kernel actually houses the drivers that the machines use, so if the driver isn’t included, it obviously isn’t going to work.