User`s guide

IP Address Management
Network Address Translation (NAT) for a LAN
Pipeline User’s Guide Preliminary January 30, 1998 3-29
Configuring NAT port routing (Static Mapping submenu)
The Static Mappings menu includes 10 Static Mapping nn submenus, where nn is
a value from 01 to 10. Each of these submenus contains parameters for
controlling the translation of a private IP address and port number to a TCP or
UDP port number. Static Mappings applies only to single-address NAT. You only
need to specify static mappings for connections initiated by devices calling into
the private LAN.
You can configure a NAT port routing
• to define a default server on the local private LAN
The Pipeline routes incoming packets to the default server when their
destination port number does not match an entry in Static Mappings nor does
it match a port number dynamically assigned when a local host initiates a
TCP / UDP session.
• to define a list of up to 10 servers & services on the local private LAN
The Pipeline routes incoming packets to hosts on the local private LAN
when their destination port matches one of the 10 destination ports in Static
Mappings.
Note:
You need to configure port routing only for sessions initiated by hosts
outside the private LAN. For sessions initiated by hosts on the private LAN, the
Pipeline generates the port mapping dynamically.
For port routing in single-address NAT to work, if firewalls are present, they must
be configured to allow the Pipeline to receive packets for the routed ports.
Routing all incoming sessions to the default server
To configure the Pipeline to perform NAT and to define a single server which
handles all 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.