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 the Pipeline as a Bridge
Managing the bridge table
Pipeline User’s Guide Preliminary January 30, 1998 5-7
Managing the bridge table
To forward bridged packets to the right network destination, the Pipeline uses a
bridge table that associates end nodes with particular connections. It builds this
table dynamically, as described in “Transparent bridging” on page 5-7. It also
incorporates the entries found in its Bridge profiles. Bridge profiles are analogous
to static routes in a routing environment. You can define up to eight destination
nodes and their connection information in Bridge profiles.
Parameters that affect the bridge table
Parameters directly related to the bridge table are set in the following menus:
Ethernet
Mod Config
Ether options...
Bridging=Yes
Ethernet
Connections
profile
Bridge=Yes
Dial Brdcast=No
Ethernet
Bridge Adrs
Enet Adrs=CFD-12367
Net Adrs=10.0.0.12
Connection #=7
For details on each parameter, see the Reference Guide.
Transparent bridging
As a transparent (or learning) bridge, the Pipeline keeps track of where addresses
are located as it forwards packets. It records each packet’s source address in a
bridging table. A Connection profile is associated with an address when it is used
to dial the link or when it matches an incoming call.