70 lines
4.8 KiB
HTML
70 lines
4.8 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="Proxy Address Resolution Protocol routing" />
|
||
|
|
<meta name="abstract" content="Proxy Address Resolution Protocol (ARP) provides connectivity between physically separate networks without creating any new logical networks and without updating any routing tables. This topic also contains a description of transparent subnets, which is an extension to the proxy ARP routing technique." />
|
||
|
|
<meta name="description" content="Proxy Address Resolution Protocol (ARP) provides connectivity between physically separate networks without creating any new logical networks and without updating any routing tables. This topic also contains a description of transparent subnets, which is an extension to the proxy ARP routing technique." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajwrcb.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajwtsg.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="rzajwproxyarp" />
|
||
|
|
<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>Proxy Address Resolution Protocol routing</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzajwproxyarp"><a name="rzajwproxyarp"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Proxy Address Resolution Protocol routing</h1>
|
||
|
|
<div><p>Proxy Address Resolution Protocol (ARP) provides connectivity between
|
||
|
|
physically separate networks without creating any new logical networks and
|
||
|
|
without updating any routing tables. This topic also contains a description
|
||
|
|
of transparent subnets, which is an extension to the proxy ARP routing technique.</p>
|
||
|
|
<p>ARP routing allows physically distinct, separate networks to appear as
|
||
|
|
if they were a single logical network. It allows systems that are not directly
|
||
|
|
connected to a LAN to appear to other systems on the LAN as though they are
|
||
|
|
connected. This is useful in dial-up scenarios to provide connections to the
|
||
|
|
entire network from a dial-in interface. The following figure shows a possible
|
||
|
|
scenario. The 10.1.1.x is your home LAN and the 10.1.1.65 through 10.1.1.68
|
||
|
|
are your remote systems.</p>
|
||
|
|
<br /><img src="rzajw500.gif" alt="ProxyARP" /><br /><p>When a system on your home LAN (10.1.1.x) wants to send data to one of
|
||
|
|
your remote systems, it will first do an ARP request. This is a broadcast
|
||
|
|
that goes out to all your systems attached to the LAN segment to request the
|
||
|
|
address of the target system. However, a remotely connected system will not
|
||
|
|
see the broadcast. This is where the proxy ARP comes in. The iSeries™ server
|
||
|
|
knows which systems are connected remotely. If your iSeries server sees an ARP request for
|
||
|
|
one of your remotely connected machines, your iSeries server will reply to the ARP
|
||
|
|
request with its address. Your iSeries server in turn receives the data
|
||
|
|
and forwards it to the remote system. For this forwarding to take place, IP
|
||
|
|
forwarding must be set to *yes. If your remote system is not connected, your iSeries server
|
||
|
|
will not reply to the ARP request and the requesting system will not send
|
||
|
|
data.</p>
|
||
|
|
<p>You can use transparent subnets as a proxy for an entire subnet, or range
|
||
|
|
of hosts. Transparent subnetting allows stub networks to be assigned addresses
|
||
|
|
out of the primary network address space.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzajwtsg.htm">Transparent subnets</a></strong><br />
|
||
|
|
You can use transparent subnets as a way to extend the proxy ARP concept.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajwrcb.htm" title="Routing deals with what path the network traffic follows from its source to its destination and how that path is connected.">Routing connectivity methods</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|