User`s guide

Configuring the Pipeline as a Bridge
Introduction to Ascend bridging
Pipeline User’s Guide Preliminary January 30, 1998 5-5
When there is no server support on the local network
If the local Ethernet supports NetWare clients only and no NetWare servers, the
bridging connection should enable a local client to bring up the WAN connection
by querying (broadcasting) for a NetWare server on a remote network. However,
the connection should not stay up indefinitely because of RIP or SAP broadcasts.
To accomplish this, open Ethernet > Connections > profile > IPX options and set
Handle IPX=Client.
When there is no server support on the remote network
If the local network supports NetWare servers (or a combination of clients and
servers) and the remote network supports NetWare clients only, the bridging
connection should enable the Pipeline to respond to NCP watchdog requests for
remote clients, but to bring down inactive connections whenever possible.
To accomplish this, open Ethernet > Connections > profile > IPX options and
specify a timeout value (for example, set NetWare t/o=30), and set the Handle
IPX parameter to Server.
When there is server support on both networks
If NetWare servers are supported on both sides of the WAN connection, it is
strongly recommended that you use an IPX routing configuration instead of
bridging IPX. If you bridge IPX in that type of environment, client/server logins
are lost when the Pipeline brings down an inactive WAN connection.
IPX routing and bridging on the same connection
When IPX routing is enabled for a connection, the Pipeline routes only one
packet frame type across that connection. For example, if the IPX frame type is
set to 802.3, only 802.3 packets are routed. If some NetWare servers on the local
network use a different frame type, such as 802.2, those packets are bridged if
bridging is enabled, or discarded if bridging is not enabled.