Latitude 5410 No Legacy boot
-
@John-L-Clark Yes there is. First describe what dhcp server are you using (manufacturer and model).
-
@george1421 We are a Meraki network and use the builtin DHCP servers in the Meraki Switches.
-
@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.
-
@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.
-
Great I will test this out and let you know. Thanks again
-
@Sebastian-Roth Will stop all other machines that use Legacy boot from booting to Fog?
-
@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.
-
@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.
-
@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
-
@John-L-Clark What is the OS on the FOG Host server? Most modern Linux OS have the newer version of dnsmasq?
-
@george1421 it is version 16.04
-
@george1421 root@FOG-SRV1:/etc/dnsmasq.d# dnsmasq -v
Dnsmasq version 2.75 Copyright
2000-2015 Simon Kelley
Compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotifyThis software comes with ABSOLUTELY NO WARRANTY.
Dnsmasq is free software, and you are welcome to redistribute it
under the terms of the GNU General Public License, version 2 or 3.
root@FOG-SRV1:/etc/dnsmasq.d# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.2 LTS
Release: 16.04
Codename: xenial -
@John-L-Clark Well I was hoping for a better answer in the 4 years since I wrote this post, but it looks like 16.04 only has 2.75 version of dnsmasq installed. You may need to follow this post to compile an updated version of dnsmasq: https://forums.fogproject.org/topic/8725/compiling-dnsmasq-2-76-if-you-need-uefi-support/11
-
@george1421 I am looking at this and got to the part where i have to edit the config.h and mine does not look the same.
This is what I see.
-
@John-L-Clark In the picture you posted, scroll down abit that section mentioned in the tutorial is there (I just checked). Its about line 173 in the config file.
-
@george1421 Ok thank you I was able to get through the rest of it to the Make install part and this is what I got.
-
@John-L-Clark so did everything on this line get installed correctly?
sudo apt-get install -y wget libdbus-1-dev libnetfilter-conntrack-dev idn libidn11-dev nettle-dev libval-dev dnssec-toolslibidn11-dev should have installed that header file.
If you just can’t get idn to load correctly then go back into the config file and remove these two lines and it should compile.
#define HAVE_DBUS >> #define HAVE_IDN >> #define HAVE_IDN_STATIC #define HAVE_CONNTRACK #define HAVE_DNSSECjust remove the lines completely from the config file.
-
@george1421 Removed the 2 lines and this is what I got. Thank you again for your help.
-
@John-L-Clark again did running this line give no errors?
sudo apt-get install -y wget libdbus-1-dev libnetfilter-conntrack-dev idn libidn11-dev nettle-dev libval-dev dnssec-tools -
@george1421 It fails
