Hi Vladimir,
You are correct, I believe. Kea flex-option hook cannot overwrite
siaddr (next-server) since it isn't a DHCP option. Do you need
next-server for other clients? You can set it to an empty string like
so:
"next-server": "",
at the global or subnet level. See here for further
Thanks Darren.
I'm trying to set up custom next-server and boot-file-name by setting up
options 66 in 67 through the flex option hook, everything based on
relaying router ip.
I can see that KEA server sends both these options properly.
But PXE (VMware) client properly picks the filename
Hi Vladimir,
You should be able to do something like this with the flex option
hook:
https://kea.readthedocs.io/en/kea-2.4.0/arm/hooks.html#libdhcp-flex-option-so-flexible-option-actions-for-option-value-settings
Just need to find out what can be tested for. Is the traffic relayed?
Will there
Let's say I want to send custom next-server and filename to PXE clients,
depending on subnet in which they are located.
In dhcpd, I define a new option, e.g.:
option something-new code 250 = string;
Then I set its value in some of the subnets:
subnet xyz {
option something-new "my-value";
Hi,
I'm not entirely sure what you are asking here. Do you mean that you
need to add a client to a class based on what subnet was selected?
Thank you,
Darren Ankney
On Fri, Oct 13, 2023 at 12:36 PM Vladimir Nikolic via Kea-users
wrote:
>
> Hi,
>
> We are struggling with the migration from
Hi,
We are struggling with the migration from DHCPD to KEA.
Is there any easy alternative to this dhcp-eval feature:
config-option option-name
The config-option operator returns the value for the specified
option that the DHCP client or server has been configured to send.
In DHCPD, we
