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-7
The “0” address for this subnet is 192.168.8.64.The broadcast address must be
the network base address plus six ones (six ones in base 2 equals 63 decimal, and
64+63=127) 192.168.8.127.
Note:
Early implementations of TCP/IP did not allow zero subnets. That is,
subnets could have the same base address that a class A, B, or C network would
have. For example, the subnet 192.168.8.0/30 was illegal because it had the same
base address as the class C network 192.168.8.0/24, while 192.168.8.4/30 was
legal. (192.168.8.0/30 is called a zero subnet, because like a class C base address,
its last octet is zero.) Modern implementations of TCP/IP allow subnets to have
base addresses that might be identical to the class A, B, or C base addresses.
Ascend's implementations of RIP 2 treats these so-called zero subnetworks the
same as any other network. However, it is important that you treat zero subnets
consistently throughout your network. Otherwise, you will encounter routing
problems.
IP routing in the Answer profile
Before the Pipeline answers an incoming call, it checks the settings in its Answer
profile for information about what to do. If the call does not include the
information required by the Answer profile, the Pipeline hangs up.
The parameters listed below are related to IP routing in the Answer profile. (For
detailed information about each parameter, see the Reference Guide. You might
also want to refer to other sections in this guide, including, “Configuring RIP for
incoming WAN connections” on page 2-22, for setting the RIP parameter in the
Answer profile, and for authentication, Chapter 7, “Setting Up Pipeline
Security.”)
• Ethernet > Answer > Session Options
RIP=Off
•Ethernet
>
Answer
>
PPP Options
Route IP=Yes
Recv Auth=Either
To enable the Pipeline to answer incoming IP routing calls:
1
Open the Ethernet > Answer > PPP Options menu.
2
Turn on IP Routing.