boot pxe issue
-
Did you restart the dhcp service after making the change?
-
Yes same issue.
-
Does the OS have tftp server running?
sudo service tftpd-hpa statusDoes the OS have a firewall blocking access potentially?
sudo ufw status -
chris@FOGSRVR:~$ sudo service tftpd-hpa status
[sudo] password for chris:
tftpd-hpa start/running, process 1078
chris@FOGSRVR:~$chris@FOGSRVR:~$ sudo ufw status
Status: inactive
chris@FOGSRVR:~$ -
@Bigredcherokee your boot file is “ipe.pxe”?
-
@Andy-Abplanalp not only that - your dhcpd.conf file has “undionly.kxpe” listed instead of “undionly.kpxe”
-
@Andy-Abplanalp
undionly.kkpxeis the new default, because it works on more systems thanundionly.kpxedoes.@Bigredcherokee the DHCP configuration is suspect to me, the subnet you are serving is defined as 192.168.3.32 255.255.255.224 while the subnet mask you’re handing out to leases is 255.255.255.0
With the actual interface subnet being 192.168.3.32 and mask being 255.255.255.224, your broadcast address would be 192.168.3.63, but you have this defined as a router address.
Also, you would have a maximum of 30 hosts.
Also - the biggest problem is you have no
next-serverdefined in the configuration.Maybe look at this as an example? https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence Also, why not let fog generate the configuration?
-
@Wayne-Workman yes, but also his settings in FOG (that he has pictured) should be pointing to a kernel and the init file. Basically…it appears to have both incorrect configuration settings AND the typo in the dhcpd.conf
-
also @Andy-Abplanalp is right, you do have a typo in the boot file as well, in addition to the other problems pointed out.
It’s undionly.
kpxe, not undionly.kxpe -
@Wayne-Workman said in boot pxe issue:
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence
Thanks Wayne I made the changes.
-
@Andy-Abplanalp thanks for catching that typo.
-
@Andy-Abplanalp Andy yes What should those feild be since I’m using the undionly.kpxe. I gotten pass the first problem now it boots the ipe. I know thats wrong what does it need to be.
Thanks,
Chris -
FOG_TFTP_PXE_KERNEL_DIR —> /var/www/fog/service/ipxe
FOG_TFTP_PXE_KERNEL ----> bzimage
FOG_PXE_BOOT_IMAGE ----> ipe.pxeFOG_TFTP_PXE_KERNEL_32 —> bzimage32
FOG_PXE_BOOT_IMAGE_32 —> init_32.xzWith undionly.kpxe set as the boot file are the above settings correct?
-
@Bigredcherokee the FOG_PXE_BOOT_IMAGE field doesn’t actually do anything at all. It’s more a place holder to remind you what is actually set.
If you have a different problem now, please make a new thread with those details.
-
-
@Andy-Abplanalp I get it mixed up, it’s the one that has a boot rom in it normally. It’s description says its just a place holder.
