UEFI won boot tools via fog menu.

[dureal99d]

@Wayne-Workman said in UEFI won boot tools via fog menu.:

same steps but turn those two settings off

@Wayne-Workman will look into this and report back. promptly!!!

[dureal99d]

@Wayne-Workman yeah after reviewing it all I have been looking for how to add onto “dhcp-boot=undionly.kpxe,fog ip address” and add on the efi boot options. I am stomped on how to do this on dnsmsq of ddwrt.

[Quazz]

@dureal99d

From what I’ve read on the Wiki they need to be added to the additional dnsmasq options manually.

https://wiki.fogproject.org/wiki/index.php/FOG_with_DD-WRT_firmware

[dureal99d]

@Quazz said in UEFI won boot tools via fog menu.:

@dureal99d

From what I’ve read on the Wiki they need to be added to the additional dnsmasq options manually.

https://wiki.fogproject.org/wiki/index.php/FOG_with_DD-WRT_firmware

@Quazz I know they need to be added on manually and i have no issue with that.
but what to add in addition to “dhcp-boot=undionly.kpxe,192.xxx.x.xxx” is what stomps me.

Ive tried several configs all of which seems to make nothing work.

[Quazz]

@dureal99d The dnsmasq on ddwrt may not support the options you need, not sure. I know they use a custom lightweight version of it.

[dureal99d]

@Quazz said in UEFI won boot tools via fog menu.:

sq on ddwrt may not support the options you need, not sure. I know they use a custom lightweight

@Quazz I am willing to try that option but i dont understand the x.x.x.x part outside of the obvious ip parts in the begin.

dhcp-match=set:bios,60,PXEClient:Arch:00000
dhcp-boot=tag:bios,undionly.kpxe,x.x.x.x,x.x.x.x <<clearly IP       # ?.?.?.? = TFTP/FOG server IP

[Quazz]

@dureal99d I found this https://davidmnoriega.wordpress.com/2015/07/27/linksys-e4200-and-dd-wrt/

Which seems to indicate you need to replace tag with #

So eg

dhcp-match=set:bios,60,PXEClient:Arch:00000
dhcp-boot=#:bios,undionly.kpxe,x.x.x.x,x.x.x.x 

Might not be all you need, though.

[Quazz]

@dureal99d The x.x.x.x simply refers to where your TFTP resides. The IP address of your FOG server most likely, unless you set it up elsewhere.

[dureal99d]

@Quazz said in UEFI won boot tools via fog menu.:

@dureal99d The x.x.x.x simply refers to where your TFTP resides. The IP address of your FOG server most likely, unless you set it up elsewhere.

@Quazz so does that mean i should put my tftp ip and where it says fog serve ip put the fog ip?

[Quazz]

@dureal99d Yes

[dureal99d]

@Quazz tried this

dhcp-match=set:bios,60,PXEClient:Arch:00000
dhcp-boot=#:bios,undionly.kpxe,192.168.1.109        # 192.168.1.109 = TFTP/192.168.1.109

did’nt work, im pretty ure its somthing im doing wrong

[Tom Elliott]

The tftp at that point is coming from your fog server .

For me, I use dd-wrt at home as well, and while I don’t have any UEFI machines to test I’m fairly sure you still need to tag the boot file line so it knows which match to use when.

It may be a light version of Dnsmasq, but it is still Dnsmasq.

[george1421]

In my tutorial for installing dnsmasq on Centos this is what I have for the dhcp-boot line:

dhcp-boot=undionly.kpxe,,<fog_server_IP>

Also you need to ensure that you are running dnsmasq 2.76 with has reportedly added the required code for pxe-uefi booting alongside legacy (bios) code.

I have not tried this with dd-wrt either but this extension should work with dnsmasq

dhcp-match=set:efi-x86_64,option:client-arch,7
dhcp-boot=tag:efi-x86_64,ipxe.efi

which sets up a flag if the client matches arch 7 (x86_64 uefi) and then sends ipxe.efi instead of undionly.kpxe. You may need additional arch added for IA32 uefi systems too. Wayne has added the info to the FOG wiki page https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#General
Look at the top for the isc dhcp server to an idea of what is going on.

[Wayne Workman]

@george1421 said in UEFI won boot tools via fog menu.:

Wayne has added the info to the FOG wiki page

@Sebastian-Roth did the dnsmasq section I’m pretty sure lol. Seems he’s always a few steps ahead of us.

[dureal99d]

@george1421 I have plugged in the information to the dnsmasq inclusive to the default dhcp-boot=undionly.kpxe,,<fog_server_IP> & the boot process was not disrupted as with previous configs I’ve tried.

I must now make sure i understand what you did here. dhcp-match=set:efi-x86_64,option:client-arch,7 dhcp-boot=tag:efi-x86_64,ipxe.efi

as it differs from the wiki of the dnsmasq setting. also it when booting uefi it see the tftp as my router ip. What would i do to re-route this to my fogserver ip?

[george1421]

@dureal99d If I understand it correctly your {next-server} value should come from your dhcp server (understand I’m guessing here a bit since I have not worked with uefi and dnsmasq as of now). But in my docs I also ahve this line:

dhcp-range=<fog_server_ip>,proxy

That defines the range.

Actually I still have my FOG-Pi server that I can boot back up. That has dnsmasq running on it. Let me see if I can get a working config.

[george1421]

@dureal99d From your image below its working. Well an iPXE kernel is getting loaded. So that should removed dnsmasq from the issues. Is your fog server at 192.168.1.1?

[dureal99d]

@george1421 NO, its at 192.168.1.109

[george1421]

@dureal99d Interesting because in the picture its thinks your fog server is 192.168.1.1 because that is where its trying to load the default.ipxe file from. I can’t remember off the top of my head where that setting comes from, its either from FOG or the next-server value from dhcp.

[dureal99d]

@george1421 at current my config looks like this

dhcp-match=set:efi-x86_64,option:client-arch,7
dhcp-boot=tag:efi-x86_64,ipxe.efi
dhcp-boot=undionly.kpxe,,192.168.1.109```

in the dnsmasq setting of ddwrt.