Creating a Point-to-Point Profile for LAN Transparent Subnetting
Access Point-to-Point functions through Operations Navigator.
From the General page, perform the following tasks:
v Specify a profile name (REMOTE_ABC for this example).
v Specify a description for the connection profile (Answer profile For Remote Box
A, B, or C in this example).
v Select PPP as the ″Type.″
v Select Switched line-answer as the ″Mode.″
From the TCP/IP Settings page, perform the following tasks:
v Specify your ″Local IP address.″ Since this example is
Unnumbered Net
,an
existing token-ring interface, 10.5.0.1, is selected from the ″Local IP address″
pull-down box.
v Specify your ″Remote IP address.″ In this example, Route specified is selected.
Remote IP addresses will be defined from the entries that are defined in the
Routing dialog.
Note: Route specified is valid only for switched line-answer profiles.
v Check ″Allow IP forwarding.″ IP packets that originate from the remote LAN are
allowed to flow through AS/400 to the ″Corporate Network″ or other remote
LANs.
Click Routing to add entries to the Route specified IP addresses. From the
Routing page, perform the following tasks:
v For ″Dynamic routing,″ select None. Routing will be carried out through static
routing.
v For ″Static routing,″ select Use static routes:
– Caller REMOTE_A receives IP address 10.5.1.1. A subnet mask of 255.255.255.0
allows AS/400 to add a direct route to the 10.5.1.0 network.
– Caller REMOTE_B receives IP address 10.5.2.1. A subnet mask of 255.255.255.0
allows AS/400 to add a direct route to the 10.5.2.0 network.
– Caller REMOTE_C receives IP address 10.5.3.1. A subnet mask of 255.255.255.0
allows AS/400 to add a direct route to the 10.5.3.0 network.
Note: You can add more routes if additional LANs are attached to AS/400
through subnetting.
Figure 78 on page 107 shows the Routing dialog.
106 OS/400 TCP/IP Configuration and Reference V4R4