69 lines
4.6 KiB
HTML
69 lines
4.6 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="Transparent subnets" />
|
||
|
|
<meta name="abstract" content="You can use transparent subnets as a way to extend the proxy ARP concept." />
|
||
|
|
<meta name="description" content="You can use transparent subnets as a way to extend the proxy ARP concept." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajwproxyarp.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="rzajwtsg" />
|
||
|
|
<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>Transparent subnets</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzajwtsg"><a name="rzajwtsg"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Transparent subnets</h1>
|
||
|
|
<div><p>You can use transparent subnets as a way to extend the proxy
|
||
|
|
ARP concept.</p>
|
||
|
|
<p>Transparent subnets work for a single host so that you can connect to an
|
||
|
|
entire subnet or range of hosts. You can see in the follwing figure that the
|
||
|
|
stub networks (10.1.1.x through 10.1.3.x) are assigned addresses out of the
|
||
|
|
primary network address space (10.1.x.x).</p>
|
||
|
|
<br /><img src="rzajw522.gif" alt="Example of a transparent subnet" /><br /><p>The twinaxial LANs are defined in address ranges that are within the real
|
||
|
|
LAN address range. Prior to V4R2, the edits on the add TCP/IP route and add
|
||
|
|
TCP/IP interface did not allow this to happen. In V4R2 the edits were relaxed.
|
||
|
|
This allows two interfaces in different segments to have addresses that look
|
||
|
|
like they are in the same segment. When the iSeries™ server sees this happen, it automatically
|
||
|
|
performs a proxy ARP for any systems that are attached behind the twinaxial
|
||
|
|
controller. This allows all the systems on the 10.1.x.x network to communicate
|
||
|
|
with all the subnet systems with no changes to the systems on the 10.1.x.x
|
||
|
|
network.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Transparent subnetting over WANs</h4><p>The transparent
|
||
|
|
subnet function can be further expanded to handle real LANs that are remotely
|
||
|
|
located. Transparent subnetting over WANs makes remote networks appear to
|
||
|
|
be connected to the home network. In the preceding figure, three networks
|
||
|
|
are attached to the home 10.1.x.x network through the iSeries server. These networks are all
|
||
|
|
defined using a subnet mask that makes them transparent to the home network.
|
||
|
|
Proxy ARP responds to any ARP request on the home network for systems in the
|
||
|
|
10.1.1.x, 10.1.2.x and 10.1.3.x subnets. This causes the traffic for the home
|
||
|
|
network to be routed automatically to the iSeries server in the home network. This iSeries server
|
||
|
|
in turn routes the data to the correct remote iSeries server. The remote iSeries server
|
||
|
|
either processes the data, or forwards it to the correct system within the
|
||
|
|
remote LAN. The workstations in the remote LAN must have a default route that
|
||
|
|
points to the remote iSeries server in their network as the first hop
|
||
|
|
gateway. The workstations in the home LAN do not need any additional routing
|
||
|
|
entries because no new logical networks are created.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajwproxyarp.htm" title="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.">Proxy Address Resolution Protocol routing</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|