[Kea-users] Adding pxe with uefi

[Stephen Berg (Code 7309)]

On 2/16/23 10:03, Stephen Berg (Code 7309) via Kea-users wrote:
> On 2/16/23 08:22, Yordanov, Damyan wrote:
>> Hi!
>>
>> […]
>>     "client-classes":
>>     [
>>       { "name": "XClient_iPXE", "test": 
>> "substring(option[77].hex,0,4) == 'iPXE'", "boot-file-name": 
>> "http://192.168.10.4/ipxe/boot.ipxe" },
>>       { "name": "UEFI-32-2",    "test": 
>> "substring(option[60].hex,0,20) == 'PXEClient:Arch:00002'", 
>> "boot-file-name": "ipxe/i386/ipxe.efi",   "next-server": 
>> "192.168.10.4" },
>>       { "name": "UEFI-32-6",    "test": 
>> "substring(option[60].hex,0,20) == 'PXEClient:Arch:00006'", 
>> "boot-file-name": "ipxe/i386/ipxe.efi",   "next-server": 
>> "192.168.10.4" },
>>       { "name": "UEFI-64-7",    "test": 
>> "substring(option[60].hex,0,20) == 'PXEClient:Arch:00007'", 
>> "boot-file-name": "ipxe/x86_64/ipxe.efi", "next-server": 
>> "192.168.10.4" },
>>       { "name": "UEFI-64-8",    "test": 
>> "substring(option[60].hex,0,20) == 'PXEClient:Arch:00008'", 
>> "boot-file-name": "ipxe/x86_64/ipxe.efi", "next-server": 
>> "192.168.10.4" },
>>       { "name": "UEFI-64-9",    "test": 
>> "substring(option[60].hex,0,20) == 'PXEClient:Arch:00009'", 
>> "boot-file-name": "ipxe/x86_64/ipxe.efi", "next-server": 
>> "192.168.10.4" },
>>       { "name": "Legacy",       "test": 
>> "substring(option[60].hex,0,20) == 'PXEClient:Arch:00000'", 
>> "boot-file-name": "ipxe/undionly.kipxe",  "next-server": 
>> "192.168.10.4" }
>>     ],
>> […]
>>
>
> What's the purpose for the three different UEFI-64 entries?  The name 
> and test fields are different but they use the same boot file.
>
> I've added the three classes for 64 bit, I don't have any 32 bit 
> systems so I don't need them.  Changed the reservation for one client 
> I'm testing with so the boot-file-name is set to "ipxe/ipxe-x86_64" 
> since that's the path and filename that I got under /tftpboot/.  
> Select the NIC to boot from and the system gets a dhcp lease, says 
> it's pulling the efi file but then just loops through the dhcp request 
> process again.  I figure I'm missing a step somewhere.
>
> For the old BIOS procedure I built a file with the boot commands named 
> by the client MAC address, is that the same thing that UEFI uses?
>
>
Got a snap shot of what I see onscreen.  This will just keep looping 
through until I reboot it.

-- 
Stephen Berg, IT Specialist, Ocean Sciences Division, Code 7309
Naval Research Laboratory
stephen.berg at nrlssc.navy.mil <- (Preferred contact)
W:   (228) 688-5738
DSN: (312) 823-5738
C:   (228) 365-0162
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dhcp-loop.jpg
Type: image/jpeg
Size: 111873 bytes
Desc: not available
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20230216/4da74eec/attachment-0001.jpg>