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-13
• A host route is created to the Lan Adrs (interface) address.
• A net route is created to the subnet of the remote interface.
• Incoming PPP/MPP calls must report their IP addresses as the Lan Adrs
(interface) address.
If the remote interface address is not specified
If interface-based routing is in use and the local interface is numbered, the remote
address will usually be known (in practice, the subnet must be agreed upon by
administrators of both sites). It is possible, but not recommended, to number the
local interface, omitting the interface address of the remote site and using only its
system or LAN address. In that case, do not use the (supposedly unknown)
remote interface address in any static routes.
When a local interface is numbered but no corresponding remote interface
address is set, the remote interface must have an address on the same subnet as
the local, numbered interface. Incoming PPP will be rejected if the Connection
Profile numbers the local interface and the (remote) caller supplies an address not
on the same subnet.
Multicast forwarding and IGMP functionality
The Pipeline supports Internet Group Membership Protocol (IGMP) version 1
and version 2, that enable the Pipeline to subscribe as a multicast client. The
Pipeline transparently passes any multicast traffic it receives from a multicast
router to its Ethernet, making these packets available to local hosts on its Ethernet
which have been set up to listen to them. The Pipeline does not operate as an
IGMP router, and does not forward multicast packets to IGMP clients.
To enable multicast forwarding:
1
Open Ethernet > Mod Config > Multicast menu.
2
Set Multicast Forwarding to Yes.
This setting enables multicast forwarding in the Pipeline. The Pipeline then
receives Internet Group Membership Protocol (IGMP) queries from the
router and responds to them using IGMP.
3
Specify the name of a resident profile to be defined as the Multicast Profile.
This profile is used to connect over the WAN to the multicast router in the