User`s guide
Table Of Contents
- Ascend Customer Service
- How to use this guide
- What you should know
- Documentation conventions
- How to use the on-board software
- Manual set
- Configuring WAN Connections
- Configuring IP Routing
- Introduction to IP routing on the Pipeline
- Managing the routing table
- Parameters that affect the routing table
- Static and dynamic routes
- Configuring static routes
- Specifying default routes on a per-user basis
- Enabling the Pipeline to use dynamic routing
- Route preferences
- Viewing the routing table
- Fields in the routing table
- Removing down routes to a host
- Identifying Temporary routes in the routing table
- Configuring IP routing connections
- Ascend Tunnel Management Protocol (ATMP)
- IP Address Management
- Connecting to a local IP network
- BOOTP Relay
- DHCP services
- Dial-in user DNS server assignments
- Local DNS host address table
- Network Address Translation (NAT) for a LAN
- Configuring IPX Routing
- How the Pipeline performs IPX routing
- Adding the Pipeline to the local IPX network
- Working with the RIP and SAP tables
- Configuring IPX routing connections
- Configuring the Pipeline as a Bridge
- Defining Filters and Firewalls
- Setting Up Pipeline Security
- Pipeline System Administration
- Pipeline 75 Voice Features
- IDSL Implementations
- APP Server utility
- About the APP Server utility
- APP Server installation and setup
- Configuring the Pipeline to use the APP server
- Using App Server with Axent SecureNet
- Creating banner text for the password prompt
- Installing and using the UNIX APP Server
- Installing and using the APP Server utility for DO...
- Installing and using the APP Server utility for Wi...
- Installing APP Server on a Macintosh
- Troubleshooting
- Upgrading system software
- What you need to upgrade system software
- Displaying the software load name
- The upgrade procedure
- Untitled

IP Address Management
Network Address Translation (NAT) for a LAN
3-26 Preliminary January 30, 1998 Pipeline User’s Guide
the Pipeline from its IP address pool. The Pipeline uses the dynamic addresses it
receives from the server to translate IP addresses on behalf of local hosts.
As packets are received on the LAN, the Pipeline determines if the source IP
address has been assigned a translated address. If so, then the packet is translated,
and forwarded to the wide area network. If no translation has been assigned (and
is not pending), then a new DHCP request is issued for this IP address. While
waiting for an IP address to be offered by the server, corresponding source
packets are dropped. Similarly, for packets received from the WAN, the Pipeline
checks the destination address against its table of translated addresses. If the
destination address exists and is active, the Pipeline forwards the packet. If the
destination address does not exit, or is not active, the packet is dropped.
IP addresses are typically offered by the DHCP server only for a limited duration,
but the Pipeline automatically renews the lease on these addresses. If the
connection to the remote server is dropped, all leased addresses are considered
revoked. Therefore, TCP connections do not persist if the WAN call disconnects.
The Pipeline itself does not have an address on the remote network. This means
that the Pipeline can only be accessed from the local network, not from the WAN.
For example, you can Telnet to the Pipeline from the local network, but not from
a remote network.
In some installations, the DHCP server will be handling both NAT DHCP
requests and ordinary DHCP requests. In this situation, if the ordinary DHCP
clients are connecting to the server over a non-bridged connection, you must have
a separate DHCP server to handle the ordinary DHCP requests; the NAT DHCP
server will only handle NAT DHCP requests.
Configuring single or multiple address NAT
To configure NAT on the Pipeline:
1
Open the menu Ethernet > NAT > NAT menu.
For example:
20-A01 NAT...
>Routing=Yes
Profile=NATprofile
Lan=Single IP addr
FR address=0.0.0.0