DHCP stands for "Dynamic Host Configuration Protocol".
DHCP's purpose is to enable individual computers on an IP network to extract their configurations from a server (the 'DHCP server') or servers, in particular, servers that have no exact information about the individual computers until they request the information. The overall purpose of this is to reduce the work necessary to administer a large IP network.
DHCP was created by the Dynamic Host Configuration Working Group of the Internet Engineering Task Force (IETF; a volunteer organization which defines protocols for use on the Internet). As such, it's definition is recorded in an Internet RFC and the Internet Activities Board (IAB) is asserting its status as to Internet Standardization. As of this writing (March 1996), DHCP is an Internet Proposed Standard Protocol and is Elective. BOOTP is an Internet Draft Standard Protocol and is Recommended. For more information on Internet standardization, see RFC1920 (March 1996).
DHCP is based on BOOTP and maintains some backward compatibility. The main difference is that BOOTP was designed for manual pre-configuration of the host information in a server database, while DHCP allows for dynamic allocation of network addresses and configurations to newly attached hosts. Additionally, DHCP allows for recovery and reallocation of network addresses through a leasing mechanism.
RARP is a protocol used by Sun and other vendors that allows a computer to find out its own IP number, which is one of the protocol parameters typically passed to the client system by DHCP or BOOTP. RARP doesn't support other parameters and using it, a server can only serve a single LAN. DHCP and BOOTP are designed so they can be routed.
It is theoretically possible for client-machines to find addresses to use by picking an address out of the blue and broadcasting a request of all the other client machines to see if they are using them. Appletalk is designed around this idea, and Apple's MacTCP can be configured to do this for IP. However, this method of IP address assignment has disadvantages.
Yes. At least there is nothing in the protocol to preclude this and one expects it to be a feature of any DHCP server. This is really a server matter and the client should work either way. The RFC refers to this as manual allocation.
Only if the DHCP server is specifically written to also handle BOOTP queries.
Only if the DHCP client were specifically written to make use of the answer from a BOOTP server. It would presumably treat a BOOTP reply as an unending lease on the IP address.
In particular, the TCP/IP stack included with Windows 95 does not have this capability.
The RFC on such interoperability (1534) is clear: "In summary, a DHCP server: ... MAY support BOOTP clients," (section 2). The word "MAY" indicates such support, however useful, is left as an option.
The RFC on such interoperability (1534) is clear: "A DHCP client MAY use a reply from a BOOTP server if the configuration returned from the BOOTP server is acceptable to the DHCP client." (section 3). The word "MAY" indicates such support, however useful, is left as an option.
A source of confusion on this point is the following statement in section 1.5 of RFC 1541: "DHCP must provide service to existing BOOTP clients." However, this statement is one in a list of "general design goals for DHCP", i.e. what the designers of the DHCP protocol set as their own goals. It is not in a list of requirements for DHCP servers.
No. There has been some discussion about adding this ability to DHCP.
(Note: as far as I can tell, the DNS needs no protocol update since the server already tells the clients how long they can use the information they receive; what is really needed is a DNS server that can make fuller use of this feature and that cooperates with a DHCP server, perhaps through the use of some new "DHCP-server-to-DNS-server" protocol).
You can have two or more servers handing out leases for different addresses. If each has a dynamic pool accessible to the same clients, then even if one server is down, one of those clients can lease an address from the other server.
However, without communication between the two servers to share their information on current leases, when one server is down, any client with a lease from it will not be able to renew their lease with the other server. Such communication is the purpose of the "server to server protocol" (see next question). It is possible that some server vendors have addressed this issue with their own proprietary server-to-server communication.
The DHC WG of the IETF is actively investigating the issues in inter-server communication. The protocol should be defined "soon".
There are several:
List Purpose ---- ------- email@example.com General discussion: a good list for server administrators. firstname.lastname@example.org DHCP bakeoffs email@example.com Implementations firstname.lastname@example.org Server to server protocol email@example.com DNS-DHCP issues firstname.lastname@example.org DHCP for IPv6The lists are run by email@example.com which can be used to subscribe and sign off. Archives for the dhcp-v4 list (which used to be called the host-conf list) are stored at ftp://ftp.bucknell.edu/pub/dhcp/.
DHCP client messages are sent to off-net servers by DHCP relay agents, which are often a part of an IP router. The DHCP relay agent records the subnet from which the message was received in the DHCP message header for use by the DHCP server.
Note: a DHCP relay agent is the same thing as a BOOTP relay agent, and technically speaking, the latter phrase is correct.
A single LAN might have more than one subnet number applicable to the same set of ports (broadcast domain). Typically, one subnet is designated as primary, the others as secondary. A site may find it necessary to support addresses on more than one subnet number associated with a single interface. DHCP's scheme for handling this is that the server has to be configured with the necessary information and has to support such configuration & allocation. Here are four cases a server might have to handle:
One way to do this is to preconfigure each client with information about what group it belongs to. A DHCP feature designed for this is the user class option. To do this, the client software must allow the user class option to be preconfigured and the server software must support its use to control which pool a client's address is allocated from.
In Internet RFCs.
See the dhcp-v4 mailing list mentioned above as well as its archives.
PPP has its own non-DHCP way in which communications servers can hand clients an IP address called IPCP (IP Control Protocol) but doesn't have the same flexibility as DHCP or BOOTP in handing out other parameters. Such a communications server may support the use of DHCP to acquire the IP addresses it gives out. This is sometimes called doing DHCP by proxy for the client. I know that Windows NT's remote access support does this.
A feature of DHCP under development (DHCPinform) is a method by which a DHCP server can supply parameters to a client that already has an IP number. With this, a PPP client could get its IP number using IPCP, then get the rest of its parameters using this feature of DHCP.
SLIP has no standard way in which a server can hand a client an IP address, but many communications servers support non-standard ways of doing this that can be utilized by scripts, etc. Thus, like communications servers supporting PPP, such communications servers could also support the use of DHCP to acquire the IP addressees to give out.
I am not currently aware of any way in which DHCP can support client-computers served solely by PPP or SLIP. Such a computer doesn't have the IEEE-style MAC address that DHCP requires to act as its key to determining which client-computer is which within the same subnet. Communications servers that acquire IP numbers for their clients via DHCP run into the same roadblock in that they have just one MAC address, but need to acquire more than one IP address. One way such a communications server can get around this problem is through the use of a set of unique pseudo-MAC addresses for the purposes of its communications with the DHCP server. Another way (used by Shiva) is to use a different "client ID type" for your hardware address. Client ID type 1 means you're using MAC addresses. However, client ID type 0 means an ASCII string.
There is nothing in the protocol to keep a client that already has a leased or permanent IP number from getting a(nother) lease on a temporary basis on another subnet (i.e., for that laptop which is almost always in one office, but occasionally is plugged in in a conference room or class room). Thus it is left to the server implementation to support such a feature. I've heard that Microsoft's NT-based server can do it.
A server on a net(subnet) can relay DHCP or BOOTP for that net. Microsoft has software to make Windows NT do this.
I don't have an answer for this, but will offer a little discussion. The answer depends a lot on what BOOTP server you are using and how you are maintaining it. If you depend heavily on BOOTP server software to support your existing clients, then the demand to support clients that support DHCP but not BOOTP presents you with problems. In general, you are faced with the choice:
Sites may choose to require central pre-configuration for all computers that will be able to acquire a dynamic address. A DHCP server could be designed to implement such a requirement, presumably as an option to the server administrator. See section below on servers that implement this.
There is no standard MIB; creating one is on the list of possible activities of the DHCP working group. It is possible that some servers implement private MIBs.
While the DHCP server protocol is designed to support dynamic management of IP addresses, there is nothing to stop someone from implementing a server that uses the DHCP protocol, but does not provide that kind of support. In particular, the maintainer of a BOOTP server-implementation might find it helpful to enhance their BOOTP server to allow DHCP clients that cannot speak "BOOTP" to retrieve statically defined addresses via DHCP. The following terminology has become common to describe three kinds of IP address allocation/management. These are independent "features": a particular server can offer or not offer any of them:
Other features which a DHCP server may or may not have:
Following are some features related not to the functions that the server is capable of carrying out, but to the way that it is administered.
(This is not necessarily a complete list)
950415 Bootp server: Bootp 2.4.3 (not DHCP, but with the "DHCP patches" mentioned below, can handle DHCP requests) ftp://ftp.mc.com/pub/bootp-2.4.3.tar.Z 950425 Bootp server version 2.4.3 with "samba" DHCP patches (does manual allocation of IP addresses) http://www.sghms.ac.uk/~mpreston/bootp_dhcp.tar.Z (within http://www.sghms.ac.uk/~mpreston/tools.htm") 950706 "samba" DHCP patches for bootp server: (does manual allocation of IP addresses) ftp://nimbus.anu.edu.au:/pub/tridge/samba/contributed/DHCP.patch (note: I've heard that the patched server will crash if it receives one particular optional packet, the DHCP Release packet) 950711 Patched bootp server supporting DHCP-based "automatic" allocation: (gives addresses dynamically, but never takes them away) ftp://ftp.ntplx.net/pub/networking/bootp/bootp-DD2.4.3.tar.gz 951219 BOOTP server and patches for DHCP ftp://africa.geomic.uni-oldenburg.de/pub/people/joey/dhcp/bootpd/ 960112 OS/2 port of BOOTP server with patches for manual DHCP support ftp://ftp.leo.org/pub/comp/os/os2/tcpip/systools/bootpd-243-dhcp.zip 960130 Rose-Hulman Institute of Technology "Mondo-DB" LAN administration project: modified DHCP server planned http://www.rose-hulman.edu/~allard/Mondo-DB/index.html 950630 WIDE Project: Akihiro Tominaga (firstname.lastname@example.org) WIDE Project Keio Univ. Japan ftp://sh.wide.ad.jp/WIDE/free-ware/dhcp/dhcp-1.2.1.tar.gz Check Archie for dhcp-1.2.1 because lots of sites distribute it. Beta version: ftp://sh.wide.ad.jp/WIDE/free-ware/dhcp/dhcp-1.3beta.tar.gz 960312 Carnegie Mellon University DHCP/BOOTP server (SunOS, dhcp-3.3.7) ftp://ftp.net.cmu.edu/pub/dhcp/dhcp-3.3.7.tar.gz 960910 Internet Software Consortium (ISC) DHCP/BOOTP Server ftp://ftp.fugue.com/pub/DHCPD-BETA-5.9.tar.gz http://www.isc.org/isc 961015 Princeton patch to dhcpd 3.7.7. http://www.princeton.edu/~irwin/src/CMU-dhcpd-3.3.7-PU-patch1.Z
(This is not necessarily a complete list)
951010 Wollongong: included in next release of PathWay for OpenVMS which is in beta 951010 TGV: DHCP/BOOTP server will be included in Multinet for VMS v3.5. http://www.tgv.com/ 951121 TGV(800-848-3440): MultiNet 3.5 for OpenVMS includes DHCP server. mailto:email@example.com http://www.tgv.com/ 951207 IBM: DHCP server included in AIX 4.1.4 server packages. Also includes custom DNS server that is "DHCP knowledgeable". http://www.ibmlink.ibm.com/(search for DHCP in SalesManual) 951219 Puzzle Systems: WEBserv (NLM(s) that do DHCP, BOOTP, HTTP, and FTP) mailto:firstname.lastname@example.org http://www.puzzle.com/ 951220 Process Software: server for OpenVMS included in TCPware for OpenVMS http://www.process.com/ 960110 Quadritek Systems, Inc. (DHCP server included in next release) http://www.qtek.com/qsi-qip.html 960130 Digital: RoamAbout Mobile IP Client/Server Network Software V2.0 http://www.digital.com/info/Customer-Update/940620001.txt.html 960312 Nevod Inc. Proxy IP/DHCP Server (PIP) Beta-1.0 http://www.nevod.com/pip/index.html 960327 Xedia: IP/Assist 1.0 feature for their switches includes DHCP service. http://www.xedia.com 960419 Hewlett-Packard: HP-UX 10.10 includes a bootp server with DHCP extensions. 960420 Competitive Automation's JOIN (415-321-4006): SunOS4.x, Solaris2.x, Digital Unix 3.2, 4.x, HP-UX 9 & 10 DHCP/BOOTP servers. http://www.join.com/ 960514 IBM: DHCP/BOOTP server included in Warp Server 3.0 (OS/2). 960514 SunSoft: Solstice SolarNet PC-Admin 1.5 includes a DHCP/BOOTP server. http://www.sun.com/solstice/Networking-products/PC-Admin.html 960514 Microsoft: DHCP server included in WIndows NT Server 3.51 http://www.microsoft.com/NTServer/ http://www.microsoft.com/BackOffice/techbriefs/tech1000.htm ftp://ftp.microsoft.com/bussys/winnt/winnt-docs/papers/tcpipimp.doc 960514 ON Technology: IPTrack 1.0 is a Novell Server-based DHCP/BOOTP server (NLM) http://www.on.com/on/onprods/iptrack.html/ 960514 FTP Software: OnNet Server 2.0 (Services OnNet Product) http://www.ftp.com/mkt_info/services.html 960531 Cisco: server in development. http://www.cisco.com 960620 Farallon: a DHCP server is built into its Netopia Internet Router http://www.farallon.com 960710 Sonic Systems: Sonic DHCP Internet Server runs on MacOS http://www.sonicsys.com/dhcp.html 960716 Weird Solutions: BOOTP Server NT supports both BOOTP and statically allocated DHCP. http://www.mhi.se 960808 Novell: NetWare/IP 2.2 (free upgrade to NetWare servers) includes a DHCP/BOOTP server; unlike NetWare/IP 2.2 itself, this server will run on NetWare 3.12. ftp://ftp.novell.com/updates/unixconn/nwip22/nip22b.exe http://netware.novell.com/discover/nwip/index.htm 960809 Silicon Graphics: 'proclaim' software for SGI workstations; part of IRIXpro. http://www.sgi.com/Products/hardware/challenge/IRIXpro/IRIXpro.html http://www.sgi.com/Products/hardware/challenge/IRIXpro/IRIXprospecs.html 960829 Isotro: NetID DHCP Server (BOOTP/DHCP server) http://www.isotro.com 960904 VICOM: VICOM DHCP Server (runs on MacOS) http://www.vicomtech.com 960912 Cisco: (announced) DHCP/BOOTP server for Solaris, HP-UX, and AIX, Windows NT (Alpha & Intel) included in Cisco's DNS/DHCP Manager V1.0 and Cisco's Server Suite 1000 V1.0 http://www.cisco.com 960917 SunSoft: (future) DHCP/BOOTP server to be bundled with Solaris 2.6 or as hte "Internet Server Supplement" to Solaris 2.5.1. http://www.sun.com/ 961003 Network TeleSystems: Shadow (PC-based) http://www.nts.com/NTS/shadow.html
(This is not necessarily a complete list)
960809 WIDE Project includes a client for BSD and SunOS systems: Akihiro Tominaga (email@example.com) WIDE Project Keio Univ. Japan ftp://sh.wide.ad.jp/WIDE/free-ware/dhcp/dhcp-1.2.1.tar.gz Check Archie for dhcp-1.2.1 because lots of sites distribute it. Beta version: ftp://sh.wide.ad.jp/WIDE/free-ware/dhcp/dhcp-1.3beta.tar.gz 960904 Linux bootp client: bootpc; DHCP being added over time. ftp://ftp.dampt.cam.ac.uk/pub/linux/bootpc/ 960910 Internet Software Consortium (ISC) DHCP/BOOTP Server includes a minimal client that can be used for testing. See ISC server in section above on "Freeware Servers". 961003 dhcpcd 0.4 (for Linux 1.2.xx, 1.3.xx, and 2.0.x) ftp://sunsite.unc.edu/pub/Linux/system/Network/daemons/dhcpcd-0.4.tar.gz
(This is not necessarily a complete list)
950417 Shiva: proxy client for remote users (in Lanrovers and Netmodems) 950425 Hewlett-Packard 950502 NetManage: Chameleon 4.5 950630 Beame & Whiteside Software: resells Dirk Koeppen EDV-Beratungs-GmbH's TCP/IP BOOT-PROM 950705 Microsoft: MS-TCP/IP 3.11a & MS-TCP/IP 3.11b 950711 Microsoft: Windows NT 3.5 950711 Microsoft: Windows for Workgroups 3.11a 950711 Frontier Technologies(800-929-3054): in SuperTCP for Windows http:www.frontiertech.com firstname.lastname@example.org 950712 Beame & Whiteside(800-720-7151): BW-Connect NFS for DOS & Windows 950725 IBM: a future release of AIX 950802 Wollongong: PathWay Access ver 3.2 (Windows) http://www.twg.com/ 950802 WRQ: Reflection Network Series products (version 5) for Windows http://www.wrq.com/ 950814 Competitive Automation(415-321-4006): SunOS4.x, Solaris2.x and DECOSF3.x,4.x clients 950915 Stampede: included in Remote Office Gold 951113 Persoft(800-368-5283): TCP Addition and Portable TCP http://www.persoft.com 951207 Dirk Koeppen EDV-Beratungs-GmbH: TCP/IP DHCP Boot ROMs (TCP/IP BOOT-PROM) www.dunkel.de/dksoft 951207 IBM: AIX 4.1.4 client and server packages include a DHCP client. http://www.ibmlink.ibm.com/(search for DHCP in SalesManual) 951220 Attachmate: IRMA TCP Suite Version 3.1 960130 Digital: RoamAbout Mobile IP Client/Server Network Software V2.0 http://www.digital.com/info/Customer-Update/940620001.txt.html 960209 FTP Software: included in OnNet 2.0 (Windows) http://www.ftp.com/ 960209 FTP Software: PC/TCP 4.0 (DOS) http://www.ftp.com/ 960312 Core Systems: Internet-Connect for Windows 95 Version 2.1 has DHCP proxy client. http://ns1.win.net/~core/Coresys/homepage.html 960313 Apple: Open Transport 1.1 included with System 7.5.3 & runs on 68030, 68040, and PowerPC Macintoshes. 960314 Apple: Open Transport 1.1 shrink wrap version will be offered. 960408 IBM: Client DHCP software for Windows 3.x. 960408 IBM: Client DHCP software for MS/PC-DOS. 960501 SunSoft: included in PC-NFS Pro 2.0 for Windows 960501 TGV: included in MultiNet for Windows V1.2 http://www.tgv.com/ 960501 NetManage: included in ChameleonNFS 4.6 960503 FTP Software: included in OnNet32, Version 1.0 (Windows 95 and NT) http://www.ftp.com/ 960514 Novell: Client32 for DOS/Windows 3.1 (beta) will use either DHCP or BOOTP to get IP parameters. 960514 Novell: NetWare/IP for DOS, Windows 3.1, Windows 95, and Windows NT uses DHCP to obtain IP parameters. 960514 Novell: NetWare/IP servers can use DHCP to auto-configure their IP parameters. 960606 IBM: Clients built with OS/2 Warp Server code include DHCP client code. Note that OS/2 Warp Connect supports BOOTP but not DHCP. 960715 IBM fixpak for OS/2 WARP (the WARP Connect Version) that includes a DHCP client: UN00067 (updates TCP/IP V3.0 and assumes fixpak WR08210 has been applied to update MPTS). ftp://service.boulder.ibm.com 960809 Silicon Graphics: included in IRIX since version 5.3. http://www.sgi.com/Products/software/IRIX6.2/IRIX62DS.html http://www.sgi.com/Products/hardware/challenge/IRIXpro/IRIXpro.html 960823 IBM future version of OS/2 (codenamed Merlin) will include DHCP in the basic package. 960917 Sun: Solaris 2.6. http://www.sun.com/
(This is not necessarily a complete list).
Note that in general, these routers probably already had BOOTP forwarding, but lacked the support for the BOOTP broadcast flag (see "broadcast flag" under What are the Gotcha's? above). It is likely that many other routers also support BOOTP forwarding.
DHCP requires disk storage (or some other form of reliable non-volatile storage), making the task of DHCP service more compatible with servers than with dedicated routers. The large-scale routers (i.e., those of Cisco, Bay, Fore) don't an will probably never will have a DHCP server function.
But there are a number of types of servers that can be configured to route and serve DHCP. This includes Novell servers and computers running Unix. There are also units designed to handle two or more aspects of your Internet connection, e.g. routing between a LAN and a leased line as well as doing other functions to allow computers on the LAN to reach the Internet (or corporate intranet as the case may be). One example is Farallon's Netopia Internet Router mentioned above under commercial servers.
The DHCP RFC specifically says that DHCP is not intended for use in configuring routers. The reason is that in maintaining and troubleshooting routers, it is important to know its exact configuration rather than leaving that to be automatically done, and also that you do not want your router's operation to depend upon the working of yet another server.
It may be possible to configure some types of more general-purpose computers or servers to get their addresses from DHCP and to act as routers. Also, there are remote access servers, often which are usually not true routers, which use DHCP to acquire addresses to hand out to their clients.
The broadcast flag is an optional element of DHCP, but a client which sets it works only with a server or relay that supports it.
(These are not a complete lists) The following servers can handle dynamic allocation on secondary subnet numbers:
The following can serve manually allocated addresses on secondary subnet numbers:
The following cannot support secondary subnet numbers:
Not really a DHCP question, but it has been asked a lot, particularly by sites for which changing from BOOTP represents a lot of work. Some choices:
A Document that addresses this question is the Windows 95tm Networking FAQ, http://www-leland.stanford.edu/~llurch/win95netbugs/faq.html
In many cases, new releases have solved the problems that have been identified with various DHCP implementations.