How to boot on fog with bios legacy and uefi on a computer park ???
-
Hello,
For several years I use fog to deploy windows and linux images on my computer and I am currently experiencing a problem.
I use a router mikrotik (router OS) as a DHCP server and I found that by filling in the file: “undionly.kpxe” computers could boot into legacy and informing “ipxe.efi” in uefi.
I would like to boot automatically on one or the other.
But how to do it ?? An idea ??Have a good day
Best regards -
If your dhcp device does not support dynamic boot files then you need to change to a different dhcp server or install dnsmasq on your fog server and remove the boot file information from your current dhcp server. In this configuration dnsmasq (a service running on the fog server) will only supply the pxe boot information to your target computers. I have a tutorial on how to install dnsmasq onto your fog server. The only requirement is that the version of dnsmasq you install has to be version 2.75 or later to use this configuration file. Follow the instructions and use my config file exactly (with the mentioned modifications) and you should be up and running in about 15 minutes. https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server
-
@franck25 said in How to boot on fog with bios legacy and uefi on a computer park ???:
mikrotik
Seems like MikroTik did not have the feature to distinguish between legacy BIOS and UEFI clients for PXE booting for a very long time. I just found a forum post that is telling about a new MicroTik firmware released in Summer 2019 that supports so called vendor class id matching. See here: https://forum.mikrotik.com/viewtopic.php?f=1&t=95674&p=476807&hilit=dhcp+option+pxe#p738671
You need at least RouterOS version 6.45.1 on your MicroTik to be able to test this. Though I have not found any reference on the commands you need to use (“CLI only”).
If you don’t want to mess with this follow George’s advice and use dnsmasq DHCP proxy.
-
On Windows server 2012
-
@ george1421 Thank you very much for your answers.
I test it is I come back to you.
Have a good day
Best regards -
@george1421 Bonjour,
I have a problem with line 38.
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2019-12-05 18:18:29 CET; 4s ago
Process: 13554 ExecStop=/etc/init.d/dnsmasq systemd-stop-resolvconf (code=exited, status=0/SUCCESS)
Process: 13988 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=1/FAILURE)
Process: 13987 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS)
Main PID: 13206 (code=exited, status=0/SUCCESS)déc. 05 18:18:29 11fog1 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server…
déc. 05 18:18:29 11fog1 dnsmasq[13987]: dnsmasq: vérification de syntaxe OK.
déc. 05 18:18:29 11fog1 dnsmasq[13988]: dnsmasq: mauvaise plage d’adresses DHCP (dhcp-range) at line 38 of /etc/dnsmasq.d/ltsp.conf
déc. 05 18:18:29 11fog1 systemd[1]: dnsmasq.service: Control process exited, code=exited status=1
déc. 05 18:18:29 11fog1 dnsmasq[13988]: mauvaise plage d’adresses DHCP (dhcp-range) at line 38 of /etc/dnsmasq.d/ltsp.conf
déc. 05 18:18:29 11fog1 systemd[1]: dnsmasq.service: Failed with result ‘exit-code’.
déc. 05 18:18:29 11fog1 dnsmasq[13988]: IMPOSSIBLE de démarrer
déc. 05 18:18:29 11fog1 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.Here is my line 38:
dhcp-range = <10.20.11.201> Proxy
10.20.11.201 is my FOG server.
If I delete this line dnsmasq works but the computers do not boot.
If you have an idea ??
Best regards
-
@franck25 said in How to boot on fog with bios legacy and uefi on a computer park ???:
dhcp-range = <10.20.11.201> Proxy
Make it
dhcp-range=10.20.11.201,proxy -
@franck25 said in How to boot on fog with bios legacy and uefi on a computer park ???:
dhcp-range = <10.20.11.201> Proxy
If you have an idea ??dhcp-range = <10.20.11.201> Proxyis part of the problem. You need to replace the greater than and less than signs because they are part of the label and should not be in the config file. The correct answer isdhcp-range=10.20.11.201,proxy(also don’t miss the comma after the IP address). Nowhere in your config file should the greater than, less than wrap your IP addresses.Edit: George1421 == to slow… Sebastian for the win!!
-
@george1421
Thank you so much !
It works well !
Have a good day.
