73 lines
4.9 KiB
HTML
73 lines
4.9 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="DHCP client support" />
|
||
|
|
<meta name="abstract" content="Using DHCP, you can manage each client in your network individually, rather than managing all of the clients as a large group (subnet)." />
|
||
|
|
<meta name="description" content="Using DHCP, you can manage each client in your network individually, rather than managing all of the clients as a large group (subnet)." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgconceptparent.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgconceptbootp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakgplanningdemands.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzakgconceptsupport" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>DHCP client support</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakgconceptsupport"><a name="rzakgconceptsupport"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">DHCP client support</h1>
|
||
|
|
<div><p>Using DHCP, you can manage each client in your network individually,
|
||
|
|
rather than managing all of the clients as a large group (subnet).</p>
|
||
|
|
<p>This DHCP setup method allows only the clients identified by the DHCP server
|
||
|
|
to receive IP address and configuration information.</p>
|
||
|
|
<p>People often think about using DHCP to distribute IP addresses
|
||
|
|
from an address pool to a subnet of clients. Any client that requests DHCP
|
||
|
|
information from the network might receive an IP address from the address
|
||
|
|
pool when you use subnets, unless they are explicitly excluded by the DHCP
|
||
|
|
administrator. However, the DHCP server is also capable of the inverse --
|
||
|
|
limiting DHCP service to only specific clients.</p>
|
||
|
|
<p>The DHCP server can limit service at both the individual client level and
|
||
|
|
by the type of client (BOOTP or DHCP). To limit service at the individual
|
||
|
|
client level, you must identify each network client individually in your DHCP
|
||
|
|
configuration. Each client is identified by their client ID (typically their
|
||
|
|
MAC address). Only the clients that are identified in the DHCP configuration
|
||
|
|
will be served an IP address and configuration information from the DHCP server.
|
||
|
|
If a client is not listed in the DHCP configuration, it is refused service
|
||
|
|
by the DHCP server. This method prevents unknown hosts from obtaining an IP
|
||
|
|
address and configuration information from the DHCP server.</p>
|
||
|
|
<p>If you want even more control over your network clients and the configuration
|
||
|
|
information that they receive, you can set up your DHCP clients to receive
|
||
|
|
a static IP address rather than receiving an IP address from an address pool.
|
||
|
|
If you set up the client to receive a defined IP address, that client should
|
||
|
|
be the only client that can receive that IP address to avoid address overlap.
|
||
|
|
If you use dynamic IP address allocation, the DHCP server will manage IP address
|
||
|
|
assignment for the clients.</p>
|
||
|
|
<p>On a broader level, the DHCP server can limit service to a client based
|
||
|
|
on the type of client, BOOTP or DHCP. The DHCP server can refuse
|
||
|
|
service to BOOTP clients.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakgconceptparent.htm" title="DHCP interacts with clients and works in a network.">DHCP concepts</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakgconceptbootp.htm" title="This topic describes what BOOTP is, and gives some history about BOOTP and DHCP.">BOOTP</a></div>
|
||
|
|
<div><a href="rzakgplanningdemands.htm" title="You can plan for most of the DHCP setup by looking at your network topology, the devices on the network (for example, routers), and how you want to support your clients in DHCP.">Network topology considerations</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|