reserved leases

[Ray Phillips]

Thanks for your reply David.

>  > As I understand it this wouldn't work with failover since pools need
>>  to have at least two IP numbers so each peer can be responsible to
>>  half the pool?
>
>I'm not aware of any such restriction, per se.  It certainly would not
>work well, however, since only one server would have the ability to
>answer.  You'd have to assume your servers always operate in normal
>state.
>
>It might be easier to use host records, which are 'failover compatible'
>(in that both servers will happily answer).

Yes, it would be easier.  I just like the DNS records to be updated 
automatically.

>  > Is it possible to use 3.1.0's reserved lease feature to replace this
>>  scheme?
>
>I'm not sure.  Do you allocate multiple clients to a pool of one address,
>or is it a 1:1 ratio on clients to addresses?
>
>Reserved leases will only work in the 1:1 case.

OK, there's only one client per one-number pool.

>  > The man page seems to say a client can only have a reserved
>>  lease if it requests an infinite lease, or if it OMAPI is used to
>>  configure it.
>
>You can also edit dhcpd.leases.  Just mark a lease "reserved;".
>
>  > Can a lease only be reserved once it's been allocated,
>>  in which case it's not possible to specify in advance which IP number
>>  a client with a reserved lease will get?
>
>No, but you have to know how the client is going to identify itself
>beforehand.  Client identifier or hardware address, and the contents
>of those fields.

How would you use the client identifier, for example, to make a 
device lease the number you want it to?  Is it a matter of inserting 
a lease with that client-id and IP number into dhcpd.leases manually?

By the way, in case it matters, when I tried using 3.1.0a1 briefly on 
a machine running NetBSD/i386 3.0 "non-null pointer" appeared in 
/var/log/dhcpd a couple of times:

Sep 21 00:56:22 ns dhcpd: Internet Systems Consortium DHCP Server V3.1.0a1
Sep 21 00:56:22 ns dhcpd: Copyright 2004-2006 Internet Systems Consortium.
Sep 21 00:56:22 ns dhcpd: All rights reserved.
Sep 21 00:56:22 ns dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Sep 21 00:56:22 ns dhcpd: Internet Systems Consortium DHCP Server V3.1.0a1
Sep 21 00:56:22 ns dhcpd: Copyright 2004-2006 Internet Systems Consortium.
Sep 21 00:56:22 ns dhcpd: All rights reserved.
Sep 21 00:56:22 ns dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
Sep 21 00:56:22 ns dhcpd: Wrote 0 class decls to leases file.
Sep 21 00:56:22 ns dhcpd: Wrote 0 deleted host decls to leases file.
Sep 21 00:56:22 ns dhcpd: Wrote 0 new dynamic host decls to leases file.
Sep 21 00:56:22 ns dhcpd: Wrote 4 leases to leases file.
Sep 21 00:56:22 ns dhcpd: Listening on BPF/ex0/00:04:75:98:01:04/192.168.0/24
Sep 21 00:56:22 ns dhcpd: Sending on   BPF/ex0/00:04:75:98:01:04/192.168.0/24
Sep 21 00:56:22 ns dhcpd: Sending on   Socket/fallback/fallback-net
Sep 21 01:03:11 ns dhcpd: dhcp.c(3928): non-null pointer
Sep 21 01:03:11 ns dhcpd: DHCPDISCOVER from 00:a0:d1:34:d7:33 via ex0
Sep 21 01:03:12 ns dhcpd: DHCPOFFER on 192.168.0.220 to 
00:a0:d1:34:d7:33 (june) via ex0
Sep 21 01:06:16 ns dhcpd: dhcp.c(3928): non-null pointer
Sep 21 01:06:16 ns dhcpd: DHCPDISCOVER from 00:a0:d1:34:d7:33 (june) via ex0
Sep 21 01:06:17 ns dhcpd: DHCPOFFER on 192.168.0.220 to 
00:a0:d1:34:d7:33 (june) via ex0
Sep 21 01:06:17 ns dhcpd: 00:a0:d1:34:d7:33 believed to be Microsoft 
Windows XP - MSFT 5.0
Sep 21 01:06:17 ns dhcpd: dhcp.c(3928): non-null pointer
Sep 21 01:06:17 ns dhcpd: DHCPREQUEST for 192.168.0.220 
(192.168.0.60) from 00:a0:d1:34:d7:33 (june) via ex0
Sep 21 01:06:17 ns dhcpd: DHCPACK on 192.168.0.220 to 
00:a0:d1:34:d7:33 (june) via ex0

Ray