137 lines
8.4 KiB
HTML
137 lines
8.4 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="reference" />
|
||
|
|
<meta name="DC.Title" content="Example: PPP and DHCP on a single iSeries server" />
|
||
|
|
<meta name="abstract" content="You can learn how to set up the iSeries server as a DHCP server for a LAN and a remote dial-in client." />
|
||
|
|
<meta name="description" content="You can learn how to set up the iSeries server as a DHCP server for a LAN and a remote dial-in client." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiyscenarios.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzakgscenario5" />
|
||
|
|
<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>Example: PPP and DHCP on a single iSeries server</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakgscenario5"><a name="rzakgscenario5"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Example: PPP and DHCP on a single iSeries server</h1>
|
||
|
|
<div><p>You can learn how to set up the iSeries™ server as a DHCP server for a
|
||
|
|
LAN and a remote dial-in client.</p>
|
||
|
|
<div class="section"><p>Remote clients, such as dial-in clients, often require access
|
||
|
|
to a company's network. Dial-in clients can gain access to an iSeries server
|
||
|
|
with PPP. To access the network, the dial-in client will need IP information
|
||
|
|
just like any direct-attached network client. An iSeries DHCP server can distribute IP
|
||
|
|
address information to a PPP dial-in client just like it is any other directly
|
||
|
|
attached client. The following figure shows a remote employee that needs to
|
||
|
|
dial into the company's network to do some work.</p>
|
||
|
|
<div class="fignone"><span class="figcap">Figure 1. PPP and DHCP
|
||
|
|
on a single iSeries server</span><br /><img src="rzakg505.gif" alt="PPP and DHCP on a single iSeries server." /><br /></div>
|
||
|
|
<p>For the remote employee to successfully become part of the company's
|
||
|
|
network, the iSeries server
|
||
|
|
must use a combination of Remote Access Services and DHCP. The Remote Access
|
||
|
|
Services function creates the the dial-in capability for the iSeries server.
|
||
|
|
If set up properly, after the worker establishes the dial-in connection, the
|
||
|
|
PPP server tells the DHCP server to distribute TCP/IP information to the worker.</p>
|
||
|
|
<p>In
|
||
|
|
this example, a single DHCP subnet policy covers both the on-site network
|
||
|
|
clients and the dial-in clients.</p>
|
||
|
|
<p>If you want your PPP profile to defer
|
||
|
|
to the DHCP for IP distribution, you must do so in the PPP profile. In the
|
||
|
|
TCP/IP settings of the receiver connection profile, you must set the Remote
|
||
|
|
IP address assignment method from Fixed to DHCP. To allow the dial-in clients
|
||
|
|
to communicate with other network clients like the LAN printer, you must also
|
||
|
|
allow IP forwarding in the TCP/IP settings of the profile and the TCP/IP configuration
|
||
|
|
(stack) properties. If you only set IP forwarding on in the PPP profile, the iSeries server
|
||
|
|
will not pass the IP packets. You must set IP forwarding on in both the profile
|
||
|
|
and stack.</p>
|
||
|
|
<p>Also, the Local Interface IP address in the PPP profile must
|
||
|
|
be an IP address that falls within the subnet definition in the DHCP server.
|
||
|
|
In this example, the PPP profile Local Interface address should be 10.1.1.1.
|
||
|
|
This address should also be excluded from the DHCP server's address pool so
|
||
|
|
that it is not assigned to a DHCP client.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Planning the DHCP setup for on-site and PPP clients</h4>
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="border" border="1" rules="all"><caption>Table 1. Global configuration options (applies to all clients
|
||
|
|
served by the DHCP server)</caption><thead align="left"><tr><th colspan="2" valign="top" id="d0e63">Object</th>
|
||
|
|
<th valign="top" width="43.624161073825505%" id="d0e65">Value</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td rowspan="3" valign="top" width="12.751677852348994%" headers="d0e63 ">Configuration options</td>
|
||
|
|
<td valign="top" width="43.624161073825505%" headers="d0e63 ">option 1: Subnet mask</td>
|
||
|
|
<td valign="top" width="43.624161073825505%" headers="d0e65 ">255.255.255.0</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="43.624161073825505%" headers="d0e63 ">option 6: Domain name server</td>
|
||
|
|
<td valign="top" width="43.624161073825505%" headers="d0e65 ">10.1.1.1</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="43.624161073825505%" headers="d0e63 ">option 15: Domain name</td>
|
||
|
|
<td valign="top" width="43.624161073825505%" headers="d0e65 ">mycompany.com</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e63 ">Is the server performing DNS updates?</td>
|
||
|
|
<td valign="top" width="43.624161073825505%" headers="d0e65 ">No</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e63 ">Is the server supporting BOOTP clients?</td>
|
||
|
|
<td valign="top" width="43.624161073825505%" headers="d0e65 ">No</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="border" border="1" rules="all"><caption>Table 2. Subnet for both on-site and dial-in clients</caption><thead align="left"><tr><th colspan="2" valign="top" id="d0e104">Object</th>
|
||
|
|
<th valign="top" width="43.91891891891892%" id="d0e106">Value</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td colspan="2" valign="top" headers="d0e104 ">Subnet Name</td>
|
||
|
|
<td valign="top" width="43.91891891891892%" headers="d0e106 ">MainNetwork</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e104 ">Addresses to manage</td>
|
||
|
|
<td valign="top" width="43.91891891891892%" headers="d0e106 ">10.1.1.3 - 10.1.1.150</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e104 ">Lease time</td>
|
||
|
|
<td valign="top" width="43.91891891891892%" headers="d0e106 ">24 hours (default)</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="12.5%" headers="d0e104 ">Configuration options</td>
|
||
|
|
<td valign="top" width="43.58108108108108%" headers="d0e104 ">Inherited options</td>
|
||
|
|
<td valign="top" width="43.91891891891892%" headers="d0e106 ">Options from Global configuration</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="2" valign="top" headers="d0e104 ">Subnet addresses not assigned by server</td>
|
||
|
|
<td valign="top" width="43.91891891891892%" headers="d0e106 ">10.1.1.1 (Local interface address specified in the TCP/IP Settings
|
||
|
|
of the Receiver Connection Profile properties in iSeries Navigator)</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Other setup</h4><ul><li>Set the Remote IP address method to DHCP in the PPP receiver
|
||
|
|
connection profile.<ol><li>Enable DHCP WAN client connection with a DHCP server or relay connection
|
||
|
|
using the Services menu item for Remote Access Services in iSeries Navigator.</li>
|
||
|
|
<li>Select to Use DHCP for the IP address assignment method under the TCP/IP
|
||
|
|
Settings Properties of the Receiver Connection Profile in iSeries Navigator.</li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
<li>Allow remote system to access other networks (IP forwarding) under the
|
||
|
|
TCP/IP Settings Properties of the Receiver Connection Profile in iSeries Navigator.</li>
|
||
|
|
<li>Enable IP datagram forwarding under the Settings Properties of the TCP/IP
|
||
|
|
Configuration in iSeries Navigator.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiyscenarios.htm" title="The scenarios in this topic help you understand how PPP works, and how you can implement a PPP environment in your network. These scenarios introduce fundamental PPP concepts from which beginners and experienced users can benefit before they proceed to the planning and configuration tasks.">Scenarios</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|