ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzamv_5.4.0.1/rzamvtcpslip.htm

84 lines
5.4 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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="Security considerations for using SLIP" />
<meta name="abstract" content="TCP/IP support includes Serial Interface Line Protocol (SLIP)." />
<meta name="description" content="TCP/IP support includes Serial Interface Line Protocol (SLIP)." />
<meta name="DC.Relation" scheme="URI" content="rzamvtcpsetupsecurity.htm" />
<meta name="DC.Relation" scheme="URI" content="rzamvtcpdialin.htm" />
<meta name="DC.Relation" scheme="URI" content="rzamvtcppreventdialin.htm" />
<meta name="DC.Relation" scheme="URI" content="rzamvtcpdialout.htm" />
<meta name="DC.Relation" scheme="URI" content="rzamvtcpsecdialout.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="tcpslip" />
<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>Security considerations for using SLIP</title>
</head>
<body id="tcpslip"><a name="tcpslip"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Security considerations for using SLIP</h1>
<div><p>TCP/IP support includes Serial Interface Line Protocol (SLIP). </p>
<p>SLIP provides low-cost point-to-point connectivity. A SLIP user can connect
to a LAN or a WAN by establishing a point-to-point connection with a system
that is part of the LAN or WAN. SLIP runs on an asynchronous connection. You
can use SLIP for dial-up connection to and from iSeries™ servers. </p>
<p>For example, you might use SLIP to dial in from your PC to an iSeries system.
After the connection is established, you can use the TELNET application on
your PC to connect to the iSeries TELNET server. Or, you can use the FTP application
to transfer files between the two systems. </p>
<p>No SLIP configuration exists on your system when it ships. Therefore, if
you do not want SLIP (and dial-up TCP/IP) to run on your system, do not configure
any configuration profiles for SLIP. You use the Work with TCP/IP Point-to-Point
(WRKTCPPTP) command to create SLIP configurations. You must have *IOSYSCFG
special authority to use the WRKTCPPTP command.</p>
<div class="p">If you want SLIP to run on your system, you create one or more SLIP (point-to-point)
configuration profiles. You can create configuration profiles with the following
operating modes:<ul><li>Dial in (*ANS)</li>
<li>Dial out (*DIAL)</li>
</ul>
<div class="note"><span class="notetitle">Note:</span> A user profile is system object that allows signon. Every system
job must have a user profile to run. A configuration profile stores information
that is used to establish a SLIP connection with an iSeries system. When you start a SLIP
connection to iSeries servers,
you are simply establishing a link. You have not yet signed on and started
an iSeries server
job. Therefore, you do not necessarily need a user profile to start a SLIP
connection to iSeries servers.
However, as you will see in the discussions that follow, the SLIP configuration
profile may require a user profile to determine whether to allow the connection.</div>
</div>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rzamvtcpdialin.htm">Secure dial-in SLIP connections</a></strong><br />
Before someone can establish a dial-in connection to your system with SLIP, you must start a SLIP *ANS configuration profile.</li>
<li class="ulchildlink"><strong><a href="rzamvtcppreventdialin.htm">Prevent dial-in users from accessing other systems</a></strong><br />
Depending on your system and network configuration, a user who starts a SLIP connection might be able to access another system in your network without signing on to your system.</li>
<li class="ulchildlink"><strong><a href="rzamvtcpdialout.htm">Control dial-out sessions</a></strong><br />
Before someone can use SLIP to establish a dial-out connection from your system, you must start a SLIP *DIAL configuration profile.</li>
<li class="ulchildlink"><strong><a href="rzamvtcpsecdialout.htm">Secure dial-out sessions</a></strong><br />
Users on your iSeries system might want to establish dial-out connections
to systems that require user validation.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzamvtcpsetupsecurity.htm" title="The following information guides you through the process of setting up TCP/IP security.">Set up TCP/IP security</a></div>
</div>
</div>
</body>
</html>