Re: Move dhcp lease to new ip+reservation. How?

Simon <[email protected]>
Newsgroups gmane.network.dhcp.isc.dhcp-client
Message-ID <7C3CC58F-42B7-4F81-8405-14E7007F2163__35998.4806784027$1630057018$gmane$org@thehobsons.co.uk>
Gregory Sloop <[email protected]> wrote:

> I've thought about pre-creating leases for 51-70 and essentially adding "bogus" information for those leases and reserving them. (While allowing unknown-clients for the 51-70 pool - but since they're all "taken" it won't hand one out),  Then when I want to move something there, I can remove the "bogus" reservation and move the "real" lease to the appropriate IP in the 51-70 block/pool.

That’s what I’ve done for a small pool I’ve created at home for some devices - I wanted to segregate (isolate) some IoT stuff that others insist on having in the house.
When you move the device, as well as assigning it to the reserved lease (which as you’ve probably realised, only initially needs to be a skeleton entry with MAC, IP, and the reserved flag), you need to remove it’s other lease(s) to ensure that it changes address.

I don’t run failover, so I don’t know what you’ll need to do in terms of making the two servers agree on the details - e.g. whether it’s enough to do it on one with OMAPI and it’ll get copied by the failover setup, or whether you have to do it to both servers separately.

Simon

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

dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.