vRMTGATEWAY is the user ID that is used by the remote gateway to dial in to
LCL400.
From the TCP/IP Settings page, perform the following tasks:
vSet your local IP address. In this example, the existing Ethernet interface
10.1.1.1 is selected from the ″Local IP address″pull-down box.
vSet your remote IP address. In this example, ″Route specified″is selected. This
signifies that remote IP addresses will be defined from entries that are defined
from the Routing dialog.
Note: ″Route specified″is valid only for Switched Line-Answer profiles.
vCheck ″Allow IP forwarding.″IP packets that originate from the remote system
will be allowed to flow through LCL400 to the 10.1.1.0 network.
vClick Routing to add the ″Route specified″IP addresses.
Figure 75 shows the Routing dialog.
The following values hold true for this example of the Routing dialog:
vRMTGATEWAY user ID (from the Remote Gateway)
When user RMTGATEWAYdials in, he or she receives IP address 192.168.2.6. A
subnet mask of 255.255.255.0 was used to allow LCL400 to add a direct route to
the 192.168.2.0 network that is attached to the Remote Gateway.
vRMTOFFICE user ID (from system RMT400)
When user RMTOFFICE dials in, he or she receives IP address 10.2.1.1.A
subnet mask of 255.255.255.0 was used to allow LCL400 to add a direct route to
the 10.2.1.0 network that is attached to RMT400.
A route was defined for RMTOFFICE.The destination network is 10.2.0.0 with a
subnet mask of 255.255.0.0. This route is added when RMTOFFICE dials in and
allows LCL400 to have access to any 10.2.x.x network that is attached to
RMT400. In this scenario, this would include the 10.2.1.0 network, which is also
covered by the direct route that was added for the interface, as well as the
10.2.2.0 network. If any other 10.2.x.x networks are added to RMT400, the
necessary route to reach them is already defined.
Figure 75. Routing
102 OS/400 TCP/IPConfiguration and Reference V4R4