ibm-information-center/dist/eclipse/plugins/i5OS.ic.cl_5.4.0.1/addtcpptp.htm

603 lines
27 KiB
HTML
Raw Permalink Normal View History

2024-04-02 14:02:31 +00:00
<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head><META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Add Point-to-Point Profile (ADDTCPPTP)</title>
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body bgcolor="white">
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<a name="ADDTCPPTP.Top_Of_Page"></a>
<h2>Add Point-to-Point Profile (ADDTCPPTP)</h2>
<table width="100%">
<tr>
<td valign="top" align="left"><b>Where allowed to run: </b>All environments (*ALL)<br>
<b>Threadsafe: </b>No
</td>
<td valign="top" align="right">
<a href="#ADDTCPPTP.PARAMETERS.TABLE">Parameters</a><br>
<a href="#ADDTCPPTP.COMMAND.EXAMPLES">Examples</a><br>
<a href="#ADDTCPPTP.ERROR.MESSAGES">Error messages</a></td>
</tr>
</table>
<div> <a name="ADDTCPPTP"></a>
<p>The Add Point-to-Point TCP/IP Profile (ADDTCPPTP) command is used to create a simple PPP (point-to-point protocol) connection profile. Profiles can be created to answer incoming calls by specifying OPRMODE(*ANS), or to dial remote systems by specifying OPRMODE(*DIAL).
</p>
<p>
<b>Note: </b>The preferred method of creating point-to-point profiles is through iSeries Navigator, since it supports all features of PPP. In cases where it is not feasible to create a point-to-point profile using iSeries Navigator, the ADDTCPPTP command can be used to create a simple point-to-point profile.
</p>
<p><b>Restrictions:</b>
</p>
<ul>
<li>You must have input/output system configuration (*IOSYSCFG) special authority to run this command.
</li>
</ul>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div>
<h3><a name="ADDTCPPTP.PARAMETERS.TABLE">Parameters</a></h3>
<table border="1" cellpadding="4" cellspacing="0">
<!-- col1="10" col2="15" col3="30" col4="10" -->
<tr>
<th bgcolor="aqua" valign="bottom" align="left">Keyword</th>
<th bgcolor="aqua" valign="bottom" align="left">Description</th>
<th bgcolor="aqua" valign="bottom" align="left">Choices</th>
<th bgcolor="aqua" valign="bottom" align="left">Notes</th>
</tr>
<tr>
<td valign="top"><a href="#ADDTCPPTP.CFGPRF"><b>CFGPRF</b></a></td>
<td valign="top">Configuration profile</td>
<td valign="top"><i>Character value</i></td>
<td valign="top">Required, Positional 1</td>
</tr>
<tr>
<td valign="top"><a href="#ADDTCPPTP.OPRMODE"><b>OPRMODE</b></a></td>
<td valign="top">Operating mode</td>
<td valign="top">*ANS, *DIAL</td>
<td valign="top">Required, Positional 2</td>
</tr>
<tr>
<td valign="top"><a href="#ADDTCPPTP.RSRCNAME"><b>RSRCNAME</b></a></td>
<td valign="top">Resource name</td>
<td valign="top"><i>Name</i>, <b><u>*CALC</u></b></td>
<td valign="top">Optional, Positional 3</td>
</tr>
<tr>
<td valign="top"><a href="#ADDTCPPTP.MODEM"><b>MODEM</b></a></td>
<td valign="top">Modem</td>
<td valign="top"><i>Character value</i>, <b><u>*RSRCNAME</u></b>, *SELECT</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#ADDTCPPTP.CALLNBR"><b>CALLNBR</b></a></td>
<td valign="top">Calling number</td>
<td valign="top"><i>Character value</i>, <b><u>*NONE</u></b></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#ADDTCPPTP.LCLINTNETA"><b>LCLINTNETA</b></a></td>
<td valign="top">Local internet address</td>
<td valign="top"><i>Character value</i>, <b><u>*OPRMODE</u></b>, *CURRENT, *DYNAMIC</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#ADDTCPPTP.RMTINTNETA"><b>RMTINTNETA</b></a></td>
<td valign="top">Remote internet address</td>
<td valign="top"><i>Character value</i>, <b><u>*OPRMODE</u></b>, *DYNAMIC</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#ADDTCPPTP.ENBPPPAUT"><b>ENBPPPAUT</b></a></td>
<td valign="top">Enable PPP authentication</td>
<td valign="top"><b><u>*NO</u></b>, *YES</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top" rowspan="6"><a href="#ADDTCPPTP.PPPAUT"><b>PPPAUT</b></a></td>
<td valign="top">PPP authentication</td>
<td valign="top"><i>Element list</i></td>
<td valign="top" rowspan="6">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: User name and password</td>
<td valign="top">
Values (up to 10 repetitions): <i>Element list</i></td>
</tr>
<tr>
<td valign="top" style="padding-left:10pt">Element 1: User name</td>
<td valign="top">
<i>Character value</i></td>
</tr>
<tr>
<td valign="top" style="padding-left:10pt">Element 2: User password</td>
<td valign="top">
<i>Character value</i></td>
</tr>
<tr>
<td valign="top">Element 2: Authentication protocol</td>
<td valign="top">
<b><u>*ENCRYPTED</u></b>, *UNENCRYPTED</td>
</tr>
<tr>
<td valign="top">Element 3: Validation list</td>
<td valign="top">
<i>Name</i>, <b><u>*CFGPRF</u></b></td>
</tr>
<tr>
<td valign="top"><a href="#ADDTCPPTP.INACTTMR"><b>INACTTMR</b></a></td>
<td valign="top">Inactivity timer</td>
<td valign="top">15-65535, <b><u>*NOMAX</u></b></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#ADDTCPPTP.TEXT"><b>TEXT</b></a></td>
<td valign="top">Text 'description'</td>
<td valign="top"><i>Character value</i>, <b><u>*BLANK</u></b></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#ADDTCPPTP.FULLMASQ"><b>FULLMASQ</b></a></td>
<td valign="top">Full masquerading</td>
<td valign="top"><b><u>*NO</u></b>, *YES</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#ADDTCPPTP.IPDTGFWD"><b>IPDTGFWD</b></a></td>
<td valign="top">IP datagram forwarding</td>
<td valign="top"><b><u>*NO</u></b>, *YES</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#ADDTCPPTP.ALWRMTOVR"><b>ALWRMTOVR</b></a></td>
<td valign="top">Allow remote address override</td>
<td valign="top"><b><u>*NO</u></b>, *YES</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#ADDTCPPTP.ADDDFTRTE"><b>ADDDFTRTE</b></a></td>
<td valign="top">Add default route</td>
<td valign="top"><b><u>*NO</u></b>, *YES</td>
<td valign="top">Optional</td>
</tr>
</table>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
</div>
<div> <a name="ADDTCPPTP.CFGPRF"></a>
<h3>Configuration profile (CFGPRF)</h3>
<p>Specifies the point-to-point configuration profile to be added.
</p>
<p>This is a required parameter.
</p>
<dl>
<dt><b><i>character-value</i></b></dt>
<dd>Specify the name of a point-to-point configuration profile to add.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDTCPPTP.OPRMODE"></a>
<h3>Operating mode (OPRMODE)</h3>
<p>Specifies the mode of operation for this point-to-point connection profile.
</p>
<p>This is a required parameter.
</p>
<dl>
<dt><b>*ANS</b></dt>
<dd>The profile is defined to answer calls from a remote system.
</dd>
<dt><b>*DIAL</b></dt>
<dd>The profile is defined to dial a remote system.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDTCPPTP.RSRCNAME"></a>
<h3>Resource name (RSRCNAME)</h3>
<p>Specifies the communications hardware resource to be used by this profile.
</p>
<dl>
<dt><b><u>*CALC</u></b></dt>
<dd>The resource name will be determined as follows:
<ul>
<li>Look for resources being used by the 2771 integrated modem. If only one 2771 is defined, use that resource for this PPP line. *CALC is not valid if more than one 2771 modem is defined.
</li>
<li>If a 2771 cannot be used, determine if any resources are defined for use by ECS (Electronic Customer Support). If an ECS resource is available, use that resource for this PPP line.
</li>
<li>If neither a single 2771 integrated modem or ECS resource is available, the resource cannot be calculated and it will have to be explicitly defined.
</li>
</ul>
</dd>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of the hardware resource.
<p>
<b>Note: </b>You can use the Work With Hardware Resources (WRKHDWRSC) command with *CMN specified for the TYPE parameter to help determine the resource name.
</p>
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDTCPPTP.MODEM"></a>
<h3>Modem (MODEM)</h3>
<p>Specifies the modem description to use for this point-to-point profile. The list of currently supported modem descriptions can be seen by using the *SELECT value in interactive mode or by using option 11 from the CFGTCPPTP (Configure TCP/IP point-to-point) command.
</p>
<dl>
<dt><b><u>*RSRCNAME</u></b></dt>
<dd>The modem name will be determined based on the value defined for the RSRCNAME parameter.
<ul>
<li>If the resource is defined to use the 2771 integrated modem, the '2771 Internal Modem' description will be used.
</li>
<li>If the resource is defined to use the 2772 integrated modem, the '2772 Internal Modem' description will be used.
</li>
<li>If the resource is defined to use the 2761 internal modem, the '2761 Internal Modem' description will be used.
</li>
<li>If the ECS resource was chosen, the 'IBM 7852-400' modem description will be used.
</li>
<li>Otherwise, if the resource does not have a pre-defined modem description, MODEM(*RSRCNAME) cannot be used and the modem description will have to be explicitly defined.
</li>
</ul>
</dd>
<dt><b>*SELECT</b></dt>
<dd>A list of modems is shown from which you will select the modem to use. This option is only valid when running the ADDTCPPTP CL command in interactive mode, otherwise an error will occur. If you are running interactively, it is recommended that you use the *SELECT value to help ensure that you properly select the modem to use.
</dd>
<dt><b><i>character-value</i></b></dt>
<dd>Specify the name of the modem to use. Note that modem names are case sensitive and must match exactly to the modems defined for the system.
<p>You can also specify a generic name of the modem you wish to use. A generic modem name is a character string of one or more characters followed by an asterisk (*); for example, 'abc*'. If a generic name is specified, then the <b>first</b> modem name that matches the generic name will be used. It is recommended that you include as many characters in the modem name string as possible to avoid any ambiguity. If an asterisk is not included with the generic (prefix) name, the system assumes it to be the complete modem name. The actual modem name chosen will be posted in a message in the job log.
</p>
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDTCPPTP.CALLNBR"></a>
<h3>Calling number (CALLNBR)</h3>
<p>Specifies the telephone number of the remote system to call. This parameter is only used when OPRMODE(*DIAL) is defined.
</p>
<dl>
<dt><b><u>*NONE</u></b></dt>
<dd>No telephone number is defined. If OPRMODE(*DIAL) is specified, a value other then *NONE must be defined for this parameter.
</dd>
<dt><b><i>character-value</i></b></dt>
<dd>Specify the telephone number to call to connect to the remote system. If additional numbers are required to establish an outside call, they must also be specified. Special character ',' (comma) may be used to signify if a delay is required before dialing the next number. Typically this delay is one second for most modems.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDTCPPTP.LCLINTNETA"></a>
<h3>Local internet address (LCLINTNETA)</h3>
<p>Specifies the local internet address of the system to be used for this PPP connection.
</p>
<dl>
<dt><b><u>*OPRMODE</u></b></dt>
<dd>The mode of operation will determine the local IP address. If OPRMODE(*DIAL) is specified, the local IP address will be defined as *DYNAMIC. If OPRMODE(*ANS) is specified, the local IP address will defined as *CURRENT.
</dd>
<dt><b>*DYNAMIC</b></dt>
<dd>The IP address will be defined by the remote system during PPP negotiations.
</dd>
<dt><b>*CURRENT</b></dt>
<dd>The current local IP address will be used. This address is determined as follows:
<ul>
<li>If a local host name has been defined using the Change TCP/IP Domain (CHGTCPDMN) command, this host name will be resolved to an IP address (either defined in the local host table or by a domain name server). If this IP address is found to also exist on the local system, it will be used.
</li>
<li>If no local host name is defined, or could not be resolved to, the first valid local IP address found will be used.
</li>
<li>If no valid local IP addresses are found, *CURRENT will not be allowed.
</li>
</ul>
</dd>
<dt><b><i>character-value</i></b></dt>
<dd>Specify the internet address to use as the local IP address for this PPP profile. The address specified here can already exist on the system or a unique IP address can be defined.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDTCPPTP.RMTINTNETA"></a>
<h3>Remote internet address (RMTINTNETA)</h3>
<p>Specifies the internet address of the remote system to use for this PPP connection.
</p>
<dl>
<dt><b><u>*OPRMODE</u></b></dt>
<dd>The mode of operation will determine the remote IP address. If OPRMODE(*DIAL) is specified, the remote IP address will be defined as *DYNAMIC. If OPRMODE(*ANS) is specified, the remote IP address will be defined as '169.254.x.x' where 169.254.x.x is a reserved IANA LINKLOCAL network address. The actual host portion (x.x) of this address will be determined at run-time.
</dd>
<dt><b>*DYNAMIC</b></dt>
<dd>The IP address will be defined by the remote system during PPP negotiations.
</dd>
<dt><b><i>character-value</i></b></dt>
<dd>Specify the internet address to use as the remote IP address for this PPP profile. The address specified here <b>must</b> be an unique IP address for this system.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDTCPPTP.ENBPPPAUT"></a>
<h3>Enable PPP authentication (ENBPPPAUT)</h3>
<p>Specifies whether PPP authentication will be enabled for this profile.
</p>
<dl>
<dt><b><u>*NO</u></b></dt>
<dd>No PPP authentication will be required to either connect to the remote system or to allow the remote system to connect to the local system.
</dd>
<dt><b>*YES</b></dt>
<dd>PPP authentication will be required to either connect to the remote system or to allow the remote system to connect to the local system.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDTCPPTP.PPPAUT"></a>
<h3>PPP authentication (PPPAUT)</h3>
<p>Specifies the PPP authentication values to use for PPP authentication. This parameter is only in effect if ENBPPPAUT(*YES) is defined.
</p>
<p><b>Element 1: User name and password</b>
</p>
<p>Specifies the user names and passwords to use for PPP authentication. Only one user name and password can be specified for OPRMODE(*DIAL) profiles. Up to ten user names and passwords can be specified for OPRMODE(*ANS) profiles. Additional entries can be added with iSeries Navigator.
</p>
<dl>
<dt><b></b></dt>
<dd>
<p><b>Element 1: User name</b>
</p>
<dl>
<dt><b><i>character-value</i></b></dt>
<dd>Specify the user name to be used for PPP authentication. Each user name can be up to 64 characters in length. User names are case sensitive and will be stored exactly as they are entered.
</dd>
</dl>
</dd>
<dt><b></b></dt>
<dd>
<p><b>Element 2: User password</b>
</p>
<dl>
<dt><b><i>character-value</i></b></dt>
<dd>Specify the password associated with the user name. Each password can be up to 64 characters in length. Passwords are case sensitive and will be stored exactly as they are entered.
</dd>
</dl>
</dd>
</dl>
<p><b>Element 2: Authentication protocol</b>
</p>
<p>Specifies which authentication protocol to use for PPP authentication. This value also specifies which authentication protocol to associate with each specified user name and password.
</p>
<dl>
<dt><b><u>*ENCRYPTED</u></b></dt>
<dd>Only PPP authentication methods using encrypted passwords will be used. This value will support both EAP (Extended Authentication Protocol) and CHAP (Challenge Authentication Protocol - using MD-5 hashing algorithm).
</dd>
<dt><b>*UNENCRYPTED</b></dt>
<dd>Only PPP authentication methods using unencrypted passwords will be used. Currently this is limited to PAP (Password Authentication Protocol).
<p>
<b>Note: </b>This method of authentication is not as secure as CHAP or EAP since it allows user name and password information to flow over the link unprotected.
</p>
</dd>
</dl>
<p><b>Element 3: Validation list</b>
</p>
<p>Specifies the validation list used to store remote user name and password information for OPRMODE(*ANS) profiles. This element is ignored if OPRMODE(*DIAL) is specified. All validation lists defined for use by PPP must exist in library QUSRSYS.
</p>
<dl>
<dt><b><u>*CFGPRF</u></b></dt>
<dd>The validation list to store user name and password information is the same name as the point-to-point profile. If the validation list does not exist, it will be created in library QUSRSYS.
</dd>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of the validation list in library QUSRSYS to store username and password information. If the validation list does not exist, it will be created.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDTCPPTP.INACTTMR"></a>
<h3>Inactivity timer (INACTTMR)</h3>
<p>Specifies the time (in seconds) that the system waits for user data activity for this profile before disconnecting. This timer is started once LCP (Link Control Protocol) and NCP (Network Control Protocol) negotiations have completed successfully, and restarted when user data is sent or received. LCP and NCP packets do not cause this timer to be restarted.
</p>
<dl>
<dt><b><u>*NOMAX</u></b></dt>
<dd>The inactivity timer is disabled.
</dd>
<dt><b><i>15-65535</i></b></dt>
<dd>Specify the number of seconds to use as the timer value.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDTCPPTP.TEXT"></a>
<h3>Text 'description' (TEXT)</h3>
<p>Specifies the text description for the point-to-point profile.
</p>
<dl>
<dt><b><u>*BLANK</u></b></dt>
<dd>No text is specified.
</dd>
<dt><b><i>character-value</i></b></dt>
<dd>Specify no more than 50 characters of text, enclosed in apostrophes.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDTCPPTP.FULLMASQ"></a>
<h3>Full masquerading (FULLMASQ)</h3>
<p>Specifies whether full masquerading will be used. If enabled, all IP addresses will be hidden behind the remote IP address for the dial PPP connection. This parameter is only in effect if OPRMODE(*DIAL) is specified. This feature allows all outbound IP traffic to have it's source IP address translated to the remote IP address defined for the PPP link. The source port is also modified, so that return IP traffic can be properly associated with the correct conversation and have it's IP address and destination port changed back to the correct values.
</p>
<p>This feature is particularly useful to allow other hosts on the same network as the local system to use the system as a gateway to the internet. If the local system is connected to the internet using an ISP (Internet Service Provider), the other hosts, such as PCs, could also gain access to the internet and 'hide' behind the system's assigned PPP IP address.
</p>
<dl>
<dt><b><u>*NO</u></b></dt>
<dd>No IP addresses will be hidden (masqueraded) behind the system's PPP IP address.
</dd>
<dt><b>*YES</b></dt>
<dd>All IP addresses will be hidden (masqueraded) behind the system's PPP IP address when traffic flows out the PPP link.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDTCPPTP.IPDTGFWD"></a>
<h3>IP datagram forwarding (IPDTGFWD)</h3>
<p>Specifies whether IP datagram forwarding is enabled for this PPP connection. This parameter is only in effect if OPRMODE(*ANS) is specified.
</p>
<dl>
<dt><b><u>*NO</u></b></dt>
<dd>Internet Protocol (IP) will discard those datagrams from the remote system that are not destined for any addresses local to this system.
</dd>
<dt><b>*YES</b></dt>
<dd>This allows Internet Protocol (IP) datagrams not destined for this system to pass through this system onto a connected network. Enabling IP datagram forwarding essentially enables the system to act as router for this connection. Careful security considerations should be reviewed prior to enabling IP forwarding for the PPP link. Note that this will only take effect if system wide IP datagram forwarding is enabled, otherwise it will be ignored even if marked. System-wide IP datagram forwarding is controlled by the IPDTGFWD parameter on the CHGTCPA (Change TCP/IP Attributes) command.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDTCPPTP.ALWRMTOVR"></a>
<h3>Allow remote address override (ALWRMTOVR)</h3>
<p>Specifies whether remote systems will be allowed to override the remote IP address defined in RMTINTNETA. This parameter is only in effect if OPRMODE(*ANS) is specified and RMTINTNETA(*DYNAMIC) is not specified.
</p>
<dl>
<dt><b><u>*NO</u></b></dt>
<dd>If a specific remote IP address is defined for RMTINTNETA, remote systems will not be allowed to define their own address. The remote system must use the address defined by the local system or the PPP connection will be terminated.
</dd>
<dt><b>*YES</b></dt>
<dd>If a specific remote IP address is defined for RMTINTNETA, remote systems will still be allowed to define their own address. This is useful if you want to allow more than one type of remote client to be able to dial into the system. Typically the remote system dialing in will request that it be told what its IP address is. By specifying ALWRMTOVR(*YES), you tell remote clients what their IP address should be, but also allow other remote clients to specify their own address without the need for an additional profile or resource.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="ADDTCPPTP.ADDDFTRTE"></a>
<h3>Add default route (ADDDFTRTE)</h3>
<p>Specifies whether you want a default route added when this Point-to-Point Connection profile is started. This parameter is only in effect if OPRMODE(*DIAL) is specified.
</p>
<dl>
<dt><b><u>*NO</u></b></dt>
<dd>A default route will NOT be automatically added.
</dd>
<dt><b>*YES</b></dt>
<dd>A default route will be automatically added when this Point-to-Point profile is started. The next hop address will be the IP address of the remote system.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="ADDTCPPTP.COMMAND.EXAMPLES">Examples</a> </h3>
<p><b>Example 1: Create an Answer Profile</b>
</p>
<p>
<pre>
ADDTCPPTP CFGPRF(ANSPROFILE) OPRMODE(*ANS)
</pre>
</p>
<p>This command will create answer PPP profile with the following properties
</p>
<ul>
<li>The resource will be calculated and the modem description will be determined by the resource. Assuming a 2771 integrated modem is found then the '2771 Internal modem' modem description will be used.
</li>
<li>Line description 'QPPPCMNxx' will be created, where CMNxx is the 2771 resource.
</li>
<li>An existing IP address on the local system will be defined as the local IP address. If there is an IP address associated with the local host name then this address will be used. If not, then the first local IP address found for the local system will be used.
</li>
<li>The remote IP address (address that is assigned to the remote system) will be defined as 169.254.x.x, where x.x is determined at runtime.
</li>
<li>Authentication is not enabled.
</li>
</ul>
<p><b>Example 2: Create a PPP Dial Profile</b>
</p>
<p>
<pre>
ADDTCPPTP CFGPRF(DIALPROF) OPRMODE(*DIAL) RSRCNAME(CMN14)
MODEM('2761 Internal Modem') CALLNBR('1,,9876543')
ENBPPPAUT(*YES)
PPPAUT(((dialuser dialpw)) *ENCRYPTED *CFGPRF)
FULLMASQ(*YES)
</pre>
</p>
<p>This command will create a dial PPP profile with the following properties:
</p>
<ul>
<li>The profile will use a PPP line named 'QPPPCMN14', defined to use communication resource CMN14.
</li>
<li>The 2761 internal modem will be used (Modem name as seen in CFGTCPPTP, option 11).
</li>
<li>When calling the remote system, a '1' will be dialed first (possibly to reach an outside line), then there will a 2 second delay (approximately), then telephone number '9875432' will be called.
</li>
<li>Authentication is enabled and an authentication protocol using encryption will be used (EAP - extended authentication protocol or CHAP - Challenge authentication protocol (MD-5)). The user name and password defined will be used for authentication.
</li>
<li>The local and remote IP addresses will be defined as *DYNAMIC, which means the addresses will be defined by the remote system during the IPCP (Internet Protocol Control Protocol) negotiation phase of the PPP connection.
</li>
<li>All IP traffic going out the PPP link will appear as if it originated from the local system's PPP IP address.
</li>
</ul>
<p><b>Example 3: Create Profile Using Predefined IP Addresses</b>
</p>
<p>
<pre>
ADDTCPPTP CFGPRF(ANSPROFILE) OPRMODE(*ANS) RSRCNAME(CMN10)
MODEM('USRobotics 56K*') LCLINTNETA('10.9.8.1')
RMTINTNETA('10.9.8.2') ENBPPPAUT(*YES)
PPPAUT(((RmtID1 RmtPW1) (RmtID2 RmtPW2))
*ENCRYPTED PPPVLDL)
TEXT('PPP *ANS profile') IPDTGFWD(*YES)
</pre>
</p>
<p>This command will create an answer PPP profile with the following properties:
</p>
<ul>
<li>The profile will use a PPP line named 'QPPPCMN10', defined to use communication resource CMN10.
</li>
<li>Modem name of 'USRobotics 56K V.90 Sportster' will be used assuming it is the first modem name found starting with the string 'USRobotics 56K'. The actual modem selected will be posted to the joblog in a message.
</li>
<li>Authentication is enabled and an authentication protocol using encryption will be used (EAP - extended authentication protocol or CHAP - Challenge authentication protocol (MD-5)). Both user RmtID1 and RmtID2 are authorized to connect using this profile.
</li>
<li>Validation list PPPVLDL in library QUSRSYS will be used to store the user names and passwords.
</li>
<li>The local IP address will be 10.9.8.1 and the remote IP address will be 10.9.8.2. The 10.9.8.1 local address is an existing IP address on the system and is attached to the 10.9.8.0 network.
</li>
<li>The remote system will be allowed to directly access the 10.9.8.0 network.
</li>
</ul>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="ADDTCPPTP.ERROR.MESSAGES">Error messages</a> </h3>
<p><b><u>*ESCAPE Messages</u></b>
</p>
<dl>
<dt><b>TCP83D0</b></dt>
<dd>Point-to-point profile &amp;1 not added.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#ADDTCPPTP.Top_Of_Page">Top</a></td></tr>
</table>
</body>
</html>