User`s guide

Configuring IP Routing
Introduction to IP routing on the Pipeline
2-2 Preliminary January 30, 1998 Pipeline User’s Guide
IP routing connections have a level of built-in authentication, because the
Pipeline matches the IP address of a Connection profile to the source IP address
of a caller. For most sites, however, this level of security is not enough and a form
of password authentication is used as well. (For more information, see Chapter 7,
“Setting Up Pipeline Security.”)
Note:
IP routing can be configured along with protocol-independent bridging
and IPX routing in any combination. However, you cannot bridge and route IP
packets across the same connection. When you configure the Pipeline as an IP
router, IP packets are no longer bridged at the link layer. They are always routed
at the network layer. All other protocols continue to be bridged unless you turn
off bridging. (For more information about bridging, see Chapter 5, “Configuring
the Pipeline as a Bridge.”)
Host-to-router connections
When the device connecting to the Pipeline is a host running PPP dial-in
software, the Pipeline adds a “host route” to its routing table. (For discussion of
host routes, see “Subnet mask notation” on page 2-4.)
If the host belongs to its own IP network, the Pipeline must have a Connection
profile stating the host’s address, using a 32-bit netmask.
When the dial-in user calls the Pipeline, the Pipeline checks its Answer profile to
verify that it can accept incoming IP routing calls. If it can, it checks whether it
has a Connection profile for that user. If the Answer profile is not configured to
allow incoming IP routing calls, or if there is no Connection profile for the call,
the call is refused.
If the Answer profile does allow the call, the Pipeline looks for a Connection
profile matching the user’s name and IP address. If the Pipeline doesn’t find a
matching profile, it ends the call.
If the Pipeline does find an address and the PPP software accepts it, the Pipeline
authenticates the connection using password authentication, and then establishes
the connection.
When the connection is established, the Pipeline adds a host route to its routing
table and begins functioning as an IP router between its local and WAN