I believe if you're running kea5 and set authoritative (will send nack to client) that will clear this problem
On Fri, May 3, 2019 at 2:29 PM oc <[email protected]> wrote: > [new user] > > We have multiple KEA servers hosted in our infrastructure (with shared > lease > database). Most recently, we noticed that our DHCP clients failed to renew > their IP address as the KEA servers are rejecting INIT_REBOOT. It appears > to > be an expected behavior for a KEA server to ignore INIT_REBOOT if the lease > was allocated by another KEA server. > > In this particular case, even though all the KEA servers are running (and > are seeing INIT_REBOOT request), none of them respond to INIT_REBOOT > requests. > > What could be causing this problem? No changes to KEA servers > configuration. > > We have another problem in the form of bad DHCP client implementation. > Unfortunately, our DHCP clients are not falling back to 4 way exchange to > get a new lease when they see no response to INIT_REBOOT. > > Is it possible for us to configure one of the other KEA servers to respond > to "INIT_REBOOT" as they all share the same lease database and have > information on the existing lease. > > Thanks > > > > > -- > Sent from: http://kea-users.7364.n8.nabble.com/ > _______________________________________________ > Kea-users mailing list > [email protected] > https://lists.isc.org/mailman/listinfo/kea-users > -- Dave m: 408-655-9704
_______________________________________________ Kea-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/kea-users
