User`s guide

IP Address Management
Network Address Translation (NAT) for a LAN
3-30 Preliminary January 30, 1998 Pipeline User’s Guide
4
Set the Lan parameter to Single IP Addr.
5
If you previously configured the Pipeline to route incoming packets for
specific TCP or UDP ports (as described in “Routing incoming sessions for
up to 10 servers on a LAN” on page 3-30).
– Open each Ethernet > NAT > Static Mapping > Static Mapping nn menu
(where nn is a number between 01 and 10).
– Set the Valid parameter in each menu to No.
6
Set the Def Server parameter to the IP address of the server on the local
network to receive all incoming packets from the remote network.
7
Press the Esc key to exit the menu.
8
Save the changes when prompted.
The changes take effect the next time a connection is made for the NAT profile.
To make the changes immediately, close the connection specified by the Profile
parameter and then reopen it.
Routing incoming sessions for up to 10 servers on a LAN
To configure the Pipeline to perform NAT and to define up to 10 servers and
optionally a default server which handle sessions initiated by callers from outside
the private LAN:
1
Open the Ethernet > NAT > NAT menu.
2
Set the Routing parameter to Yes.
3
Set the Profile parameter to the name of an existing Connection profile.
The Pipeline performs NAT whenever a connection is made with this
Connection profile. The connection can be initiated either by the Pipeline or
by the remote network.
4
Set the Lan parameter to Single IP Addr.
5
Open the Ethernet > NAT > NAT > Static Mapping menu.
6
Open a Static Mapping nn menu, where nn is a number between 01 and 10.
You use the parameters in each Static Mapping nn menu to specify routing
for incoming packets sent to a particular TCP or UDP port.