DHCP for Linux?
Adrian Ball
--
Adrian Ball Bio-Informatics Dept, IACR-Rothamsted
adria...@bbsrc.ac.uk Harpenden, Herts
+44 1582 763133 - ext 2419 England
http://www.res.bbsrc.ac.uk/computing/staff/adrian.html AL5 2JQ
Bruce Lyon
: The subject says it all!
check out latest bootp stuff on your nearest archie ...!
: --
Martin Giguere
DHCP FAQ
Author
John Wobus, jmw...@syr.edu (corrections welcome)
Date
8/15/1995
This file
http://web.syr.edu/~jmwobus/comfaqs/dhcp.faq.html
Questions
1. General
1. What is DHCP?
2. What is DHCP's purpose?
3. How is it different that BOOTP or RARP?
4. Why shouldn't clients assign IP numbers without the use of a
server?
5. Can DHCP support statically defined addresses?
6. Can a BOOTP client boot from a DHCP server?
7. Can a DHCP client boot from a BOOTP server?
8. Can a DHCP client update its DNS entry through DHCP?
9. When will the server to server protocol be defined?
10. Is there a DHCP mailing list?
11. In a subnetted environment, how does the DHCP server discover
what subnet a request has come from?
12. Where is DHCP defined?
13. Can DHCP support remote access?
14. What are the Gotcha's?
2. Info on Implementations
1. What freeware DHCP servers are available?
2. What commercial DHCP servers are available?
3. Which vendors of client software currently support DHCP?
4. What are the DHCP plans of major client-software vendors?
5. What Routers forward DHCP requests?
6. Which implementations support or require the broadcast flag?
Answers
1. General
1. What is DHCP?
DHCP stands for "Dynamic Host Configuration Protocol".
2. What is DHCP's purpose?
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.
3. How is it different that BOOTP or RARP?
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.
4. Why shouldn't clients assign IP numbers without the use of a
server?
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.
1. A computer that needs a permanently-assigned IP number
might be turned off and lose its number to a machine
coming up. This has problems both for finding services
and for security.
2. A network might be temporarily divided into two
non-communicating networks while a network component is
not functioning. During this time, two different
client-machines might end up claiming the same IP
number. When the network comes back, they start
malfunctioning.
3. If such dynamic assignment is to be confined to ranges
of IP addresses, then the ranges are configured in each
desktop machine rather than being centrally
administered. This can lead both to hidden configuration
errors and to difficulty in changing the range. Another
problem with the use of such ranges is keeping it easy
to move a computer from one subnet to another.
5. Can DHCP support statically defined addresses?
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.
6. Can a BOOTP client boot from a DHCP server?
A DHCP server can be written this way. Since DHCP was
developed after BOOTP, it would be logical for most server
developers to support this.
7. Can a DHCP client boot from a BOOTP server?
A DHCP client can be written this way, i.e. to treat a BOOTP
reply as an unending lease on the IP address.
8. Can a DHCP client update its DNS entry through DHCP?
There are options in DHCP through which a DHCP client can
request that its DNS entry be updated. DHCP clients will be
able to take advantage of planned enhancements to the DNS
protocol that will allow dynamic updates through the network.
(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).
9. When will the server to server protocol be defined?
The DHC WG of the IETF is actively investigating the issues
in inter-server communication. The protocol should be defined
"soon".
10. Is there a DHCP mailing list?
There are several:
List Purpose
---- -------
host...@sol.eg.bucknell.edu General discussion
dhcp...@bucknell.edu DHCP bakeoffs
dhcp...@bucknell.edu Implementations
dhcp-...@bucknell.edu Server to server protocol
Admin requests for the host-conf list should go to
host-con...@sol.eg.bucknell.edu; admin requests for
the other lists should go to list...@bucknell.edu.
11. In a subnetted environment, how does the DHCP server discover
what subnet a request has come from?
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.
12. Where is DHCP defined?
In Internet RFCs.
RFC1541
R. Droms, "Dynamic Host Configuration Protocol",
10/27/1993.
RFC1534
R. Droms, "Interoperation Between DHCP and BOOTP",
10/08/1993.
RFC1533
S. Alexander, R. Droms, "DHCP Options and BOOTP
Vendor Extensions", 10/08/1993.
13. Can DHCP support remote access?
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.
14. What are the Gotcha's?
o Someone suggested to me that a malicious user could make
trouble by putting up an unofficial DHCP server. The
main problem I can see is the potential for two or more
"innocent bystander" nodes ending up with the same IP
number. Net result is problems using the nodes, possibly
intermittent of one or the other is sometimes turned
off.
o The "broadcast flag": DHCP includes a way in which
client implementations unable to receive a packet with a
specific IP address can ask the server or relay agent to
use the broadcast IP address in the replies (a "flag"
set by the client in the requests). The definition of
DHCP states that implementations "should" honor this
flag, but it doesn't say they "must". Some Microsoft
TCP/IP implementations used this flag, which meant in
practical terms, relay agents and servers had to
implement it. A number of BOOTP-relay-agent
implementations (e.g. in routers) handled DHCP just fine
except for the need for this feature, thus they
announced new versions stated to handle DHCP.
o Some of the virtual LAN schemes, i.e., those that use
the packet's IP number to decide which "virtual LAN" a
client-computer is on for the purposes of TCP/IP, don't
work when using DHCP to dynamically assign addresses.
DHCP servers and relay agents use their knowledge of
what LAN the client-station is on to select the subnet
number for the client-station's new IP address whereas
such switches use the subnet number sent by the
client-station to decide which (virtual) LAN to put the
station on.
o There have been servers that are inflexible as to the
list of configuration parameters they were able to
serve. If your client requires certain parameters, you
could find such a server unusable.
o I hate to cast wide suspicions, but I've heard
occasional word on client DHCP implementations that do
not implement the entire protocol. Doing so requires
that the software module be able to wake up again after
a specified period of time and "renew the lease", i.e.,
ask to continue using the IP number. This is at least
one feature of DHCP that is very hard to implement in
some simpler systems.
> o The knowledge that a particular IP number is associated
with a particular node is often used for various
functions. Examples are: for security purposes, for
network management, and even for identifying resources.
Furthermore, if the DNS's names are going to identify IP
numbers, the numbers, the IP numbers have to be stable.
Dynamic configuration of the IP numbers undercuts such
methods. For this reason, some sites try to keep the
continued use of dynamically allocatable IP numbers to a
minimum.
o There are a number of issues regarding the patched bootp
servers. These have been reported to re DD2.4.3:
# 'When run from inetd, I had problems with "Could
not bind port" and DHCP request failure. I don't
know why, and the problem went away when bootpd is
run as a daemon.'
# 'Unless you set "dl" to some value in the bootptab
file, the DHCP lease time, renewal time and
prebinding time will be rubbish, which will cause
occasional renewal problems.'
2. Info on Implementations
1. What freeware DHCP servers are available?
(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 static allocation of IP addresses)
http://www.sghms.ac.uk/~mpreston/bootp_dhcp.tar.Z
(within http://www.sghms.ac.uk/~mpreston/tools.htm")
950630 WIDE Project:
Akihiro Tominaga (to...@sfc.wide.ad.jp)
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.
950706 "samba" DHCP patches for bootp server:
(does static 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
2. What commercial DHCP servers are available?
(This is not necessarily a complete list)
950425 Silicon Graphics
950613 NetWare/IP 2.1 will NOT support DHCP but support for enhanced
bootp will be provided. I'm guessing this means DHCP-format
packets, but no address leasing.
950713 James Drews (dr...@engr.wisc.edu)
of U Wisconsin is working on an NLM which he plans to sell
ommercially.
950714 FTP Software (Services OnNet Product)
http://www.ftp.com/mkt_info/services.html
950714 Sun (SolarNet)
ttp://www.sun.com/cgi-bin/show?sunsoft/Products/Networking-products/pro
ducts/pcadmin.html
950714 Microsoft Windows NT
http://www.microsoft.com/NTServer/
http://www.microsoft.com/BackOffice/techbriefs/tech1000.htm
950714 Hewlett Packard HP-UX
950714 TGV: next major release of Multinet for VMS
950802 Process Software: server for OpenVMS
http://www.process.com/
950814 Competitive Automation(415-321-4006): SunOS4.x, Solaris2.x and
DECOSF3.x,4.x servers
3. Which vendors of client software currently support DHCP?
(This is not necessarily a complete list)
950417 Shiva: proxy client for remote users (in Lanrovers and Netmodems)
950419 Dirk Koeppen EDV-Beratungs-GmbH: TCP/IP DHCP Boot ROMs (TCP/IP
BOOT-PROM)
>950421 Microsoft: Windows for Workgroups
950425 Sun
950425 Silicon Graphics
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
in...@frontiertech.com
950712 Beame & Whiteside(800-720-7151): BW-Connect NFS for DOS & Windows
950726 TGV: next release of Multinet for Windows (beyond V3.3)
950725 IBM: a future release of AIX
950728 Sun: PCNFS for Windows
950801 FTP Software: for DOS and Windows (included in PC/TCP OnNet and
PC/TCP networking software; note: the DOS client utilizes DHCP
queries/responses to get an IP address, but does not track its
lease and renew when it should; however, the Windows client is
true DHCP. FTP has stated that the DHCP client the upcoming
OnNet 2.0 and PC/TCP 4.0 releases will perform lease renewal
properly).
http://www.ftp.com/
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
4. What are the DHCP plans of major client-software vendors?
Apple MacTCP
MacTCP's successor, Open Transport, supports DHCP.
As of 7/5/95, Open Trasnport is included with the
Macintosh 9500. Version 1.1 of Open Transport will
ship as a separate product very soon (8/95 is a
good guess).
Microsoft Windows95
will support it and will not support BOOTP.
Novell LAN Workplace for DOS
has plans for client support later in 1995.
IBM OS/2
will support it; I have no news on when or what
version.
5. What Routers forward DHCP requests?
(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).
Cisco
(from Cisco FAQ) Routers running GSYS version
9.21(4) and 10.0(3) as well as later releases.
Wellfleet/Bay
(from Wellfleet FAQ) DHCP is supported by enabling
BOOTP support (with transmission and/or reception
as needed).
3Com Netbuilder
Version 7.2 software can support DHCP relaying
through the use of its generic UDP Helper service.
Version 8.0 and later officially supports DHCP.
Xyplex
Word is that release 5.1 slated for first quarter
1996 will support it.
6. Which implementations support or require the broadcast flag?
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.
o Clients
Microsoft Windows NT
DHCP client support added with version 3.5
sets the broadcast flag. Version 3.51 and
later no longer set it. The exception is in
the remote access support: it sets the flag
when it uses DHCP to acquire addresses to
> hand out to its PPP clients.
tcp/ip-32 for Microsoft Windows for Workgroups (WFW)
Version 3.11a sets it, but version 3.11B
doesn't.
Microsoft Windows 95
Does not set the broadcast flag.
--
Martin Giguere | Un*x: Linux, Solaris
WEBMASTER, EDS Canada | OS: Win95, Dos
mzg...@can.eds.com | This message contains my opinion only...
fax: +1(905)644-7509 | My employer canot be hold resposible for it.