]>
Commit | Line | Data |
---|---|---|
91da194e | 1 | Internet Systems Consortium DHCP Distribution |
82e0ea57 TM |
2 | Version 4.4.2b1 |
3 | 12 December 2019 | |
4650dc25 | 4 | |
98311e4b | 5 | README FILE |
4650dc25 TL |
6 | |
7 | You should read this file carefully before trying to install or use | |
8 | the ISC DHCP Distribution. | |
9 | ||
10 | TABLE OF CONTENTS | |
11 | ||
12 | 1 WHERE TO FIND DOCUMENTATION | |
13 | 2 RELEASE STATUS | |
14 | 3 BUILDING THE DHCP DISTRIBUTION | |
986bf898 TL |
15 | 3.1 UNPACKING IT |
16 | 3.2 CONFIGURING IT | |
17 | 3.2.1 DYNAMIC DNS UPDATES | |
38793a26 | 18 | 3.2.2 LOCALLY DEFINED OPTIONS |
986bf898 | 19 | 3.3 BUILDING IT |
4650dc25 TL |
20 | 4 INSTALLING THE DHCP DISTRIBUTION |
21 | 5 USING THE DHCP DISTRIBUTION | |
da411127 TL |
22 | 5.1 FIREWALL RULES |
23 | 5.2 LINUX | |
24 | 5.2.1 IF_TR.H NOT FOUND | |
25 | 5.2.2 SO_ATTACH_FILTER UNDECLARED | |
26 | 5.2.3 PROTOCOL NOT CONFIGURED | |
27 | 5.2.4 BROADCAST | |
28 | 5.2.6 IP BOOTP AGENT | |
29 | 5.2.7 MULTIPLE INTERFACES | |
30 | 5.3 SCO | |
31 | 5.4 HP-UX | |
32 | 5.5 ULTRIX | |
33 | 5.6 FreeBSD | |
34 | 5.7 NeXTSTEP | |
35 | 5.8 SOLARIS | |
7cfeb916 | 36 | 5.8.1 Solaris 11 |
b89b8e16 SR |
37 | 5.8.2 Solaris 11 and ATF |
38 | 5.8.3 Other Solaris Items | |
236d3a99 DH |
39 | 5.9 AIX |
40 | 5.10 MacOS X | |
6913a589 | 41 | 5.11 ATF |
4650dc25 | 42 | 6 SUPPORT |
986bf898 | 43 | 6.1 HOW TO REPORT BUGS |
fef8c6f0 | 44 | 7 HISTORY |
4650dc25 TL |
45 | |
46 | WHERE TO FIND DOCUMENTATION | |
2d1b06e0 TL |
47 | |
48 | Documentation for this software includes this README file, the | |
49 | RELNOTES file, and the manual pages, which are in the server, common, | |
da411127 TL |
50 | client and relay subdirectories. The README file (this file) includes |
51 | late-breaking operational and system-specific information that you | |
52 | should read even if you don't want to read the manual pages, and that | |
53 | you should *certainly* read if you run into trouble. Internet | |
802fdea1 TM |
54 | standards relating to the DHCP protocol are listed in the References |
55 | document that is available in html, txt and xml formats in doc/ | |
da411127 TL |
56 | subdirectory. You will have the best luck reading the manual pages if |
57 | you build this software and then install it, although you can read | |
58 | them directly out of the distribution if you need to. | |
2d1b06e0 TL |
59 | |
60 | DHCP server documentation is in the dhcpd man page. Information about | |
61 | the DHCP server lease database is in the dhcpd.leases man page. | |
62 | Server configuration documentation is in the dhcpd.conf man page as | |
63 | well as the dhcp-options man page. A sample DHCP server | |
9ff4e0a2 SR |
64 | configuration is in the file server/dhcpd.conf.example. The source for |
65 | the dhcpd, dhcpd.leases and dhcpd.conf man pages is in the server/ sub- | |
4650dc25 TL |
66 | directory in the distribution. The source for the dhcp-options.5 |
67 | man page is in the common/ subdirectory. | |
2d1b06e0 TL |
68 | |
69 | DHCP Client documentation is in the dhclient man page. DHCP client | |
70 | configuration documentation is in the dhclient.conf man page and the | |
71 | dhcp-options man page. The DHCP client configuration script is | |
72 | documented in the dhclient-script man page. The format of the DHCP | |
73 | client lease database is documented in the dhclient.leases man page. | |
4650dc25 TL |
74 | The source for all these man pages is in the client/ subdirectory in |
75 | the distribution. In addition, the dhcp-options man page should be | |
76 | referred to for information about DHCP options. | |
2d1b06e0 | 77 | |
4650dc25 TL |
78 | DHCP relay agent documentation is in the dhcrelay man page, the source |
79 | for which is distributed in the relay/ subdirectory. | |
2d1b06e0 | 80 | |
2ca63671 TM |
81 | KEA Migration Assistant documentation, including how to build, install |
82 | and use it, is including in the keama directory. | |
83 | ||
2d1b06e0 | 84 | To read installed manual pages, use the man command. Type "man page" |
4650dc25 TL |
85 | where page is the name of the manual page. This will only work if |
86 | you have installed the ISC DHCP distribution using the ``make install'' | |
87 | command (described later). | |
2d1b06e0 TL |
88 | |
89 | If you want to read manual pages that aren't installed, you can type | |
90 | ``nroff -man page |more'' where page is the filename of the | |
91 | unformatted manual page. The filename of an unformatted manual page | |
92 | is the name of the manual page, followed by '.', followed by some | |
93 | number - 5 for documentation about files, and 8 for documentation | |
4650dc25 TL |
94 | about programs. For example, to read the dhcp-options man page, |
95 | you would type ``nroff -man common/dhcp-options.5 |more'', assuming | |
96 | your current working directory is the top level directory of the ISC | |
97 | DHCP Distribution. | |
2d1b06e0 | 98 | |
e021c50c DH |
99 | Please note that the pathnames of files to which our manpages refer |
100 | will not be correct for your operating system until after you iterate | |
101 | 'make install' (so if you're reading a manpage out of the source | |
102 | directory, it may not have up-to-date information). | |
2d1b06e0 | 103 | |
26833160 TL |
104 | BUILDING THE DHCP DISTRIBUTION |
105 | ||
986bf898 TL |
106 | UNPACKING IT |
107 | ||
1409f290 TL |
108 | To build the DHCP Distribution, unpack the compressed tar file using |
109 | the tar utility and the gzip command - type something like: | |
110 | ||
82e0ea57 TM |
111 | gunzip dhcp-4.4.2b1.tar.gz |
112 | tar xvf dhcp-4.4.2b1.tar | |
98bf1607 | 113 | |
986bf898 TL |
114 | CONFIGURING IT |
115 | ||
82e0ea57 | 116 | Now, cd to the dhcp-4.4.2b1 subdirectory that you've just created and |
6b911c86 | 117 | configure the source tree by typing: |
1409f290 | 118 | |
98311e4b | 119 | ./configure |
1409f290 TL |
120 | |
121 | If the configure utility can figure out what sort of system you're | |
122 | running on, it will create a custom Makefile for you for that | |
123 | system; otherwise, it will complain. If it can't figure out what | |
124 | system you are using, that system is not supported - you are on | |
125 | your own. | |
126 | ||
dbd65517 SR |
127 | Several options may be enabled or disabled via the configure command. |
128 | You can get a list of these by typing: | |
129 | ||
130 | ./configure --help | |
131 | ||
007ba82a FD |
132 | If you want to use dynamic shared libraries automake, autoconf |
133 | (aka GNU autotools) and libtool must be available. The DHCP | |
134 | distribution provides 3 configure.ac* files: the -lt version | |
135 | has no libtool support and was copied to the configure.ac | |
136 | standard file in the distribution. To enable libtool support | |
137 | you should perform these steps: | |
138 | ||
139 | cp configure.ac+lt configure.ac | |
140 | autoreconf -i | |
141 | ||
142 | after you can use the regenerated configure as usual | |
143 | (with libtool support (--enable-libtool) on by default): | |
144 | ||
145 | ./configure | |
146 | ||
147 | For compatibility (and people who don't read this documentation) | |
148 | the --enable-libtool configuration file is supported even by | |
149 | the distributed configure (and off by default). The previous | |
150 | steps are performed and the regenerated configure called with | |
151 | almost the same parameters (this "almost" makes the use of | |
152 | this feature not recommended). | |
153 | ||
838cc5ea FD |
154 | Note you can't go back from with libtool support to without libtool |
155 | support by restoring configure.ac and rerun autoreconf. If you | |
156 | want or need to restore the without libtool support state the | |
157 | required way is to simply restore the whole distribution. | |
158 | ||
986bf898 TL |
159 | DYNAMIC DNS UPDATES |
160 | ||
da411127 | 161 | A fully-featured implementation of dynamic DNS updates is included in |
98bf1607 | 162 | this release. It uses libraries from BIND and, to avoid issues with |
95bba8b6 SR |
163 | different versions, includes the necessary BIND version. The appropriate |
164 | BIND libraries will be compiled and installed in the bind subdirectory | |
165 | as part of the make step. In order to build the necessary libraries you | |
166 | will need to have "gmake" available on your build system. | |
167 | ||
986bf898 | 168 | |
6b3d9544 TL |
169 | There is documentation for the DDNS support in the dhcpd.conf manual |
170 | page - see the beginning of this document for information on finding | |
171 | manual pages. | |
986bf898 | 172 | |
38793a26 TL |
173 | LOCALLY DEFINED OPTIONS |
174 | ||
175 | In previous versions of the DHCP server there was a mechanism whereby | |
176 | options that were not known by the server could be configured using | |
177 | a name made up of the option code number and an identifier: | |
178 | "option-nnn" This is no longer supported, because it is not future- | |
179 | proof. Instead, if you want to use an option that the server doesn't | |
180 | know about, you must explicitly define it using the method described | |
181 | in the dhcp-options man page under the DEFINING NEW OPTIONS heading. | |
182 | ||
986bf898 TL |
183 | BUILDING IT |
184 | ||
1409f290 TL |
185 | Once you've run configure, just type ``make'', and after a while |
186 | you should have a dhcp server. If you get compile errors on one | |
187 | of the supported systems mentioned earlier, please let us know. | |
188 | If you get warnings, it's not likely to be a problem - the DHCP | |
189 | server compiles completely warning-free on as many architectures | |
190 | as we can manage, but there are a few for which this is difficult. | |
191 | If you get errors on a system not mentioned above, you will need | |
192 | to do some programming or debugging on your own to get the DHCP | |
193 | Distribution working. | |
26833160 | 194 | |
b4a10c76 FD |
195 | If you cross compile you have to follow the instructions from |
196 | the BIND README, in particular you must set the BUILD_CC | |
197 | environment variable. | |
198 | ||
4650dc25 TL |
199 | INSTALLING THE DHCP DISTRIBUTION |
200 | ||
68c039d3 TL |
201 | Once you have successfully gotten the DHCP Distribution to build, you |
202 | can install it by typing ``make install''. If you already have an old | |
203 | version of the DHCP Distribution installed, you may want to save it | |
204 | before typing ``make install''. | |
3dcbf508 | 205 | |
4650dc25 TL |
206 | USING THE DHCP DISTRIBUTION |
207 | ||
da411127 TL |
208 | FIREWALL RULES |
209 | ||
210 | If you are running the DHCP server or client on a computer that's also | |
211 | acting as a firewall, you must be sure to allow DHCP packets through | |
212 | the firewall. In particular, your firewall rules _must_ allow packets | |
213 | from IP address 0.0.0.0 to IP address 255.255.255.255 from UDP port 68 | |
214 | to UDP port 67 through. They must also allow packets from your local | |
215 | firewall's IP address and UDP port 67 through to any address your DHCP | |
216 | server might serve on UDP port 68. Finally, packets from relay agents | |
217 | on port 67 to the DHCP server on port 67, and vice versa, must be | |
218 | permitted. | |
219 | ||
220 | We have noticed that on some systems where we are using a packet | |
221 | filter, if you set up a firewall that blocks UDP port 67 and 68 | |
222 | entirely, packets sent through the packet filter will not be blocked. | |
223 | However, unicast packets will be blocked. This can result in strange | |
224 | behaviour, particularly on DHCP clients, where the initial packet | |
225 | exchange is broadcast, but renewals are unicast - the client will | |
226 | appear to be unable to renew until it starts broadcasting its | |
227 | renewals, and then suddenly it'll work. The fix is to fix the | |
228 | firewall rules as described above. | |
229 | ||
230 | PARTIAL SERVERS | |
231 | ||
232 | If you have a server that is connected to two networks, and you only | |
233 | want to provide DHCP service on one of those networks (e.g., you are | |
234 | using a cable modem and have set up a NAT router), if you don't write | |
235 | any subnet declaration for the network you aren't supporting, the DHCP | |
236 | server will ignore input on that network interface if it can. If it | |
237 | can't, it will refuse to run - some operating systems do not have the | |
238 | capability of supporting DHCP on machines with more than one | |
239 | interface, and ironically this is the case even if you don't want to | |
240 | provide DHCP service on one of those interfaces. | |
241 | ||
26833160 TL |
242 | LINUX |
243 | ||
6da19769 TL |
244 | There are three big LINUX issues: the all-ones broadcast address, |
245 | Linux 2.1 ip_bootp_agent enabling, and operations with more than one | |
3dcbf508 TL |
246 | network interface. There are also two potential compilation/runtime |
247 | problems for Linux 2.1/2.2: the "SO_ATTACH_FILTER undeclared" problem | |
248 | and the "protocol not configured" problem. | |
249 | ||
3dcbf508 TL |
250 | LINUX: PROTOCOL NOT CONFIGURED |
251 | ||
e021c50c | 252 | If you get the following message, it's because your kernel doesn't |
713a2956 | 253 | have the Linux packetfilter or raw packet socket configured: |
3dcbf508 | 254 | |
c87fcde1 TL |
255 | Make sure CONFIG_PACKET (Packet socket) and CONFIG_FILTER (Socket |
256 | Filtering) are enabled in your kernel configuration | |
257 | ||
258 | If this happens, you need to configure your Linux kernel to support | |
e021c50c DH |
259 | Socket Filtering and the Packet socket, or to select a kernel provided |
260 | by your Linux distribution that has these enabled (virtually all modern | |
261 | ones do by default). | |
2a1ebeee | 262 | |
3dcbf508 | 263 | LINUX: BROADCAST |
2a1ebeee | 264 | |
da411127 TL |
265 | If you are running a recent version of Linux, this won't be a problem, |
266 | but on older versions of Linux (kernel versions prior to 2.2), there | |
267 | is a potential problem with the broadcast address being sent | |
268 | incorrectly. | |
269 | ||
26833160 TL |
270 | In order for dhcpd to work correctly with picky DHCP clients (e.g., |
271 | Windows 95), it must be able to send packets with an IP destination | |
4650dc25 TL |
272 | address of 255.255.255.255. Unfortunately, Linux changes an IP |
273 | destination of 255.255.255.255 into the local subnet broadcast address | |
da411127 TL |
274 | (here, that's 192.5.5.223). |
275 | ||
276 | This isn't generally a problem on Linux 2.2 and later kernels, since | |
277 | we completely bypass the Linux IP stack, but on old versions of Linux | |
278 | 2.1 and all versions of Linux prior to 2.1, it is a problem - pickier | |
279 | DHCP clients connected to the same network as the ISC DHCP server or | |
280 | ISC relay agent will not see messages from the DHCP server. It *is* | |
281 | possible to run into trouble with this on Linux 2.2 and later if you | |
80778e94 | 282 | are running a version of the DHCP server that was compiled on a Linux |
da411127 | 283 | 2.0 system, though. |
7751e60d | 284 | |
26833160 TL |
285 | It is possible to work around this problem on some versions of Linux |
286 | by creating a host route from your network interface address to | |
287 | 255.255.255.255. The command you need to use to do this on Linux | |
288 | varies from version to version. The easiest version is: | |
7751e60d | 289 | |
26833160 | 290 | route add -host 255.255.255.255 dev eth0 |
7751e60d | 291 | |
26833160 TL |
292 | On some older Linux systems, you will get an error if you try to do |
293 | this. On those systems, try adding the following entry to your | |
294 | /etc/hosts file: | |
7751e60d | 295 | |
26833160 | 296 | 255.255.255.255 all-ones |
7751e60d | 297 | |
26833160 | 298 | Then, try: |
7751e60d | 299 | |
26833160 | 300 | route add -host all-ones dev eth0 |
7751e60d | 301 | |
26833160 | 302 | Another route that has worked for some users is: |
7751e60d | 303 | |
26833160 | 304 | route add -net 255.255.255.0 dev eth0 |
471fe68c | 305 | |
26833160 TL |
306 | If you are not using eth0 as your network interface, you should |
307 | specify the network interface you *are* using in your route command. | |
a8b53b42 | 308 | |
3dcbf508 | 309 | LINUX: IP BOOTP AGENT |
6da19769 TL |
310 | |
311 | Some versions of the Linux 2.1 kernel apparently prevent dhcpd from | |
312 | working unless you enable it by doing the following: | |
313 | ||
314 | echo 1 >/proc/sys/net/ipv4/ip_bootp_agent | |
315 | ||
316 | ||
3dcbf508 | 317 | LINUX: MULTIPLE INTERFACES |
2a1ebeee | 318 | |
4650dc25 TL |
319 | Very old versions of the Linux kernel do not provide a networking API |
320 | that allows dhcpd to operate correctly if the system has more than one | |
321 | broadcast network interface. However, Linux 2.0 kernels with version | |
322 | numbers greater than or equal to 2.0.31 add an API feature: the | |
323 | SO_BINDTODEVICE socket option. If SO_BINDTODEVICE is present, it is | |
324 | possible for dhcpd to operate on Linux with more than one network | |
cd977bed | 325 | interface. In order to take advantage of this, you must be running a |
3dcbf508 TL |
326 | 2.0.31 or greater kernel, and you must have 2.0.31 or later system |
327 | headers installed *before* you build the DHCP Distribution. | |
2a1ebeee | 328 | |
cd977bed TL |
329 | We have heard reports that you must still add routes to 255.255.255.255 |
330 | in order for the all-ones broadcast to work, even on 2.0.31 kernels. | |
331 | In fact, you now need to add a route for each interface. Hopefully | |
332 | the Linux kernel gurus will get this straight eventually. | |
333 | ||
4650dc25 TL |
334 | Linux 2.1 and later kernels do not use SO_BINDTODEVICE or require the |
335 | broadcast address hack, but do support multiple interfaces, using the | |
336 | Linux Packet Filter. | |
337 | ||
09c6b1cf PS |
338 | LINUX: OpenWrt |
339 | ||
113e193f PS |
340 | DHCP 4.1 has been tested on OpenWrt 7.09 and 8.09. In keeping with |
341 | standard practice, client/scripts now includes a dhclient-script file | |
342 | for OpenWrt. However, this is not sufficient by itself to run dhcp on | |
343 | OpenWrt; a full OpenWrt package for DHCP is available at | |
344 | ftp://ftp.isc.org/isc/dhcp/dhcp-4.1.0-openwrt.tar.gz | |
09c6b1cf | 345 | |
88cd8aca DH |
346 | LINUX: 802.1q VLAN INTERFACES |
347 | ||
348 | If you're using 802.1q vlan interfaces on Linux, it is necessary to | |
349 | vconfig the subinterface(s) to rewrite the 802.1q information out of | |
350 | packets received by the dhcpd daemon via LPF: | |
351 | ||
352 | vconfig set_flag eth1.523 1 1 | |
353 | ||
354 | Note that this may affect the performance of your system, since the | |
355 | Linux kernel must rewrite packets received via this interface. For | |
356 | more information, consult the vconfig man pages. | |
357 | ||
26833160 | 358 | SCO |
a8b53b42 | 359 | |
41e45067 DH |
360 | ISC DHCP will now work correctly on newer versions of SCO out of the |
361 | box (tested on OpenServer 5.05b, assumed to work on UnixWare 7). | |
a8b53b42 | 362 | |
45d545f0 | 363 | Older versions of SCO have the same problem as Linux (described earlier). |
41e45067 DH |
364 | The thing is, SCO *really* doesn't want to let you add a host route to |
365 | the all-ones broadcast address. | |
366 | ||
367 | You can try the following: | |
fcebfc39 TL |
368 | |
369 | ifconfig net0 xxx.xxx.xxx.xxx netmask 0xNNNNNNNN broadcast 255.255.255.255 | |
370 | ||
371 | If this doesn't work, you can also try the following strange hack: | |
372 | ||
373 | ifconfig net0 alias 10.1.1.1 netmask 8.0.0.0 | |
a8b53b42 | 374 | |
26833160 TL |
375 | Apparently this works because of an interaction between SCO's support |
376 | for network classes and the weird netmask. The 10.* network is just a | |
377 | dummy that can generally be assumed to be safe. Don't ask why this | |
41e45067 | 378 | works. Just try it. If it works for you, great. |
a8b53b42 | 379 | |
26833160 TL |
380 | HP-UX |
381 | ||
382 | HP-UX has the same problem with the all-ones broadcast address that | |
aa857ee0 TL |
383 | SCO and Linux have. One user reported that adding the following to |
384 | /etc/rc.config.d/netconf helped (you may have to modify this to suit | |
385 | your local configuration): | |
386 | ||
387 | INTERFACE_NAME[0]=lan0 | |
388 | IP_ADDRESS[0]=1.1.1.1 | |
389 | SUBNET_MASK[0]=255.255.255.0 | |
390 | BROADCAST_ADDRESS[0]="255.255.255.255" | |
391 | LANCONFIG_ARGS[0]="ether" | |
392 | DHCP_ENABLE[0]=0 | |
26833160 TL |
393 | |
394 | ULTRIX | |
395 | ||
396 | Now that we have Ultrix packet filter support, the DHCP Distribution | |
397 | on Ultrix should be pretty trouble-free. However, one thing you do | |
398 | need to be aware of is that it now requires that the pfilt device be | |
399 | configured into your kernel and present in /dev. If you type ``man | |
400 | packetfilter'', you will get some information on how to configure your | |
401 | kernel for the packet filter (if it isn't already) and how to make an | |
402 | entry for it in /dev. | |
403 | ||
404 | FreeBSD | |
405 | ||
406 | Versions of FreeBSD prior to 2.2 have a bug in BPF support in that the | |
407 | ethernet driver swaps the ethertype field in the ethernet header | |
408 | downstream from BPF, which corrupts the output packet. If you are | |
409 | running a version of FreeBSD prior to 2.2, and you find that dhcpd | |
410 | can't communicate with its clients, you should #define BROKEN_FREEBSD_BPF | |
411 | in site.h and recompile. | |
a8b53b42 | 412 | |
98311e4b DH |
413 | Modern versions of FreeBSD include the ISC DHCP 3.0 client as part of |
414 | the base system, and the full distribution (for the DHCP server and | |
415 | relay agent) is available from the Ports Collection in | |
416 | /usr/ports/net/isc-dhcp3, or as a package on FreeBSD installation | |
417 | CDROMs. | |
418 | ||
adbef119 | 419 | NeXTSTEP |
a8f3586f TL |
420 | |
421 | The NeXTSTEP support uses the NeXTSTEP Berkeley Packet Filter | |
cd977bed TL |
422 | extension, which is not included in the base NextStep system. You |
423 | must install this extension in order to get dhcpd or dhclient to work. | |
a8f3586f | 424 | |
3dcbf508 TL |
425 | SOLARIS |
426 | ||
e950a7be SR |
427 | There are two known issues seen when compiling using the Sun compiler. |
428 | ||
429 | The first is that older Sun compilers generate an error on some of | |
430 | our uses of the flexible array option. Newer versions only generate | |
431 | a warning, which can be safely ignored. If you run into this error | |
432 | ("type of struct member "buf" can not be derived from structure with | |
7cfeb916 SR |
433 | flexible array member"), upgrade your tools to Oracle Solaris Studio |
434 | (previously Sun Studio) 12 or something newer. | |
e950a7be SR |
435 | |
436 | The second is the interaction between the configure script and the | |
437 | makefiles for the Bind libraries. Currently we don't pass all | |
438 | environment variables between the DHCP configure and the Bind configure. | |
439 | ||
440 | If you attempt to specify the compiler you wish to use like this: | |
441 | ||
442 | CC=/opt/SUNWspro/bin/cc ./configure | |
443 | ||
444 | "make" may not build the Bind libraries with that compiler. | |
445 | ||
446 | In order to use the same compiler for Bind and DHCP we suggest the | |
447 | following commands: | |
448 | ||
449 | CC=/opt/SUNWspro/bin/cc ./configure | |
450 | CC=/opt/SUNWspro/bin/cc make | |
451 | ||
7cfeb916 SR |
452 | Solaris 11 |
453 | ||
454 | We have integrated a patch from Oracle to use sockets instead of | |
455 | DLPI on Solaris 11. This functionality was written for use with | |
456 | Solaris Studio 12.2 and requires the system/header package. | |
457 | ||
458 | By default this code is disabled in order to minimize disruptions | |
459 | for current users. In order to enable this code you will need to | |
460 | enable both USE_SOCKETS and USE_V4_PKTINFO as part of the | |
461 | configuration step. The command line would be something like: | |
462 | ||
463 | ./configure --enable-use-sockets --enable-ipv4-pktinfo | |
464 | ||
b89b8e16 SR |
465 | Solaris 11 and ATF |
466 | ||
467 | We have reports that ATF 0.15 and 0.16 do not build on Solaris 11. The | |
468 | following changes to the ATF source code appear to fix this issue: | |
469 | ||
470 | diff -ru atf-0.15/atf-c/tp_test.c atf-0.15-patched/atf-c/tp_test.c | |
471 | --- atf-0.15/atf-c/tp_test.c 2011-12-06 06:31:11.000000000 +0100 | |
472 | +++ atf-0.15-patched/atf-c/tp_test.c 2012-06-19 15:54:57.000000000 +0200 | |
473 | @@ -28,6 +28,7 @@ | |
474 | */ | |
475 | ||
476 | #include <string.h> | |
477 | +#include <stdio.h> | |
478 | #include <unistd.h> | |
479 | ||
480 | #include <atf-c.h> | |
481 | ||
482 | diff -ru atf-0.15/atf-run/requirements.cpp atf-0.15-patched/atf-run/requirements.cpp | |
483 | --- atf-0.15/atf-run/requirements.cpp 2012-01-13 20:44:25.000000000 +0100 | |
484 | +++ atf-0.15-patched/atf-run/requirements.cpp 2012-06-19 15:41:51.000000000 +0200 | |
485 | @@ -29,7 +29,7 @@ | |
486 | ||
487 | extern "C" { | |
488 | #include <sys/param.h> | |
489 | -#include <sys/sysctl.h> | |
490 | +//#include <sys/sysctl.h> | |
491 | } | |
492 | ||
493 | #include <cerrno> | |
494 | ||
7cfeb916 SR |
495 | Other Solaris Items |
496 | ||
ce53cc84 TL |
497 | One problem which has been observed and is not fixed in this |
498 | patchlevel has to do with using DLPI on Solaris machines. The symptom | |
499 | of this problem is that the DHCP server never receives any requests. | |
35eb3023 TL |
500 | This has been observed with Solaris 2.6 and Solaris 7 on Intel x86 |
501 | systems, although it may occur with other systems as well. If you | |
502 | encounter this symptom, and you are running the DHCP server on a | |
503 | machine with a single broadcast network interface, you may wish to | |
504 | edit the includes/site.h file and uncomment the #define USE_SOCKETS | |
88cd8aca DH |
505 | line. Then type ``make clean; make''. As an alternative workaround, |
506 | it has been reported that running 'snoop' will cause the dhcp server | |
507 | to start receiving packets. So the practice reported to us is to run | |
508 | snoop at dhcpd startup time, with arguments to cause it to receive one | |
509 | packet and exit. | |
510 | ||
511 | snoop -c 1 udp port 67 > /dev/null & | |
ce53cc84 TL |
512 | |
513 | The DHCP client on Solaris will only work with DLPI. If you run it | |
514 | and it just keeps saying it's sending DHCPREQUEST packets, but never | |
515 | gets a response, you may be having DLPI trouble as described above. | |
88cd8aca DH |
516 | If so, we have no solution to offer at this time, aside from the above |
517 | workaround which should also work here. Also, because Solaris requires | |
518 | you to "plumb" an interface before it can be detected by the DHCP client, | |
519 | you must either specify the name(s) of the interface(s) you want to | |
520 | configure on the command line, or must plumb the interfaces prior to | |
521 | invoking the DHCP client. This can be done with ``ifconfig iface plumb'', | |
522 | where iface is the name of the interface (e.g., ``ifconfig hme0 plumb''). | |
ce53cc84 TL |
523 | |
524 | It should be noted that Solaris versions from 2.6 onward include a | |
525 | DHCP client that you can run with ``/sbin/ifconfig iface dhcp start'' | |
786b0930 DH |
526 | rather than using the ISC DHCP client, including DHCPv6. Consequently, |
527 | we don't believe there is a need for the client to run on Solaris, and | |
528 | have not engineered the needed DHCPv6 modifications for the dhclient-script. | |
529 | If you feel this is in error, or have a need, please contact us. | |
3dcbf508 | 530 | |
98311e4b DH |
531 | AIX |
532 | ||
533 | The AIX support uses the BSD socket API, which cannot differentiate on | |
534 | which network interface a broadcast packet was received; thus the DHCP | |
535 | server and relay will work only on a single interface. (They do work | |
536 | on multi-interface machines if configured to listen on only one of the | |
537 | interfaces.) | |
538 | ||
80778e94 | 539 | We have reports of Windows XP clients having difficulty retrieving |
fc06ee4f SR |
540 | addresses from a server running on an AIX machine. This issue |
541 | was traced to the client requiring messages be sent to the all ones | |
542 | broadcast address (255.255.255.255) while the AIX server was sending | |
543 | to 192.168.0.255. | |
544 | ||
545 | You may be able to solve this by including a relay between the client | |
546 | and server with the relay configured to use a broadcast of all-ones. | |
547 | ||
548 | A second option that worked for AIX 5.1 but doesn't seem to work for | |
549 | AIX 5.3 was to: | |
550 | create a host file entry for all-ones (255.255.255.255) | |
551 | and then add a route: | |
552 | route add -host all-ones -interface <local-ip-address> | |
553 | ||
98311e4b DH |
554 | The ISC DHCP distribution does not include a dhclient-script for AIX-- |
555 | AIX comes with a DHCP client. Contribution of a working dhclient-script | |
556 | for AIX would be welcome. | |
557 | ||
fc06ee4f | 558 | |
236d3a99 DH |
559 | MacOS X |
560 | ||
561 | The MacOS X system uses a TCP/IP stack derived from FreeBSD with a | |
562 | user-friendly interface named the System Configuration Framework. | |
563 | As it includes a builtin DHCPv4 client (you are better just using that), | |
564 | this text is only about the DHCPv6 client (``dhclient -6 ...''). The DNS | |
565 | configuration (domain search list and name servers' addresses) is managed | |
566 | by a System Configuration agent, not by /etc/resolv.conf (which is a link | |
567 | to /var/run/resolv.conf, which itself only reflects the internal state; | |
394c505d | 568 | the System Configuration framework's Dynamic Store). |
236d3a99 | 569 | |
394c505d SR |
570 | This means that modifying resolv.conf directly doesn't have the |
571 | intended effect, instead the macos script sample creates its own | |
572 | resolv.conf.dhclient6 in /var/run, and inserts the contents of this | |
573 | file into the Dynamic Store. | |
574 | ||
575 | When updating the address configuration the System Configuration | |
576 | framework expects the prefix and a default router along with the | |
577 | configured address. As this extra information is not available via | |
578 | the DHCPv6 protocol the System Configuration framework isn't usable | |
579 | for address configuration, instead ifconfig is used directly. | |
236d3a99 DH |
580 | |
581 | Note the Dynamic Store (from which /var/run/resolv.conf is built) is | |
394c505d SR |
582 | recomputed from scratch when the current location/set is changed. |
583 | Running the dhclient-script reinstalls the resolv.conf.dhclient6 | |
584 | configuration. | |
236d3a99 | 585 | |
6913a589 FD |
586 | |
587 | ATF | |
588 | ||
589 | Please see the file DHCP/doc/devel/atf.dox for a description of building | |
590 | and using these tools. | |
591 | ||
592 | The optional unit tests use ATF (Automated Testing Framework) including | |
593 | the atf-run and atf-report tools. ATF deprecated these tools in | |
594 | version 0.19 and removed these tools from its sources in version 0.20, | |
595 | requiring you to get an older version, use Kyua with an ATF compatibility | |
596 | package or use the version included in the Bind sources. | |
597 | ||
f76ebbfd TL |
598 | SUPPORT |
599 | ||
98311e4b DH |
600 | The Internet Systems Consortium DHCP server is developed and distributed |
601 | by ISC in the public trust, thanks to the generous donations of its | |
e021c50c | 602 | sponsors. ISC now also offers commercial quality support contracts for |
98311e4b DH |
603 | ISC DHCP, more information about ISC Support Contracts can be found at |
604 | the following URL: | |
605 | ||
2c85ac9b | 606 | https://www.isc.org/services/support/ |
98311e4b | 607 | |
e021c50c DH |
608 | Please understand that we may not respond to support inquiries unless |
609 | you have a support contract. ISC will continue its practice of always | |
610 | responding to critical items that effect the entire community, and | |
611 | responding to all other requests for support upon ISC's mailing lists | |
612 | on a best-effort basis. | |
98311e4b DH |
613 | |
614 | However, ISC DHCP has attracted a fairly sizable following on the | |
45d545f0 | 615 | Internet, which means that there are a lot of knowledgeable users who |
e021c50c DH |
616 | may be able to help you if you get stuck. These people generally |
617 | read the dhcp-users@isc.org mailing list. Be sure to provide as much | |
618 | detail in your query as possible. | |
0cd69353 | 619 | |
e021c50c DH |
620 | If you are going to use ISC DHCP, you should probably subscribe to |
621 | the dhcp-users or dhcp-announce mailing lists. | |
da411127 | 622 | |
98311e4b DH |
623 | WHERE TO SEND FEATURE REQUESTS: We like to hear your feedback. We may |
624 | not respond to it all the time, but we do read it. If ISC DHCP doesn't | |
625 | work well for you, or you have an idea that would improve it for your | |
626 | use, please send your suggestion to dhcp-suggest@isc.org. This is also | |
627 | an excellent place to send patches that add new features. | |
628 | ||
e021ce5c TL |
629 | WHERE TO REPORT BUGS: If you want the act of sending in a bug report |
630 | to result in you getting help in the form of a fixed piece of | |
631 | software, you are asking for help. Your bug report is helpful to us, | |
632 | but fundamentally you are making a support request, so please use the | |
1ad180b1 TL |
633 | addresses described in the previous paragraphs. If you are _sure_ that |
634 | your problem is a bug, and not user error, or if your bug report | |
e021c50c DH |
635 | includes a patch, you can send it to our ticketing system at |
636 | dhcp-bugs@isc.org. If you have not received a notice that the ticket | |
637 | has been resolved, then we're still working on it. | |
e021ce5c | 638 | |
da411127 TL |
639 | PLEASE DO NOT REPORT BUGS IN OLD SOFTWARE RELEASES! Fetch the latest |
640 | release and see if the bug is still in that version of the software, | |
802fdea1 TM |
641 | and if it is still present, _then_ report it. ISC release versions |
642 | always have three numbers, for example: 1.2.3. The 'major release' is | |
643 | 1 here, the 'minor release' is 2, and the 'maintenance release' is 3. | |
644 | ISC will accept bug reports against the most recent two major.minor | |
e021c50c DH |
645 | releases: for example, 1.0.0 and 0.9.0, but not 0.8.* or prior. |
646 | ||
647 | PLEASE take a moment to determine where the ISC DHCP distribution | |
648 | that you're using came from. ISC DHCP is sometimes heavily modified | |
649 | by integrators in various operating systems - it's not that we | |
650 | feel that our software is perfect and incapable of having bugs, but | |
651 | rather that it is very frustrating to find out after many days trying | |
652 | to help someone that the sources you're looking at aren't what they're | |
653 | running. When in doubt, please retrieve the source distribution from | |
654 | ISC's web page and install it. | |
0cd69353 | 655 | |
e021ce5c | 656 | HOW TO REPORT BUGS OR REQUEST HELP |
4650dc25 | 657 | |
da411127 TL |
658 | When you report bugs or ask for help, please provide us complete |
659 | information. A list of information we need follows. Please read it | |
660 | carefully, and put all the information you can into your initial bug | |
e021c50c DH |
661 | report. This will save us a great deal of time and more informative |
662 | bug reports are more likely to get handled more quickly overall. | |
0cd69353 | 663 | |
1ad180b1 | 664 | 1. The specific operating system name and version of the |
adbef119 | 665 | machine on which the DHCP server or client is running. |
1ad180b1 | 666 | 2. The specific operating system name and version of the |
adbef119 DH |
667 | machine on which the client is running, if you are having |
668 | trouble getting a client working with the server. | |
1ad180b1 | 669 | 3. If you're running Linux, the version number we care about is |
adbef119 DH |
670 | the kernel version and maybe the library version, not the |
671 | distribution version - e.g., while we don't mind knowing | |
672 | that you're running Redhat version mumble.foo, we must know | |
673 | what kernel version you're running, and it helps if you can | |
674 | tell us what version of the C library you're running, | |
675 | although if you don't know that off the top of your head it | |
676 | may be hard for you to figure it out, so don't go crazy | |
677 | trying. | |
1ad180b1 | 678 | 4. The specific version of the DHCP distribution you're |
adbef119 | 679 | running, as reported by dhcpd -t. |
1ad180b1 | 680 | 5. Please explain the problem carefully, thinking through what |
adbef119 DH |
681 | you're saying to ensure that you don't assume we know |
682 | something about your situation that we don't know. | |
e021c50c DH |
683 | 6. Include your dhcpd.conf and dhcpd.leases file as MIME attachments |
684 | if they're not over 100 kilobytes in size each. If they are | |
713a2956 | 685 | this large, please make them available to us, e.g., via a hidden |
e021c50c DH |
686 | http:// URL or FTP site. If you're not comfortable releasing |
687 | this information due to sensitive contents, you may encrypt | |
688 | the file to our release signing key, available on our website. | |
1ad180b1 | 689 | 7. Include a log of your server or client running until it |
adbef119 DH |
690 | encounters the problem - for example, if you are having |
691 | trouble getting some client to get an address, restart the | |
692 | server with the -d flag and then restart the client, and | |
693 | send us what the server prints. Likewise, with the client, | |
694 | include the output of the client as it fails to get an | |
695 | address or otherwise does the wrong thing. Do not leave | |
696 | out parts of the output that you think aren't interesting. | |
1ad180b1 | 697 | 8. If the client or server is dumping core, please run the |
adbef119 DH |
698 | debugger and get a stack trace, and include that in your |
699 | bug report. For example, if your debugger is gdb, do the | |
700 | following: | |
0cd69353 TL |
701 | |
702 | gdb dhcpd dhcpd.core | |
703 | (gdb) where | |
704 | [...] | |
705 | (gdb) quit | |
706 | ||
707 | This assumes that it's the dhcp server you're debugging, and | |
708 | that the core file is in dhcpd.core. | |
cd977bed | 709 | |
684111f9 | 710 | Please see https://www.isc.org/dhcp/ for details on how to subscribe |
98311e4b | 711 | to the ISC DHCP mailing lists. |
da411127 | 712 | |
fef8c6f0 SR |
713 | HISTORY |
714 | ||
715 | ISC DHCP was originally written by Ted Lemon under a contract with | |
716 | Vixie Labs with the goal of being a complete reference implementation | |
717 | of the DHCP protocol. Funding for this project was provided by | |
718 | Internet Systems Consortium. The first release of the ISC DHCP | |
719 | distribution in December 1997 included just the DHCP server. | |
720 | Release 2 in June 1999 added a DHCP client and a BOOTP/DHCP relay | |
721 | agent. DHCP 3 was released in October 2001 and included DHCP failover | |
722 | support, OMAPI, Dynamic DNS, conditional behaviour, client classing, | |
723 | and more. Version 3 of the DHCP server was funded by Nominum, Inc. | |
724 | The 4.0 release in December 2007 introduced DHCPv6 protocol support | |
725 | for the server and client. | |
726 | ||
727 | This product includes cryptographic software written | |
728 | by Eric Young (eay@cryptsoft.com). |