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
2-4 Preliminary January 30, 1998 Pipeline User’s Guide
Subnet mask notation
In the Pipeline, IP addresses are specified in decimal format (not hexadecimal).
For example:
198.5.248.40
If no netmask is specified, the Pipeline assumes a default netmask based on the
“class” of the address:
For example, a class C address such as 198.5.248.40 has 24 network bits, as
shown in Figure 2-2. That leaves 8 bits for the host portion of the address, so up
to 255 hosts can be supported on the class C network.
Figure 2-2. A class C address
To specify a netmask, the Pipeline does not use dotted decimal format, as in:
IP Address=198.5.248.40
Netmask=255.255.255.248
Instead, it includes a netmask modifier that specifies the total number of network
bits in the address. For example:
Table 2-1. IP address classes and default netmasks
Class Address range Network bits
Class A 0.0.0.0
→
127.255.255.255 8
Class B 128.0.0.0
→
191.255.255.255 16
Class C 192.0.0.0
→
223.255.255.255 24
Class D 224.0.0.0
→
239.255.255.255 N/A
Class E (reserved) 240.0.0.0
→
247.255.255.255 N/A