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
|
Internet Software Consortium
Dynamic Host Configuration Protocol Server
Version 1.0, Patchlevel 2
June 24, 1998
Release Notes
This is version 1.0 Patchlevel 2 of the Internet Software Consortium
DHCP Server The previous version was Version 1.0 Patchlevel 1.
CHANGES FROM VERSION 1.0 BETA 1 PATCHLEVEL 1
- Fix two more potential buffer overflow problems.
- Disable certain warnings on Solaris.
- Include different headers on Linux 1.x and 2.x.
- Fix stupid typo in cons_option call in dhcp.c which caused long dhcp
packets to be sent incorrectly.
- Fix ancient typo in memory.c.
CHANGES FROM VERSION 1.0 BETA 1 PATCHLEVEL 0
- Fix two potential buffer overflow problems.
- Clarify socket API error message on multiple interfaces.
- Fix broken comparison that was setting IP source address to zero.
- Only return 64 bytes of options to BOOTP clients, as specified in
BOOTP protocol.
- Documentation fixes.
CHANGES IN VERSION 1.0
- Minor adjustment to dhcpd.8 documentation.
CHANGES IN VERSION 1.0, BETA 5, PATCHLEVEL 17
- Added a man page for dhcpd.leases.
- Updated README to answer some frequently asked questions.
- Fixed a compile problem on Solaris 2.6.
- Support interface aliases on Solaris.
- Print day and month with leading zero in lease files if less than
ten, for easier parsing by perl/sed/awk scripts.
- Never make the lease database world writable, even if dhcpd is
invoked with a bogus umask.
- Fix DHCPRELEASE handling (before, addressed would never be
released.)
- If there is more than one lease for a particular client on a
particular network, find the lease the client is asking for so as to
avoid a cycle of NAKs.
- If a BOOTP request is received from a particular client and that
client has previously received a DHCP address, make sure that we
still find a valid BOOTP lease so that we don't cycle through
addresses.
- Remove server-identifier option from documentation, other than to
document that it has been deprecated.
- Don't give up if we get an EINTR or EAGAIN while polling or
selecting - these return statuses can occur spuriously without
indicating a fatal problem.
- Do not select for exceptions, since we don't handle them. This was
causing massive CPU consumption on some systems.
- When a DHCP client has been assigned a fixed address but had
previously had a lease, it will request the old leased address. In
such an event, send a DHCPNAK so that it will discover its new
static binding.
|