[Kea-users] next-server-address in hooks for UEFI config servers

Gokulakrishnan Gopalakrishnan ggopalakrishnan at salesforce.com
Fri May 25 10:53:13 UTC 2018


Thanks, Francis. If I want to get rid of hardcoding 'next-server' from
kea.conf and move it to the hooks library by setting the field dynamically,
what it the right way?

On Fri, May 25, 2018 at 4:00 PM, Francis Dupont <fdupont at isc.org> wrote:

> Gokulakrishnan Gopalakrishnan writes:
> > I'm trying to assign IPs to my servers using Kea 1.3.0. Some of my
> servers
> > are UEFI configured ones and those are failing in getting IP.
> > When I dig deep, I found out that setting "next-server": "192.168.1.1"
> > manually in kea.conf works fine. I was setting next-server via hooks code
> > (pasted below).
>
> => next-server is a BOOTP/DHCP field, not an option. Note some of these
> fields have a corresponding option used for instance when the field
> is too small (can't happen with an IPv4 address :-).
>
> > // Add next server option to packet.
> > opt = response->getOption(DHO_HOME_AGENT_ADDRS);
>
> => This option gives a list (vs one) of addresses of the Mobile IP
> home agent. So it is something different (but if it makes the client
> happy...).
>
> Regards
>
> Francis Dupont <fdupont at isc.org>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20180525/9f107267/attachment.htm>


More information about the Kea-users mailing list