Latitude 5410 No Legacy boot
-
@george1421 it is version 16.04
-
@John-L-Clark What is the OS on the FOG Host server? Most modern Linux OS have the newer version of dnsmasq?
-
@george1421 I just got back to work this week and i have done these steps for the dnsmasq but I can only get version 2.75. I have tried updating the app and still 2.75. Would you have time to work with me on this today? Thanks
-
@george1421 said in Latitude 5410 No Legacy boot:
You can technically leave dhcp option 67 in place since proxydhcp will override any values that come from dhcp/bootp.
While this works with many PXE boot firmwares there are also some that get confused by that and don’t properly boot up. Just saying so you have been warned in case something seems wired.
-
@John-L-Clark said in Latitude 5410 No Legacy boot:
@Sebastian-Roth Will stop all other machines that use Legacy boot from booting to Fog?
You can technically leave dhcp option 67 in place since proxydhcp will override any values that come from dhcp/bootp. You should remove it when you are done testing so you don’t have a random parameter out there that may cause confusion in the future, but for dnsmasq removing this value is not important.
The dnsmasq configuration I provided supports both bios and uefi systems and will dynamically adjust depending on the target computer.
We have found the meraki dhcp server to be lacking in several areas so jumping into dnsmasq is the quickest solution to getting you up and running with FOG.
-
@Sebastian-Roth Will stop all other machines that use Legacy boot from booting to Fog?
-
Great I will test this out and let you know. Thanks again
-
@John-L-Clark Yeah George is right, in this case one quick option is to use dnsmasq to supply the PXE boot information. Make sure you leave your DHCP server on the Meraki enabled but remove the PXE boot information from that (option 66, 67 usually). This will be provided by dnsmasq in so called DHCPProxy mode as an add-on to the Meraki handing out IPs via DHCP. This works quite well in most situations.
-
@John-L-Clark Ok the solution for you too is to install dnsmasq on your fog server and then let dnsmasq provide the pxe boot information (only). I have a tutorial on installing dnsmasq here: https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server
The reason for dnsmasq is to provide dynamic boot information to the target computer based on the target computer’s type.
-
@george1421 We are a Meraki network and use the builtin DHCP servers in the Meraki Switches.
-
@John-L-Clark Yes there is. First describe what dhcp server are you using (manufacturer and model).
-
I had the same issue i followed the steps on this link https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence. Once you have done the steps disable the secure boot on the device itself.
