Send dhcp-users mailing list submissions to
        dhcp-users@lists.isc.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
        dhcp-users-requ...@lists.isc.org

You can reach the person managing the list at
        dhcp-users-ow...@lists.isc.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."


Today's Topics:

   1. Re: Move dhcp lease to new ip+reservation. How? (Gregory Sloop)
   2. Re: Move dhcp lease to new ip+reservation. How? (Simon)
   3. Re: Move dhcp lease to new ip+reservation. How? (Gregory Sloop)


----------------------------------------------------------------------

Message: 1
Date: Fri, 27 Aug 2021 09:35:28 -0700
From: Gregory Sloop <gr...@sloop.net>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Move dhcp lease to new ip+reservation. How?
Message-ID: <129744849.20210827093...@sloop.net>
Content-Type: text/plain; charset="utf-8"

An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/dhcp-users/attachments/20210827/ada49aee/attachment-0001.htm>
-------------- next part --------------
I like this approach best, since it's kind of where I started heading as I 
thought about it.?
(Though Glenn's also has promise. Thanks to you both!)
?
However, I've kind of struggled at knowing exactly what OMAPI commands to use 
to create the skeleton lease (What I've tried doesn't work) and what, exactly, 
to do to "expire" the "old" lease. (There doesn't appear to be any way 
to?remove the lease - it looks like all you can do is expire it. (Though I'm 
not sure if setting the end-time to 0, or something else is the "way" to do it.)

Simon - if you have scripts I could look at, it would be very handy - or at 
least tell me what attributes you set (and to what).
OMAPI and I don't get on very well. (I feel like a bumbling fool any time I try 
to figure out how to do anything in it.)
?
TIA!
?

> Gregory Sloop <gr...@sloop.net> 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

------------------------------

Message: 2
Date: Fri, 27 Aug 2021 17:53:27 +0100
From: Simon <dh...@thehobsons.co.uk>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Move dhcp lease to new ip+reservation. How?
Message-ID: <471e21e4-009e-4eaf-878a-ae6d5632f...@thehobsons.co.uk>
Content-Type: text/plain;       charset=utf-8

Gregory Sloop <gr...@sloop.net> wrote:

> However, I've kind of struggled at knowing exactly what OMAPI commands to use 
> to create the skeleton lease (What I've tried doesn't work) and what, 
> exactly, to do to "expire" the "old" lease. (There doesn't appear to be any 
> way to remove the lease - it looks like all you can do is expire it. (Though 
> I'm not sure if setting the end-time to 0, or something else is the "way" to 
> do it.)
> 
> Simon - if you have scripts I could look at, it would be very handy - or at 
> least tell me what attributes you set (and to what).
> OMAPI and I don't get on very well. (I feel like a bumbling fool any time I 
> try to figure out how to do anything in it.)

I just stop the server and edit the leases file - I only run a home server 
these days. I never did run anything ?big enough? that I needed to do online 
maintenance and never used OMAPI.

All you need to create for a skeleton lease is (from memory) :

lease {
  hardware 1:xx......;
  address 192.168....;
  reserved;
}

The server will fill in the rest as it goes.

Simon



------------------------------

Message: 3
Date: Fri, 27 Aug 2021 10:06:37 -0700
From: Gregory Sloop <gr...@sloop.net>
To: Users of ISC DHCP <dhcp-users@lists.isc.org>
Subject: Re: Move dhcp lease to new ip+reservation. How?
Message-ID: <335243988.20210827100...@sloop.net>
Content-Type: text/plain; charset="utf-8"

An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/dhcp-users/attachments/20210827/b01d7741/attachment-0001.htm>
-------------- next part --------------
?


> Gregory Sloop <gr...@sloop.net> wrote:

>> However, I've kind of struggled at knowing exactly what OMAPI commands to 
>> use to create the skeleton lease (What I've tried doesn't work) and what, 
>> exactly, to do to "expire" the "old" lease. (There doesn't appear to be any 
>> way to remove the lease - it looks like all you can do is expire it. (Though 
>> I'm not sure if setting the end-time to 0, or something else is the "way" to 
>> do it.)

>> Simon - if you have scripts I could look at, it would be very handy - or at 
>> least tell me what attributes you set (and to what).
>> OMAPI and I don't get on very well. (I feel like a bumbling fool any time I 
>> try to figure out how to do anything in it.)

> I just stop the server and edit the leases file - I only run a home server 
> these days. I never did run anything ?big enough? that I needed to do online 
> maintenance and never used OMAPI.

> All you need to create for a skeleton lease is (from memory) :

> lease {
> ? hardware 1:xx......;
> ? address 192.168....;
> ? reserved;
> }

Ah. Bummer. In this case, we've got perhaps 400+ devices on the network getting 
leases and using fail-over.
?
Stopping and editing the leases file isn't much of an option - especially since 
operating hours are pretty wide. (Doing it occasionally would work, but I'd 
like a way I can do this maintence during a regular operating day, instead of 
4a in the morning.)
?
I guess I'll just setup a VM here and test against a test server and poke/prod 
until I think I've got it figure out. I've been playing with the production 
server, which is a little scary.
?
Can anyone confirm that you _can_ create a new empty lease (like above) with 
OMAPI?
(I should have kept better track of my searches on the topic. I know I've seen 
people claiming they've successfully expired a lease, but I'm not sure I've 
seen any where they are creating new leases.)
?
Thanks again!
?
-Greg

------------------------------

Subject: Digest Footer

_______________________________________________
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
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users


------------------------------

End of dhcp-users Digest, Vol 154, Issue 9
******************************************

Reply via email to