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-9
routing connection that comes in. In that case, it does not have a route for the
incoming source IP address, and builds a temporary route using an assumed
Class A (8), B (16), or C (24) netmask for the source IP address. If this type of
connection is with a router or a host that does not recognize the initial temporary
route (that is, one from another manufacturer), you might have to turn on RIP or
configure a static route to build a route to that network.
RIP-v2 and RIP-v1 routing
The Pipeline includes a Routing Information Protocol (RIP) version 2
implementation (RIP-v2), which includes a set of improvements to RIP-v1. You
can configure the Pipeline to send, receive, or send and receive RIP-v1 or RIP-v2
on Ethernet or any WAN interface.
Note:
RIP-v2 is a compatible upgrade to RIP-v1, but do not run RIP-v2 and
RIP-v1 on the same network in such a way that the routers receive each other’s
advertisements. RIP-v1 “guesses” subnet masks, while RIP-v2 handles them
explicitly. Running the two versions on the same network can result in RIP-v1
“guesses” overriding accurate subnet information obtained via RIP-v2.
RIP-v2 includes the following improvements to RIP-v1:
Subnet routing The biggest difference between RIP-v1 and RIP-v2 is the
inclusion of subnet mask information in RIP-v2 routes.
RIP-v1 recognized subnet information only within the subnet
and purposely did not advertise subnet masks to other routers.
There was no way to distinguish between a subnet and a host
entry, unless it was for a router directly connected to the
subnet. When a RIP-v1 router receives an IP address, it
assumes the default subnet mask.
RIP-v2 passes the netmask in parallel with the address. This
enables support not only of reliable subnet routing, but also of
variable length masks within the same network as well as
Classless Inter-domain Routing (CIDR).
If a RIP-v1 router receives a RIP-v2 update that includes
netmasks, it ignores the subnet information.