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

Configuring IP Routing
Managing the routing table
Pipeline User’s Guide Preliminary January 30, 1998 2-19
Private=No
This setting specifies that the Pipeline will disclose the existence of the route
when queried by RIP or another routing protocol.
8
Close and save the profile.
Configuring the default route
If no routes exist for the destination address of a packet, the Pipeline forwards the
packet to the default route. Most sites use the default route to specify a local IP
router (such as a UNIX host running the route daemon). This helps to offload
routing tasks to other devices.
Note:
If there is no default route, the Pipeline drops packets for which it has no
route. By default, the Pipeline uses the value you entered for the Rem Adr
parameter in the Configure profile as the default gateway.
To configure the default route:
1
Open the Ethernet > Static Rtes > Default profile.
The name of that profile is always Default, and its destination is always
0.0.0.0 (you cannot change these values).
2
Specify that the route should be added to the routing table.
Active=Yes
3
Specify the address of the router to use for packets with unknown
destinations.
For example:
Gateway=10.9.8.10
4
Specify a metric for this route.
For example:
Metric=1
5
Specify whether this route is private.
For example:
Private=Yes
This setting specifies that the Pipeline will not disclose the existence of the
route when queried by RIP or another routing protocol.
6
Close and save the Default profile.