Send dhcp-users mailing list submissions to
dhcp-users@lists.isc.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
dhcp-users-requ...@lists.isc.org
You can reach the person managing the list at
dhcp-users-ow...@lists.isc.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. option 67 boot-file-name FF00 at the end of the data string
(Jan-Philipp Snizek)
2. kea-dhcp4 behaviour question client-class vs reservations
(Jan-Philipp Snizek)
----------------------------------------------------------------------
Message: 1
Date: Fri, 26 Apr 2024 08:51:45 +0000
From: Jan-Philipp Snizek <jan-philipp.sni...@business.uzh.ch>
To: "dhcp-users@lists.isc.org" <dhcp-users@lists.isc.org>
Subject: option 67 boot-file-name FF00 at the end of the data string
Message-ID:
<zrap278mb0756d60d9bc531421ab329ed82...@zrap278mb0756.chep278.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
Hi
In isc-dhcpd I use as option 67 option bootfile-name
"SMSBoot\\x64\\wdsmgfw.efi\000";
This works with any uefi bios, older or new.
How do I do the end of string sequence \000 in kea-dhcp4?
There seem to be older uefi BIOSes that upon receiving the option 67 string,
they attach FF00 at the end of the string and then try to load the efi file.
This ends with the ftfp server returning 'file not found'.
How do I have to do this end-of-file sequence in Kea-dhcp4? Is that even the
correct name for this? I'm not sure, I usually don't play with these lower
level things.
For reference, here's the relevant part of the kea-dhcp4 config file that works
with recent uefi bioses:
"client-classes": [
{
"name": "pxeclientx64",
"test": "option[60].text == 'PXEClient:Arch:00007:UNDI:003016'",
"option-data": [
{ "name": "boot-file-name", "data": "SMSBoot\\x64\\wdsmgfw.efi"
},
{ "name": "tftp-server-name", "code": 66, "data":
"tftp-server.mydomain.local" }
]
}
],
Thanks,
--
Philipp
------------------------------
Message: 2
Date: Fri, 26 Apr 2024 09:05:22 +0000
From: Jan-Philipp Snizek <jan-philipp.sni...@business.uzh.ch>
To: "dhcp-users@lists.isc.org" <dhcp-users@lists.isc.org>
Subject: kea-dhcp4 behaviour question client-class vs reservations
Message-ID:
<zrap278mb075697c005f7099072bf79a282...@zrap278mb0756.chep278.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
Hi
I would like to ask a question regarding precedence behavior of kea-dhcp4.
Let's take this working config:
"client-classes": [
{
"name": "pxeclientx64",
"test": "option[60].text == 'PXEClient:Arch:00007:UNDI:003016'",
"option-data": [
{ "name": "vendor-encapsulated-options", "always-send": false },
{ "name": "boot-file-name", "data": "SMSBoot\\x64\\wdsmgfw.efi"
},
{ "name": "tftp-server-name", "code": 66, "data":
"my-tftp-server.domain.local" }
]
}
],
"subnet4": [
{
"id": 1,
"subnet": "172.20.19.0/24",
"next-server": "172.20.19.1",
"pools": [
{ "pool": "172.20.19.120 - 172.20.19.129" },
{ "pool": "172.20.19.130 - 172.20.19.139",
"client-class": "pxeclientx64" }
],
"reservation-mode": "out-of-pool",
"reservations": [
{ "hostname": "pxeboot1", "hw-address": "00:e0:4c:68:0a:f1",
"ip-address": "172.20.19.150" }
],
"option-data": [
{ "name": "routers", "data": "172.20.19.1" }
]
}
],
If the client with the reservation executes a PXE boot it gets the reserved IP
.19.150 and successfully boots PXE.
The kea-dhcp4 log looks like this:
Apr 25 13:53:17 hellbox kea-dhcp4[16858]: INFO EVAL_RESULT Expression
pxeclientx64 evaluated to 1
Apr 25 13:53:17 hellbox kea-dhcp4[16858]: INFO DHCP4_LEASE_ADVERT [hwtype=1
00:e0:4c:68:0a:c1], cid=[no info], tid=0x2223e0e3: lease 172.20.19.150 will be
advertised
Apr 25 13:53:20 hellbox kea-dhcp4[16858]: INFO EVAL_RESULT Expression
pxeclientx64 evaluated to 1
Apr 25 13:53:20 hellbox kea-dhcp4[16858]: INFO DHCP4_LEASE_ALLOC [hwtype=1
00:e0:4c:68:0a:c1], cid=[no info], tid=0x2223e0e3: lease 172.20.19.150 has been
allocated for 3600 seconds
As we can see both matches: pxeclientx64 and the reservation. The client
successfully boots pxe.
I don't understand why the client successfully pxe boots. The client-class
"pxeclientx64" is assigned to a pool. It is neither assigned to the subnet4 {
id: 1 } subnet declaration nor to the reservation.
What has precedence over what? How does inheritance work in kea?
Thanks,
--
Philipp
------------------------------
Subject: Digest Footer
_______________________________________________
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 184, Issue 1
******************************************
