Filter
Top Products
From the TCP/IP Settings page, perform the following tasks:
v Set your local IP address. In this example, the existing Ethernet interface
10.2.1.1 is selected from the ″Local IP address″ pull-down box.
v Set your remote IP address. In this example, ″Dynamically assigned″ is selected.
The remote system, LCL400, defines the address that RMT440 uses when the
connection is established.
The remote address of 10.1.1.1, which is the local Ethernet IP address for
LCL400, could have been defined statically for RMT400. If this address ever
changes, however, you must update the profile. The value ″Dynamically
assigned″ allows it to work for whatever address LCL400 has specified.
v Since you need to define additional routes, click Routing.
Figure 76 shows the Routing dialog.
The following values hold true for this example of the Routing dialog:
v Select ″Use static routes″ Static routing. If RMT400 only ever called LCL400,
then you could have selected ″Add remote system as the default route.″ This
ensures that
all
TCP/IP traffic would go to LCL400 if not otherwise defined. In
this example, however, assume that RMT400 has other point-to-point profiles that
can call other remote systems at the same time. Therefore, we want to define
network routes to the remote networks.
v A route is defined for remote network 10.1.0.0 with a subnet mask of
255.255.0.0. This route is added when the connection is made with LCL400. All
TCP/IP traffic for hosts on the 10.1.x.x network are sent to LCL400. Currently,
this is only 10.1.1.0. If other 10.1.x.x networks are added to LCL400 in the future,
then no further routing will need to be defined to reach hosts on the other
networks.
Example: Remote LAN Access with Transparent Subnetting
Transparent Subnetworking allows remote clients who are on separate LANs to
communicate with one another as if they were on the same physical network. To
accomplish transparent subnetworking from the home network, you must partition
blocks of addresses for each remote site. The subnet and the host are the two
levels of hierarchical addressing. The boundary between them is arbitrary.
Figure 76. Routing
104 OS/400 TCP/IP Configuration and Reference V4R4