Veronique Lefebure <veronique.lefeb...@cern.ch> wrote: > I have observed that an IPV6 client gets the wrong IP when it reboots. > See detailed logs below. > The problem seems to be due to the fact the DUID of the client changes after > reboot.
This sounds like the same problem in the disc-dhcpd & IPv4 world - client boots initially without a Client-ID, then the OS loads and sends a Client-ID; or the device runs 2 OSs, one of which supplies a Client-ID and one doesn’t (or supplies a different one). As a result, the server is required to treat them as different devices. > How to go around that and make sure that the client gets the correct IP > straightaway after reboot ? Configure the client to use the same DUID each time. Veronique Lefebure <veronique.lefeb...@cern.ch> wrote: > The client behaviour is not under control of the DHCP server admins.. No, and it never has been. The job of the server is to receive requests for information from the clients and supply the information requested. While some of the information supplied will influence client behaviour (e.g. lease length), in general the server has no control over clients. > This is a behaviour different from the ISC DHCP server behaviour, right ? As mentioned above, the ISC DHCP server has the same problem in the IPv4 world. Simon -- 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 Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users
