49 lines
3.0 KiB
HTML
49 lines
3.0 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 xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
||
|
<head>
|
||
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
<meta name="dc.language" scheme="rfc1766" 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. -->
|
||
|
<meta name="dc.date" scheme="iso8601" content="2005-09-06" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
<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))' />
|
||
|
<title>SOCKS</title>
|
||
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
||
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
||
|
</head>
|
||
|
<body>
|
||
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
||
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
||
|
|
||
|
<a name="socksserver"></a>
|
||
|
<h3 id="socksserver">SOCKS</h3>
|
||
|
<p>A SOCKS server is a TCP/IP proxy server application that allows you to
|
||
|
send information through a wide variety of protocols without providing the
|
||
|
internal TCP/IP network information. To use a SOCKS server, the client must
|
||
|
support the SOCKS protocol.</p>
|
||
|
<p>There are some systems such as i5/OS™ systems that support a SOCKS client in
|
||
|
its TCP/IP stack (versatile clients) so that all client applications can use
|
||
|
a SOCKS server. The client configuration gives the name of the SOCKS server
|
||
|
to use and the rules for when the server should be used.</p>
|
||
|
<p>SOCKS servers have no knowledge of the application protocol that they are
|
||
|
using. These servers, for example, do not distinguish Telnet form HTTP. AS
|
||
|
a result, SOCKS servers can be written in a more efficient manner than other
|
||
|
proxy server applications. The downside is that SOCKS servers can not perform
|
||
|
functions like caching or logging URLs that are accessed through the server.</p>
|
||
|
<p>The Universal Connection does not support data flow through a SOCKS server.
|
||
|
Therefore, if your i5/OS client accesses the network through a SOCKS server,
|
||
|
you must ensure that none of the Universal Connection information is routed to the SOCKS server
|
||
|
by specifying that all of the destinations are DIRECT in your SOCKS configuration.</p>
|
||
|
<p>For more information about SOCKS, see the <a href="../rzab6/csocks.htm">Client SOCKS support</a> topic and <a href="cfgvpnlocate.htm#cfgvpnlocate">Ensure compatibility with SOCKS</a>.</p>
|
||
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
</body>
|
||
|
</html>
|