User`s guide

Configuring IP Routing
Introduction to IP routing on the Pipeline
2-8 Preliminary January 30, 1998 Pipeline User’s Guide
Route IP=Yes
3
Set Recv Auth=Either.
Or set it to PAP, CHAP, or MS-CHAP. Either indicates any protocol that both
sides agree upon.
Connection profiles and IP routes
The Pipeline creates a routing table when it powers up. It adds all known routes
to the table, including connected routes (such as Ethernet) and routes configured
in its resident Connection profiles and Static Rtes profiles. If RIP is enabled in
the Ethernet, it supplies information about routes learned from other routers to
the routing table. If RIP is enabled on an active connection, it supplies
information about the routes received from the far-end of that connection to the
routing table.
There are some static routes that the Pipeline cannot read at power-up. They do
not become part of the routing table until they are up and usable. Such routes
include those added via the
Iproute add
terminal server command.
How the Pipeline uses its routing table
When the Pipeline receives an IP packet whose destination address is not on the
local network, it checks its routing table for the destination network and:
• If it finds a route to that network, it forwards the packet to the gateway
indicated by that route. If the gateway is not local, the Pipeline opens a WAN
connection to forward the packet.
• If it does not find a route to that network, it forwards the packet to the default
router.
• If it does not find a route to that network and no default route has been
configured, it drops the packet.
When the Pipeline receives an incoming IP routing call, it examines the source IP
address and looks for a matching profile. If the source matches a resident
Connection profile, the Pipeline updates its routing table, if necessary, with the
route to the source network.
If the Answer profile is configured without authentication requirements (an
unlikely scenario) and Profile Reqd is set to No, the Pipeline accepts any IP