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
Pipeline User’s Guide Preliminary January 30, 1998 3-25
The translation table entries are reused as long as packets are seen that match an
entry. All are freed (expired) when a connection disconnects. For Nailed
connections, the connection is designed not to disconnect.
Multiple-address NAT
Multiple-address NAT can be performed when translating addresses for more
than one host on the local network. To do this, the Pipeline borrows an official IP
address for each host from a Dynamic Host Configuration Protocol (DHCP)
server on the remote network or accessible from the remote network.
The advantages of multiple-address NAT are that hosts on the remote network
can connect to specific hosts on the local network, not just specific services such
as Web or FTP service, but only if the DHCP server is configured to assign the
same address whenever a particular local host requests an address. Also, network
service providers might require multiple-address NAT for networks with more
than one host.
When you use multiple-address NAT, hosts on the remote network can connect to
any of the official IP addresses that the Pipeline borrows from the DHCP server.
If the local network must have more than one IP address that is visible to the
remote network, you must use multiple-address NAT. If hosts on the remote
network need to connect to a specific host on the local network, you can
configure the DHCP server to always assign the same address when that local
host requests an address.
When multiple-address NAT is enabled, the Pipeline attempts to perform IP
address translation on all packets received. (It cannot distinguish between official
and private addresses.)
The Pipeline acts as a DHCP client on behalf of all hosts on the LAN and relies
on a DHCP server to provide addresses suitable for the remote network from its
IP address pool. On the local network, the Pipeline and the hosts all have “local”
addresses on the same network that are only used for local communication
between the hosts and the Pipeline over the Ethernet.
When the first host on the LAN requests access to the remote network, the
Pipeline gets this address through PPP negotiation. When subsequent hosts
request access to the remote network, the Pipeline asks for an IP address from the
DHCP server using a DHCP request packet. The server then sends an address to