]>
Commit | Line | Data |
---|---|---|
471fe68c TL |
1 | Internet Software Consortium |
2 | Dynamic Host Configuration Protocol Server | |
3 | Beta Release 0 | |
4 | March 6, 1996 | |
5 | ||
6 | This is the first Beta release of the Internet Software Consortium | |
7 | DHCP Server (ISC dhcpd). In this Beta release, support for the core | |
8 | DHCP protocol is provided. BOOTP support is also provided for | |
9 | backwards compatibility. The beta release currently runs on NetBSD | |
10 | and BSD/OS, and may run on Ultrix. It should port fairly easily to a | |
11 | variety of UNIX-like systems. | |
12 | ||
13 | The default Makefile is a 4.4BSD-style makefile. If you do not have | |
14 | access to a 4.4BSD-style make, use Makefile.std. This is an | |
15 | old-style makefile and should work on most systems. | |
16 | ||
17 | Last week (February 26-28), I brought ISC dhcpd to Connectathon and | |
18 | worked out many bugs. ISC dhcpd was able to boot all of the DHCP | |
19 | clients at Connectathon by the time I left. Many thanks to Audrey Van | |
20 | Belleghem for getting me in to Connectathon even though we weren't | |
21 | able to budget for it, to Mike Carney for running the DHCP testing in | |
22 | general and helping me out in particular, and to all the other DHCP | |
23 | participants at Connectathon who tried their clients against ISC dhcpd | |
24 | and told me where it was busted, or, later on, that it wasn't busted | |
25 | anymore. | |
26 | ||
27 | BUGS | |
28 | ||
29 | Currently, dhcpd supports the DHCP protocol strictly the standard | |
30 | Berkeley socket interface to UDP/IP. This makes it very portable, but | |
31 | has several drawbacks. First of all, it is impossible to identify the | |
32 | interface on which a DHCP request was received. As a consequence, | |
33 | dhcpd currently exits if it discovers that it's running on a machine | |
34 | with more than one network address. | |
35 | ||
36 | Secondly, it is difficult to send a broadcast to the all-ones IP | |
37 | broadcast address as required by the DHCP protocol. I have had some | |
38 | luck on 4.4BSD-based systems declaring a route to 255.255.255.255 | |
39 | through the local IP address, and have also found that some clients | |
40 | will accept broadcasts from the local subnet broadcast address. I | |
41 | would be interested in hearing about your experiences with this. | |
42 | ||
43 | A socket interface abstraction which can be layered atop sun's NIT or | |
44 | the Berkeley Packet Filter will be included in the next beta release, | |
45 | but probably won't work on as many systems. On those systems where | |
46 | it works, though, it will solve both the multiple interface problem | |
47 | and the all-ones broadcast problem. | |
48 | ||
49 | This release of dhcpd does not contain support for DHCPINFORM. | |
50 | Support for DHCPINFORM will be present in the next release. | |
51 | DHCPINFORM is somewhat tangential to the main purpose of the DHCP | |
52 | protocol, so this probably won't be a major problem for most users. | |
53 | ||
54 | The man page for dhcpd.leases is not yet ready. | |
55 | ||
56 | The system is painful to configure. I will try to get GNU configure | |
57 | going in the next release. | |
58 |