Bug #15116
open
Kea not working with UEFI HTTPBoot URL configured
Added by Jason Montleon 11 months ago.
Updated about 1 month ago.
Plus Target Version:
25.01
Description
I have configured and successfully use http boot to occasionally boot libvirt vms by checking off `Enable Network Booting` and entering a URL in the `UEFI HTTPBoot URL` field.
Seeing the banner message that ISC DHCP is deprecated I navigated to `System / Advanced / Networking` and switched to Kea DHCP. But when I do this I am no longer able to successfully use UEFI HTTPBoot.
Switching back and forth between ISC DHCP and Kea DHCP is all I need to do to fix and break the functionality again.
Looking at kea-dhcp4.conf there is nothing that stands out to me as obviously wrong, but clients never access the http server I have configured.
With Wireshark I was able to see that ISC DHCP sets the bootp boot file name and option 60 to HTTPClient. With Kea neither of these things is happening and instead the DHCP option 67 boot file name is being set.
An analogous configuration for Kea that works is like so:
"boot-file-name": "http://server/file",
"option-data": [
{
"name": "vendor-class-identifier",
"data": "HTTPClient"
}
]
Rather than as it is now
"option-data": [
{
"name": "boot-file-name",
"data": "http://server/file"
}
]
- Project changed from pfSense Plus to pfSense
- Category changed from DHCP Client (IPv4) to DHCP (IPv4)
- Target version set to 2.8.0
- Affected Plus Version deleted (
23.09.1)
- Plus Target Version set to 24.03
- Plus Target Version changed from 24.03 to 24.07
If I understand correctly there should be option 93 like
{
"name": "HTTPClient",
"test": "option[93].hex == 0x0010",
"option-data": [ { "name": "vendor-class-identifier", "data":
"HTTPClient" } ],
"boot-file-name": "http://192.168.200.200/boot.efi"
},
- Plus Target Version changed from 24.07 to 24.08
- Plus Target Version changed from 24.08 to 24.11
- Plus Target Version changed from 24.11 to 25.01
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by