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
Setting Up Pipeline Security
Connection security
Pipeline User’s Guide Preliminary January 30, 1998 7-13
When the Pipeline receives a PPP call, it tries to match the caller’s name and
password to a Connection profile. If the Pipeline doesn’t find a matching profile,
it ends the call. If the Pipeline finds a matching profile, it authenticates the call
and establishes the connection.
When an IP routing connection is being authenticated, the IP address is verified
as part of the PPP negotiation before a call is established.
The Ethernet > Answer > PPP options > Route IP parameter must be set to Yes.
If the caller’s PPP software presents an IP address, the Pipeline must find a
Connection profile that matches that address using Ethernet > Connections > any
profile > IP options > LAN Adrs parameter, which must contain a matching IP
address. Otherwise, it ends the call without completing PAP or CHAP
authentication. If it finds a profile, it authenticates the connection, and then
establishes the connection.
Calling-line ID authentication
Calling-line ID (CLID) requires the phone number of the calling device. CLID
authentication ensures that the incoming call originates from a known phone
number. Id Auth in Ethernet > Answer must be set to Yes, and you must set a
value in the Calling # parameter of the matching Connection profile.
When CLID authentication is required, if the calling number is not recognized,
the Pipeline hangs up. CLID authentication occurs first, before any name or
password comparison.
Note:
In some installations, the WAN provider might not be able to deliver
CLID information, or individual callers might choose to block Caller ID. In
addition, CLID is not available without end-to-end ISDN service on the call and
Automatic Number Identification (ANI) from your WAN provider. Ask your
WAN provider whether the calling-party number is conveyed by the network to
the receiving party. In some cases, the network does not deliver the calling-party
number, such as when the Pipeline is behind one or more PBXs.