1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
|
.\" $OpenBSD: dhcpd.leases.5,v 1.5 2005/09/30 20:34:26 jaredy Exp $
.\"
.\" Copyright (c) 1997, 1998 The Internet Software Consortium.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\"
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. Neither the name of The Internet Software Consortium nor the names
.\" of its contributors may be used to endorse or promote products derived
.\" from this software without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE INTERNET SOFTWARE CONSORTIUM AND
.\" CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
.\" INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
.\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
.\" DISCLAIMED. IN NO EVENT SHALL THE INTERNET SOFTWARE CONSORTIUM OR
.\" CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
.\" SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
.\" LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
.\" USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
.\" ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
.\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.\" This software has been written for the Internet Software Consortium
.\" by Ted Lemon <mellon@fugue.com> in cooperation with Vixie
.\" Enterprises. To learn more about the Internet Software Consortium,
.\" see ``http://www.isc.org/isc''. To learn more about Vixie
.\" Enterprises, see ``http://www.vix.com''.
.\"
.Dd January 1, 1997
.Dt DHCPD.LEASES 5
.Os
.Sh NAME
.Nm dhcpd.leases
.Nd DHCP client lease database
.Sh DESCRIPTION
The Internet Software Consortium DHCP Server keeps a persistent
database of leases that it has assigned.
This database is a free-form ASCII file containing a series of
lease declarations.
Every time a lease is acquired, renewed or released, its new value is
recorded at the end of the lease file.
So if more than one declaration appears for a given lease,
the last one in the file is the current one.
.Sh FORMAT
Lease descriptions are stored in a format that is parsed by the same
recursive descent parser used to read the
.Xr dhcpd.conf 5
and
.Xr dhclient.conf 5
files.
Currently, the only declaration that is used in the
.Nm
file is the
.Ic lease
declaration.
.Pp
.Xo
.Ic \ \&lease Ar ip-address No { Ar statements... No }
.Xc
.Pp
Each lease declaration includes the single IP address that has been
leased to the client.
The statements within the braces define the duration of the lease
and to whom it is assigned.
.Pp
The start and end time of a lease are recorded using the ``starts''
and ``ends'' statements:
.Pp
.D1 Ic starts Ar date ;
.D1 Ic ends Ar date ;
.Pp
Dates are specified as follows:
.Pp
.Sm off
.Xo
.Ar \ \&weekday\ \&year No / Ar month
.Pf / Ar day\ \& hour No :
.Ar minute No : Ar second
.Xc
.Sm on
.Pp
The weekday is present to make it easy for a human to tell when a
lease expires \- it's specified as a number from zero to six, with zero
being Sunday.
The day of week is ignored on input.
The year is specified with the century, so it should generally be four digits
except for really long leases.
The month is specified as a number starting with 1 for January.
The day of the month is likewise specified starting with 1.
The hour is a number from 0 to 23, the minute a number from 0 to 59,
and the second also a number from 0 to 59.
.Pp
Lease times are specified in Coordinated Universal Time (UTC), not in the
local time zone.
.Pp
The MAC address of the network interface that was used to acquire the
lease is recorded with the
.Ic hardware
statement:
.Pp
.D1 Ic hardware Ar hardware-type mac-address ;
.Pp
The MAC address is specified as a series of hexadecimal octets,
separated by colons.
.Pp
If the client uses a client identifier to acquire its address, the
client identifier is recorded using the
.Ic uid
statement:
.Pp
.D1 Ic uid Ar client-identifier ;
.Pp
The client identifier is recorded as a series of hexadecimal octets,
regardless of whether the client specifies an ASCII string or uses the
newer hardware type/MAC address format.
.Pp
If the client sends a hostname using the
.Ic Client Hostname
option, as specified in some versions of the DHCP-DNS Interaction draft, that
hostname is recorded using the
.Ic client-hostname
statement.
.Pp
.D1 Ic client-hostname Ar \&"hostname\&" ;
.Pp
If the client sends its hostname using the
.Ic Hostname
option, it is recorded using the
.Ic hostname
statement.
.Pp
.D1 Ic hostname Ar \&"hostname\&" ;
.Pp
The DHCP server may determine that a lease has been misused in some
way, either because a client that has been assigned a lease NAKs it,
or because the server's own attempt to see if an address is in use
prior to reusing it reveals that the address is in fact already in
use.
In that case, the
.Ic abandoned
statement will be used to indicate that the lease should not be reassigned.
.Pp
.D1 Ic abandoned ;
.Pp
Abandoned leases are reclaimed automatically.
When a client asks for a new address, and the server finds that there
are no new addresses, it checks to see if there are any abandoned leases,
and allocates the least recently abandoned lease.
The standard mechanisms for checking for lease address conflicts are still
followed, so if the abandoned lease's IP address is still in use,
it will be reabandoned.
.Pp
If a client
.Em requests
an abandoned address, the server assumes that the reason the address was
abandoned was that the lease file was corrupted, and that the client is
the machine that responded when the lease was probed,
causing it to be abandoned.
In that case, the address is immediately assigned to the client.
.Sh FILES
.Bl -tag -width Ds -compact
.It /var/db/dhcpd.leases
.El
.Sh SEE ALSO
.Xr dhcp-options 5 ,
.Xr dhcpd.conf 5 ,
.Xr dhcpd 8
.Pp
RFC 2132, RFC 2131.
.Sh AUTHORS
.An -nosplit
.Xr dhcpd 8
was written by
.An Ted Lemon Aq mellon@vix.com
under a contract with Vixie Labs.
.Pp
The current implementation was reworked by
.An Henning Brauer Aq henning@openbsd.org .
|
