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 IPX Routing
How the Pipeline performs IPX routing
4-4 Preliminary January 30, 1998 Pipeline User’s Guide
• IPX Route profiles
• IPX SAP filters
• Dial Query
• Watchdog spoofing
Virtual IPX network for dial-in clients
The Pipeline allows individual NetWare clients that do not have an IPX network
address to use an IPX routing connection to the local network if they are running
PPP client software.
To enable the Pipeline to route to such dial-in clients, you must specify an IPX
network number in the Ethernet profile. The number must be unique within the
entire IPX routing domain of the Pipeline (the local routing domain as well as all
WAN links). It defines a “virtual” IPX network reserved for dial-in clients.
The Connection profile for each dial-in client must specify “Dialin” for the
Pipeline to assign the virtual IPX network number to the dial-in client during PPP
negotiation. If the client does not provide its own unique node number, the
Pipeline assigns a node number as well as the network number. It does not send
RIP and SAP advertisements across the connection, and ignores RIP and SAP
advertisements received from the far end. However, it does respond to RIP and
SAP queries received from dial-in clients.
For more information, see “Defining a virtual IPX network for dial-in clients” on
page 4-15 and “An example dial-in client connection” on page 4-24.
Optimized access for dial-in NetWare clients
Without optimized access, the Pipeline assumes that the far end of an incoming
IPX connection is another IPX router. After answering the call, the Pipeline
recognizes the caller as a client via the Peer=Dialin setting in the caller’s
Connection profile.
The Answer profile also contains a Peer parameter to enable the Pipeline to treat
incoming IPX connections as clients even when configured profiles are not in
use. You must set this for dial-in Windows 95 clients with no configured profile,
because without it, the connection can take more than a minute to establish and
the client cannot see NetWare servers on the local network.