[Kea-users] (DHCP) FORCERENEW is still not/not yet supported? What about (DHCPv6) RECONF_MSG?

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Kea-users] (DHCP) FORCERENEW is still not/not yet supported? What about (DHCPv6) RECONF_MSG?

Bernd Naumann
Hi *,

I see that DHCPv4 FORCERENEW is still commented in src/lib/dhcp/dhcp4.h

So its not yet supported right? (I also only find really old discussions
about it, that isc-dchp does not want to implement it, and some say
there was/is no request by users, but this is hard to imagine for me...)


Is there any workaround with kea to force clients to refresh their
leases? Or any other way to send FORCERENEW on the subnet? And is it
even supported by dhclient?


Context: I just asked myself if/how to reduce for example the lifetime
of a lease from 1 week to 1 day without waiting, and I assume that's
what is FORCERENEW is about, right? To force clients to contact the
server to get new dhcp options?



And for DHCPv6: RECONF_MSG is set, but is it in use?
Same question, if I update options for a subnet, how do I inform the
clients about it?


Thanks,
Bernd
_______________________________________________
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.

To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.

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