Newer Older
Ted Lemon's avatar
Ted Lemon committed
		     Internet Software Consortium
	   Dynamic Host Configuration Protocol Distribution
		   Version 3, Beta 1, Patchlevel 0
Ted Lemon's avatar
Ted Lemon committed
			     July 7, 1999
5 6 7 8 9 10 11 12 13 14 15


You should read this file carefully before trying to install or use
the ISC DHCP Distribution.


16 17 18 19
20 21
22 23 24 25 26 27 28 29 30 31 32 33 34 35
	 5.1	 LINUX
	  5.1.1	  IF_TR.H NOT FOUND
	  5.1.4	  BROADCAST
	  5.1.6	  IP BOOTP AGENT
	 5.2	 SCO
	 5.3	 HP-UX
	 5.4	 ULTRIX
	 5.5	 FreeBSD
	 5.6	 NeXTSTEP
	 5.7	 SOLARIS
38 39 40

Ted Lemon's avatar
Ted Lemon committed
41 42 43 44 45 46 47 48 49 50 51 52 53

Documentation for this software includes this README file, the
RELNOTES file, and the manual pages, which are in the server, common,
client and relay subdirectories.  Internet standards relating to the
DHCP protocol are stored in the doc subdirectory.  You will have the
best luck reading the manual pages if you build this software and then
install it, although you can read them directly out of the
distribution if you need to.

DHCP server documentation is in the dhcpd man page.  Information about
the DHCP server lease database is in the dhcpd.leases man page.
Server configuration documentation is in the dhcpd.conf man page as
well as the dhcp-options man page.   A sample DHCP server
54 55 56 57
configuration is in the file server/dhcpd.conf.   The source for the
dhcpd, dhcpd.leases and dhcpd.conf man pages is in the server/ sub-
directory in the distribution.   The source for the dhcp-options.5
man page is in the common/ subdirectory.
Ted Lemon's avatar
Ted Lemon committed
58 59 60 61 62 63

DHCP Client documentation is in the dhclient man page.  DHCP client
configuration documentation is in the dhclient.conf man page and the
dhcp-options man page.  The DHCP client configuration script is
documented in the dhclient-script man page.   The format of the DHCP
client lease database is documented in the dhclient.leases man page.
64 65 66
The source for all these man pages is in the client/ subdirectory in
the distribution.   In addition, the dhcp-options man page should be
referred to for information about DHCP options.
Ted Lemon's avatar
Ted Lemon committed

68 69
DHCP relay agent documentation is in the dhcrelay man page, the source
for which is distributed in the relay/ subdirectory.
Ted Lemon's avatar
Ted Lemon committed
70 71

To read installed manual pages, use the man command.  Type "man page"
72 73 74
where page is the name of the manual page.   This will only work if
you have installed the ISC DHCP distribution using the ``make install''
command (described later).
Ted Lemon's avatar
Ted Lemon committed
75 76 77 78 79 80

If you want to read manual pages that aren't installed, you can type
``nroff -man page |more'' where page is the filename of the
unformatted manual page.  The filename of an unformatted manual page
is the name of the manual page, followed by '.', followed by some
number - 5 for documentation about files, and 8 for documentation
81 82 83 84
about programs.   For example, to read the dhcp-options man page,
you would type ``nroff -man common/dhcp-options.5 |more'', assuming
your current working directory is the top level directory of the ISC
DHCP Distribution.
Ted Lemon's avatar
Ted Lemon committed
85 86 87 88 89 90 91 92 93 94 95 96

If you do not have the nroff command, you can type ``more catpage''
where catpage is the filename of the catted man page.  Catted man
pages names are the name of the manual page followed by ".cat"
followed by 5 or 8, as with unformatted manual pages.

Please note that until you install the manual pages, the pathnames of
files to which they refer will not be correct for your operating


97 98 99 100 101
This is the first beta release of version 3.0 of the ISC DHCP
Distribution.   Development of this release is approaching the point
at which it will be frozen, and no significant new features will be

In this release, the server and relay agent currently work well on
Ted Lemon's avatar
Ted Lemon committed
103 104 105 106 107 108
NetBSD, Linux after kernel version 2.0.30, FreeBSD, BSD/OS, Ultrix,
Digital Alpha OSF/1, Solaris and SunOS 4.1.4.  They run on AIX, HPUX,
IRIX and Linux 2.0.30 and earlier kernels but support only a single
broadcast network interface.  They also runs on QNX as long as only
one broadcast network interface is configured and a host route is
added from that interface to the broadcast address.

Ted Lemon's avatar
Ted Lemon committed
110 111 112 113 114
The DHCP client currently only knows how to configure the network on
NetBSD, FreeBSD, BSD/os, Linux, Solaris and NextStep.  The client
depends on a system-dependent shell script to do network
configuration - support for other operating systems is simply a matter
of porting this shell script to the new platform.
115 116

If you wish to run the DHCP Distribution on Linux, please see the
Ted Lemon's avatar
Ted Lemon committed
Linux-specific notes later in this document.  If you wish to run on an
118 119 120 121 122
SCO release, please see the SCO-specific notes later in this document.
You particularly need to read these notes if you intend to support
Windows 95 clients.  If you are running a version of FreeBSD prior to
2.2, please read the note on FreeBSD.  If you are running HP-UX or
Ultrix, please read the notes for those operating systems below.
Ted Lemon's avatar
Ted Lemon committed
If you are running NeXTSTEP, please see the notes on NeXTSTEP below.

125 126 127 128 129
If you start dhcpd and get a message, "no free bpf", that means you
need to configure the Berkeley Packet Filter into your operating
system kernel.   On NetBSD, FreeBSD and BSD/os, type ``man bpf'' for
information.   On Digital Unix, type ``man pfilt''.

Ted Lemon's avatar
Ted Lemon committed

131 132

133 134

135 136 137
To build the DHCP Distribution, unpack the compressed tar file using
the tar utility and the gzip command - type something like:

	zcat dhcp-3.0b1pl0.tar.gz |tar xvf -

Ted Lemon's avatar
Ted Lemon committed
140 141 142
On BSD/OS, you have to type gzcat, not zcat, and you may run into
similar problems on other operating systems.

143 144

Now, cd to the dhcp-3.0b1pl0 subdirectory that you've just
Ted Lemon's avatar
Ted Lemon committed
created and configure the source tree by typing:
147 148 149 150 151 152 153 154 155


If the configure utility can figure out what sort of system you're
running on, it will create a custom Makefile for you for that
system; otherwise, it will complain.  If it can't figure out what
system you are using, that system is not supported - you are on
your own.

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

An interim implementation of dynamic DNS updates is included in this
release.   This implementation is not currently supported, and is not
built by default.   To use this implementation, you must have
installed the latest version of bind 8.2 (see for
more information about BIND).   The configuration utility assumes that
the BIND 8.2 distribution libraries and includes are under the
/usr/local/bind directory, so if you have installed them elsewhere,
you should set the BINDLIB and BINDINC variables in site.conf to
override the values that will be set by the configure script from

Assuming that you have BIND 8.2 installed, you can build dynamic DNS
update support using:

		     ./configure --with-nsupdate

Note that there's no documentation for the dynamic DNS support yet,
and not many people are using it, so you should expect it to be
difficult to set up.   We will do our best to help you on the mailing
list, and more documentation will be forthcoming later.

Also, please note that this implementation is not the final DNS update
code, and the final code will probably be substantially different.


184 185 186 187 188 189 190 191 192
Once you've run configure, just type ``make'', and after a while
you should have a dhcp server.  If you get compile errors on one
of the supported systems mentioned earlier, please let us know.
If you get warnings, it's not likely to be a problem - the DHCP
server compiles completely warning-free on as many architectures
as we can manage, but there are a few for which this is difficult.
If you get errors on a system not mentioned above, you will need
to do some programming or debugging on your own to get the DHCP
Distribution working.

194 195

196 197 198 199
Once you have successfully gotten the DHCP Distribution to build, you
can install it by typing ``make install''.   If you already have an old
version of the DHCP Distribution installed, you may want to save it
before typing ``make install''.
Ted Lemon's avatar
Ted Lemon committed

201 202

203 204

205 206
There are three big LINUX issues: the all-ones broadcast address,
Linux 2.1 ip_bootp_agent enabling, and operations with more than one
Ted Lemon's avatar
Ted Lemon committed
207 208 209 210
network interface.   There are also two potential compilation/runtime
problems for Linux 2.1/2.2: the "SO_ATTACH_FILTER undeclared" problem
and the "protocol not configured" problem.

211 212 213 214 215 216 217 218 219 220

When you compile the distribution on Linux, you may get an error
message indicating that the include file if_tr.h could not be found.
If this happens, go into includes/cf/linux.h and delete the line that
defined HAVE_TR_SUPPORT, or look into installing a new version of libc
that includes the if_tr.h file.   We will be working on removing this
problem in the future, but for now, if you run into it, this should be
a viable workaround.

Ted Lemon's avatar
Ted Lemon committed
221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240

In addition, there is a minor issue that we will mention here because
this release is so close on the heels of the Linux 2.2 release: there
is a symlink in /usr/include that points at the linux asm headers.  It
appears to be not uncommon that this link won't be updated correctly,
in which case you'll get the following error when you try to build:

   lpf.c: In function `if_register_receive':
   lpf.c:152: `SO_ATTACH_FILTER' undeclared (first use this function)
   lpf.c:152: (Each undeclared identifier is reported only once
   lpf.c:152: for each function it appears in.)

The line numbers may be different, of course.   If you see this
header, your linux asm header link is probably bad, and you should
make sure it's pointing to correct linux source directory.


One additional Linux 2.1/2.2 issue: if you get the following message,
241 242
it's because your kernel doesn't have the linux packetfilter or raw
packet socket configured:
Ted Lemon's avatar
Ted Lemon committed

244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261
 Make sure CONFIG_PACKET (Packet socket) and CONFIG_FILTER (Socket
 Filtering) are enabled in your kernel configuration

If this happens, you need to configure your Linux kernel to support
Socket Filtering and the Packet socket.  You can do this by typing
``make config'', ``make menuconfig'' or ``make xconfig'', and then
enabling the Packet socket and Socket Filtering options that you'll
see displayed on the menu or in the questionnaire.  You can also edit
your linux kernel .config file directly: set CONFIG_FILTER=y and
CONFIG_PACKET=y.  If you do this, make sure you run ``make oldconfig''
afterwards, so that the changes you've made are propogated to the
kernel header files.   After you've reconfigured, you need to type
``make'' to build a new Linux kernel, and then install it in the
appropriate place (probably /linux).  Make sure to save a copy of your
old /linux.

If the preceding paragraph made no sense to you, ask your Linux
vendor/guru for help - please don't ask us.
262 263 264 265 266

If you set CONFIG_PACKET=m or CONFIG_FILTER=m, then you must tell the
kernel module loader to load the appropriate modules.  If this doesn't
make sense to you, don't use CONFIG_whatever=m - use CONFIG_whatever=y.  
Don't ask for help with this on the DHCP mailing list - it's a Linux
267 268
kernel issue.   This is probably not a problem with the most recent
Linux 2.2.x kernels.
Ted Lemon's avatar
Ted Lemon committed

Ted Lemon's avatar
Ted Lemon committed
Ted Lemon's avatar
Ted Lemon committed

272 273
In order for dhcpd to work correctly with picky DHCP clients (e.g.,
Windows 95), it must be able to send packets with an IP destination
274 275 276 277 278 279 280 281
address of  Unfortunately, Linux changes an IP
destination of into the local subnet broadcast address
(here, that's  This isn't a problem on Linux 2.2 and
later kernels, since we completely bypass the Linux IP stack, but on
old versions of Linux 2.1 and all versions of Linux prior to 2.1, it
is a problem - pickier DHCP clients connected to the same network as
the ISC DHCP server or ISC relay agent will not see messages from the
DHCP server.
Ted Lemon's avatar
Ted Lemon committed

283 284 285 286
It is possible to work around this problem on some versions of Linux
by creating a host route from your network interface address to   The command you need to use to do this on Linux
varies from version to version.   The easiest version is:
Ted Lemon's avatar
Ted Lemon committed

	route add -host dev eth0
Ted Lemon's avatar
Ted Lemon committed

290 291 292
On some older Linux systems, you will get an error if you try to do
this.   On those systems, try adding the following entry to your
/etc/hosts file:
Ted Lemon's avatar
Ted Lemon committed

294	all-ones
Ted Lemon's avatar
Ted Lemon committed

Then, try:
Ted Lemon's avatar
Ted Lemon committed

	route add -host all-ones dev eth0
Ted Lemon's avatar
Ted Lemon committed

Another route that has worked for some users is:
Ted Lemon's avatar
Ted Lemon committed

	route add -net dev eth0
Ted Lemon's avatar
Ted Lemon committed

304 305
If you are not using eth0 as your network interface, you should
specify the network interface you *are* using in your route command.
Ted Lemon's avatar
Ted Lemon committed

Ted Lemon's avatar
Ted Lemon committed
307 308 309 310 311 312 313 314 315 316 317 318 319 320 321

If you are running the DHCP server or client on a Linux system that's
also acting as a firewall, you must be sure to allow DHCP packets
through the firewall - Linux firewalls make filtering decisions before
they make the forwarding decision, so they will filter packets that
are intended for the firewall itself, as well as packets intended to
be forwarded.   In particular, your firewall rules _must_ allow
packets from IP address to IP address from UDP
port 68 to UDP port 67 through.   They must also allow packets from
your local firewall's IP address and UDP port 67 through to any
address your DHCP server might serve on UDP port 68.   Finally,
packets from relay agents on port 67 to the DHCP server on port 67,
and vice versa, must be permitted.

Ted Lemon's avatar
Ted Lemon committed
323 324 325 326 327 328 329

Some versions of the Linux 2.1 kernel apparently prevent dhcpd from
working unless you enable it by doing the following:

	      echo 1 >/proc/sys/net/ipv4/ip_bootp_agent

Ted Lemon's avatar
Ted Lemon committed
Ted Lemon's avatar
Ted Lemon committed

332 333 334 335 336 337
Very old versions of the Linux kernel do not provide a networking API
that allows dhcpd to operate correctly if the system has more than one
broadcast network interface.  However, Linux 2.0 kernels with version
numbers greater than or equal to 2.0.31 add an API feature: the
SO_BINDTODEVICE socket option.  If SO_BINDTODEVICE is present, it is
possible for dhcpd to operate on Linux with more than one network
Ted Lemon's avatar
Ted Lemon committed
interface.  In order to take advantage of this, you must be running a
Ted Lemon's avatar
Ted Lemon committed
339 340
2.0.31 or greater kernel, and you must have 2.0.31 or later system
headers installed *before* you build the DHCP Distribution.
Ted Lemon's avatar
Ted Lemon committed

Ted Lemon's avatar
Ted Lemon committed
342 343 344 345 346
We have heard reports that you must still add routes to
in order for the all-ones broadcast to work, even on 2.0.31 kernels.
In fact, you now need to add a route for each interface.   Hopefully
the Linux kernel gurus will get this straight eventually.

347 348 349 350
Linux 2.1 and later kernels do not use SO_BINDTODEVICE or require the
broadcast address hack, but do support multiple interfaces, using the
Linux Packet Filter.

Ted Lemon's avatar
Ted Lemon committed

353 354 355 356
SCO has the same problem as Linux (described earlier).  The thing is,
SCO *really* doesn't want to let you add a host route to the all-ones
broadcast address.  One technique that has been successful on some
versions of SCO is the very bizarre command:
Ted Lemon's avatar
Ted Lemon committed

	ifconfig net0 alias netmask
Ted Lemon's avatar
Ted Lemon committed

360 361 362 363 364 365 366
Apparently this works because of an interaction between SCO's support
for network classes and the weird netmask.  The 10.* network is just a
dummy that can generally be assumed to be safe.   Don't ask why this
works.   Just try it.   If it works for you, great.   If not, SCO is
supposedly adding hooks to support real DHCP service in a future
release - I have this on good authority from the people at SCO who do
*their* DHCP server and client.
Ted Lemon's avatar
Ted Lemon committed

368 369 370

HP-UX has the same problem with the all-ones broadcast address that
371 372 373 374 375 376 377 378 379 380
SCO and Linux have.   One user reported that adding the following to
/etc/rc.config.d/netconf helped (you may have to modify this to suit
your local configuration):

381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399


Now that we have Ultrix packet filter support, the DHCP Distribution
on Ultrix should be pretty trouble-free.  However, one thing you do
need to be aware of is that it now requires that the pfilt device be
configured into your kernel and present in /dev.  If you type ``man
packetfilter'', you will get some information on how to configure your
kernel for the packet filter (if it isn't already) and how to make an
entry for it in /dev.


Versions of FreeBSD prior to 2.2 have a bug in BPF support in that the
ethernet driver swaps the ethertype field in the ethernet header
downstream from BPF, which corrupts the output packet.   If you are
running a version of FreeBSD prior to 2.2, and you find that dhcpd
can't communicate with its clients, you should #define BROKEN_FREEBSD_BPF 
in site.h and recompile.
Ted Lemon's avatar
Ted Lemon committed

Ted Lemon's avatar
Ted Lemon committed
401 402 403

The NeXTSTEP support uses the NeXTSTEP Berkeley Packet Filter
Ted Lemon's avatar
Ted Lemon committed
404 405
extension, which is not included in the base NextStep system.  You
must install this extension in order to get dhcpd or dhclient to work.
Ted Lemon's avatar
Ted Lemon committed

Ted Lemon's avatar
Ted Lemon committed
407 408

Ted Lemon's avatar
Ted Lemon committed
409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438
One problem which has been observed and is not fixed in this
patchlevel has to do with using DLPI on Solaris machines.  The symptom
of this problem is that the DHCP server never receives any requests.
If you are using Solaris 2.6, and you encounter this symptom, and
you are running the DHCP server on a machine with a single broadcast
network interface, you may wish to edit the includes/site.h file and
uncomment the #define USE_SOCKETS line.  Then type ``make clean;

The DHCP client on Solaris will only work with DLPI.  If you run it
and it just keeps saying it's sending DHCPREQUEST packets, but never
gets a response, you may be having DLPI trouble as described above.
If so, you are SOL.  Also, because Solaris requires you to "plumb" an
interface before it can be detected by the DHCP client, you must
either specify the name(s) of the interface(s) you want to configure
on the command line, or must plumb the interfaces prior to invoking
the DHCP client.   This can be done with ``ifconfig iface plumb'',
where iface is the name of the interface (e.g., ``ifconfig hme0

It should be noted that Solaris versions from 2.6 onward include a
DHCP client that you can run with ``/sbin/ifconfig iface dhcp start''
rather than using the ISC DHCP client.  The feature set of the Solaris
client is different (not necessarily better or worse) than that of the
ISC client, but in most cases it will be a lot easier for you to just
use that.  Please do not ask for help in using the Solaris DHCP client
on Internet Software Consortium mailing lists - that's why you're
paying Sun the big bucks.   If you're having a problem with the
Solaris client interoperating with the ISC dhcp server, that's another
matter, but please check with Sun first.
Ted Lemon's avatar
Ted Lemon committed

Ted Lemon's avatar
Ted Lemon committed
440 441

Ted Lemon's avatar
Ted Lemon committed
442 443 444 445 446 447
The Internet Software Consortium DHCP server is not a commercial
product, and is not supported in that sense.  However, it has
attracted a fairly sizable following on the Internet, which means that
there are a lot of knowledgable users who may be able to help you if
you get stuck.  These people generally read the
mailing list.
448 449 450

If you are going to use dhcpd, you should probably subscribe to the
dhcp-server and dhcp-announce mailing lists.  If you will be using
Ted Lemon's avatar
Ted Lemon committed
dhclient, you should subscribe to the dhcp-client mailing list.
452 453 454 455 456 457 458 459 460 461 462 463 464

If you need help, you should ask on the dhcp-server or dhcp-client
mailing list (or both) - whichever is appropriate to your
application.   This includes reporting bugs.   Please do not report
bugs in old software releases - fetch the latest release and see if
the bug is still in that copy of the software, and if it's not, _then_
report it.   It's okay to report bugs in the latest patchlevel of a
major version that's not the most recent major version, though - for
example, if you're running 2.0, you don't have to upgrade to 3.0
before you can report bugs.


465 466

467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515
When you report bugs, please provide us complete information.   A list
of information we need follows.   Please read it carefully, and put
all the information you can into your initial bug report, so that we
don't have to ask you any questions in order to figure out your

	- The specific operating system name and version of the
          machine on which the DHCP server or client is running.
	- The specific operating system name and version of the
          machine on which the client is running, if you are having
          trouble getting a client working with the server.
	- If you're running Linux, the version number we care about is
          the kernel version and maybe the library version, not the
          distribution version - e.g., while we don't mind knowing
          that you're running Redhat version, we must know
          what kernel version you're running, and it helps if you can
          tell us what version of the C library you're running,
          although if you don't know that off the top of your head it
          may be hard for you to figure it out, so don't go crazy
	- The specific version of the DHCP distribution you're
          running, for example 2.0b1pl19, not 2.0.
	- Please explain the problem carefully, thinking through what
          you're saying to ensure that you don't assume we know
          something about your situation that we don't know.
	- Include your dhcpd.conf and dhcpd.leases file if they're not
          huge (if they are huge, we may need them anyway, but don't
          send them until you're asked).
	- Include a log of your server or client running until it
          encounters the problem - for example, if you are having
          trouble getting some client to get an address, restart the
          server with the -d flag and then restart the client, and
          send us what the server prints.   Likewise, with the client,
          include the output of the client as it fails to get an
          address or otherwise does the wrong thing.   Do not leave
          out parts of the output that you think aren't interesting.
	- If the client or server is dumping core, please run the
          debugger and get a stack trace, and include that in your
          bug report.   For example, if your debugger is gdb, do the

		gdb dhcpd dhcpd.core
		(gdb) where
		(gdb) quit

	  This assumes that it's the dhcp server you're debugging, and
	  that the core file is in dhcpd.core.

Ted Lemon's avatar
Ted Lemon committed
516 517 518
PLEASE DO NOT send queries about non-isc clients to the dhcp-client
mailing list.   If you're asking about them on an ISC mailing list,
it's probably because you're using the ISC DHCP server, so ask there.
519 520 521
If you are having problems with a client whose executable is called
dhcpcd, this is _not_ the ISC DHCP client, and we probably can't help
you with it.
Ted Lemon's avatar
Ted Lemon committed
522 523 524 525 526 527 528

Please see for details on how to
subscribe.  If you don't have WorldWide Web access, you can send mail
to and tell me which lists you want to
subscribe to, but please use the web interface if you can, since I
have to handle the -request mailing list manually, and I will give you
the third degree if you make me do your subscription manually.
529 530 531 532 533 534 535 536 537 538 539

people using the DHCP Distribution is sufficiently large that if I
take an interrupt every time any one of those people runs into
trouble, I will never get any more coding done.

takes a lot more of my time and attention than answering email.  If you
do call me on the phone, I will tell you to send email to the mailing
list, and I won't answer your question, so there's no point in doing