[Kea-users] problem with INIT_REBOOT

classic Classic list List threaded Threaded
3 messages Options
oc
Reply | Threaded
Open this post in threaded view
|

[Kea-users] problem with INIT_REBOOT

oc
[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
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] problem with INIT_REBOOT

Dave Swager
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 <[hidden email]> 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
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users


--
Dave
m: 408-655-9704

_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users
Reply | Threaded
Open this post in threaded view
|

Re: [Kea-users] problem with INIT_REBOOT

Marcin Siodelski
Supplementing the answer from Dave, I am sending the link to the documentation which clarifies the server's behavior depending on the authoritative flag setting:

https://jenkins.isc.org/job/Kea_doc/guide/kea-guide.html#dhcp4-authoritative

Hope that helps.

Marcin Siodelski
DHCP Software Engineer,
ISC

On 04/05/2019 00:40, Dave Swager wrote:

> 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 <[hidden email]
> <mailto:[hidden email]>> 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
>     [hidden email] <mailto:[hidden email]>
>     https://lists.isc.org/mailman/listinfo/kea-users
>
>
>
> --
> Dave
> m: 408-655-9704
>
> _______________________________________________
> Kea-users mailing list
> [hidden email]
> https://lists.isc.org/mailman/listinfo/kea-users
>


_______________________________________________
Kea-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/kea-users