Hi, I've not tried this myself, and I expect different behavior compared to DHCPv4, but you might consider adding the old and new subnet to a single shared network. On the old subnet, remove the pools statement so that no dynamic addresses are available. Then, the clients should migrate to the new subnet as they renew since they won't be able to renew the old address any longer. This would work in DHCPv4... In DHCPv6, the move may happen much more quickly (I've seen evidence of this in other testing but haven't investigated closely), it is unclear to me as I've not experimented.
Best to set this up in a lab environment first and see what happens. Thank you, Darren Ankney On Wed, Feb 28, 2024 at 5:13 AM Thijs Blok <blokth...@gmail.com> wrote: > > Hi, > > I cannot really find it in the current manuals, but what is the best practice > to renumber a IPv6 Pool? > We just want to stay the clients online, disable the old pool, and when lease > expires, the client would recieve a new IPv6 address. > > Cheers and thank you for your suggestions up front. > > Br, > Thijs Blok > -- > 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 -- 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
