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
Configuring bridged connections
Pipeline User’s Guide Preliminary January 30, 1998 5-9
broadcast requests. Instead, it relies on its bridging table to recognize which
Connection profile to use.
Note:
If you turn off Dial Brdcast and the Pipeline does not have a bridge-table
entry for a destination address, the Pipeline will not bring up that connection.
To define a static bridge-table entry:
1
Open a Bridge profile.
2
Specify the physical address of the remote host.
For example:
Enet Adrs=0080AD12CF9B
Get this address from the administrator of the far-end device. For more
information, see “Physical addresses and the bridge table” on page 5-2.
3
If the far-end is a segment of the local IP network, specify an address on that
segment. For example:
Net Adrs=10.2.3.133
For more details, see “An example IP bridged connection” on page 5-16.
4
Specify the number of the Connection profile for this connection.
For example:
Connection #=2
You don’t have to specify the whole number, just the unique portion of it.
5
Exit and save the profile.
Configuring bridged connections
This section shows how to configure bridging for a Pipeline connecting to a
remote site. The example configuration focuses on bridging. It does not show the
link-specific settings (such as Telco options, MP+, or frame relay configuration),
or additional routing settings that might be appropriate at your site.
Connection profiles must enable bridging, and if the remote network is not
recorded as a static bridge-table entry, Dial Brdcast must also be enabled.
Parameters related to protocol-independent bridging are set in the following
menus: