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
Introduction to IP routing on the Pipeline
Pipeline User’s Guide Preliminary January 30, 1998 2-11
numbered, then the unit operates exactly as it does when using unnumbered
routing. Configure interface numbering in the Connection profile.
System behavior with a numbered interface
If a Pipeline is using a numbered interface, the following differences in operation
should be noted, compared to unnumbered (system-based) routing:
• IP packets generated in the Pipeline and sent to the remote address use an IP
source address corresponding to the numbered interface, not to the default
(Ethernet) address of the Pipeline.
• During authentication of a call placed from a Pipeline using a numbered
interface, the Pipeline reports the address of the interface as its IP address.
• The Pipeline adds, as host routes to its routing table, all numbered interfaces
listed in Connection profiles.
• The Pipeline accepts IP packets whose destination are a numbered interface
listed in a Connection profile, considering them to be destined for the
Pipeline itself. (The packet might actually arrive over any interface, and the
numbered interface corresponding to the packet’s destination address need
not be in the active state.)
Configuring interface-based routing
Configure interface-based routing in the IP Options submenu of the Connection
profile. The IF Adrs parameter specifies the IP address of the interface. If you
leave the field at its default value (0.0.0.0/0), the interface is unnumbered.
The profile below shows settings for a numbered interface. The WAN Alias
parameter contains the address of the remote end, and the IF Adrs parameter
contains the interface number of the near end.
Ip options...
LAN Adrs=192.168.6.29/24
WAN Alias=192.1.1.17
IF Adrs=192.1.1.8/30
Metric=0
Preference=2
Private=No
RIP=Off
Pool=0