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
Connecting to a local IP network
3-6 Preliminary January 30, 1998 Pipeline User’s Guide
Using Ping to verify the address
The Ping command sends an Internet Control Message Protocol (ICMP)
mandatory echo request datagram, which asks the remote station “Are you
there?” If the echo request reaches the remote station, the station sends back an
ICMP echo response datagram, which tells the sender, “Yes, I am alive.” This
exchange verifies that the transmission path is open between the Pipeline and
another station.
To verify that the Pipeline is up on the local network, invoke the terminal server
interface and enter this command:
ping <host-name>
For example:
ping 10.1.2.3
You can terminate the Ping exchange at any time by pressing Ctrl-C. (For more
information about verifying that a device is on the network, see Chapter 8,
“Pipeline System Administration.”)
Enabling proxy mode in the Pipeline
When a dial-in host has an IP address on the same network as the Pipeline, only
the Pipeline keeps track that packets addressed to the host must be routed across
the WAN. To other local routers and hosts, the address appears to be on the local
network. Therefore, they might broadcast Address Resolution Protocol (ARP)
requests on the local network expecting the apparently local host to respond with
its physical address. Because the host is not really local, it cannot receive the
requests. But if the Pipeline is in Proxy Mode, serving as a proxy for the remote
host, it responds with its own physical address.
To enable the Pipeline to respond to ARP requests for remote devices that have
local IP addresses:
1
Open the Ethernet > Mod Config > Ether Options menu.
2
Turn on Proxy Mode.
If the IP addresses are assigned dynamically, use this setting:
Proxy Mode=Active