Gokulakrishnan Gopalakrishnan writes:
> Currently, I'm hardcoding 'next-server' in kea.conf. Is it possible to do
> it via hook code?
=> yes of course. BTW the way to set the next server address field
(aka siaddr) in BOOTP/DHCP packet is the Pkt4 setSiaddr() method.
Regards
Francis Dupont
Francis,
Currently, I'm hardcoding 'next-server' in kea.conf. Is it possible to do
it via hook code?
On Fri, May 25, 2018 at 4:23 PM, Gokulakrishnan Gopalakrishnan <
ggopalakrish...@salesforce.com> wrote:
> Thanks, Francis. If I want to get rid of hardcoding 'next-server' from
> kea.conf and
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 wrote:
> Gokulakrishnan Gopalakrishnan writes:
> > I'm
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