]>
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 | ||
1521b595 TL |
17 | If you want to attempt a port, the first thing to do is to make a copy |
18 | of one of the header files in cf/ for your system and hack the | |
19 | variables you find there as needed. Hack osdep.h to conditionally | |
20 | include your header file when compiling on your system. This process | |
21 | is by no means self-explanatory at this point - it will get better as | |
22 | dhcpd matures. If you are building on BSD/os or NetBSD, just type | |
23 | make - it should build with no problem. | |
24 | ||
471fe68c TL |
25 | Last week (February 26-28), I brought ISC dhcpd to Connectathon and |
26 | worked out many bugs. ISC dhcpd was able to boot all of the DHCP | |
27 | clients at Connectathon by the time I left. Many thanks to Audrey Van | |
28 | Belleghem for getting me in to Connectathon even though we weren't | |
29 | able to budget for it, to Mike Carney for running the DHCP testing in | |
30 | general and helping me out in particular, and to all the other DHCP | |
1521b595 TL |
31 | Bakeoff participants at Connectathon who tried their clients against |
32 | dhcpd and told me where it was busted, or, later on, that it wasn't | |
33 | busted anymore. | |
471fe68c | 34 | |
a8b53b42 TL |
35 | DEBUGGING |
36 | ||
37 | dhcpd logs to LOG_DAEMON. Depending on the logging level that you | |
38 | choose with syslog, you can get quite a bit of information about what | |
39 | dhcpd is doing. To get the most logging, put the following in your | |
40 | /etc/syslog.conf file and restart syslog: | |
41 | ||
42 | daemon.debug: /var/log/daemon.log | |
43 | ||
44 | (obviously, change the filename to suit your taste). | |
45 | ||
46 | This change may have the unfortunate side effect of capturing a lot of | |
47 | information from daemons other than dhcpd that you don't want to look | |
48 | at. | |
49 | ||
50 | You can also compile dhcpd with ``make DEBUG="-g -DDEBUG"''. If you | |
51 | do this, dhcpd will run in the foreground rather than as a daemon, and | |
52 | will print its log messages to standard error. It will also dump the | |
53 | contents of all packets it receives and sends. | |
54 | ||
471fe68c TL |
55 | BUGS |
56 | ||
1521b595 | 57 | Currently, ISC dhcpd supports the DHCP protocol strictly the standard |
471fe68c TL |
58 | Berkeley socket interface to UDP/IP. This makes it very portable, but |
59 | has several drawbacks. First of all, it is impossible to identify the | |
60 | interface on which a DHCP request was received. As a consequence, | |
61 | dhcpd currently exits if it discovers that it's running on a machine | |
62 | with more than one network address. | |
63 | ||
64 | Secondly, it is difficult to send a broadcast to the all-ones IP | |
65 | broadcast address as required by the DHCP protocol. I have had some | |
66 | luck on 4.4BSD-based systems declaring a route to 255.255.255.255 | |
67 | through the local IP address, and have also found that some clients | |
68 | will accept broadcasts from the local subnet broadcast address. I | |
69 | would be interested in hearing about your experiences with this. | |
70 | ||
71 | A socket interface abstraction which can be layered atop sun's NIT or | |
72 | the Berkeley Packet Filter will be included in the next beta release, | |
73 | but probably won't work on as many systems. On those systems where | |
74 | it works, though, it will solve both the multiple interface problem | |
75 | and the all-ones broadcast problem. | |
76 | ||
77 | This release of dhcpd does not contain support for DHCPINFORM. | |
78 | Support for DHCPINFORM will be present in the next release. | |
79 | DHCPINFORM is somewhat tangential to the main purpose of the DHCP | |
80 | protocol, so this probably won't be a major problem for most users. | |
81 | ||
82 | The man page for dhcpd.leases is not yet ready. | |
83 | ||
84 | The system is painful to configure. I will try to get GNU configure | |
85 | going in the next release. | |
86 |