ECS4100 Series Web Management Guide-R07

Chapter 18 | Unicast Routing
Configuring the Routing Information Protocol
– 694 –
◆ Receive Version – The RIP version to receive on an interface.
■
RIPv1: Accepts only RIPv1 packets.
■
RIPv2: Accepts only RIPv2 packets.
■
RIPv1 and RIPv2: Accepts RIPv1 and RIPv2 packets.
■
Do Not Receive: Does not accept incoming RIP packets. This option does
not add any dynamic entries to the routing table for an interface.
The default depends on the setting for the Global RIP Version. (See
“Configuring General Protocol Settings” on page 681.)
◆ Authentication Type – Specifies the type of authentication required for
exchanging RIPv2 protocol messages. (Default: No Authentication)
■
No Authentication: No authentication is required.
■
Simple Password: Requires the interface to exchange routing information
with other routers based on an authorized password. (Note that
authentication only applies to RIPv2.)
■
MD5: Message Digest 5 (MD5) authentication.
MD5 is a one-way hash algorithm is that takes the authentication key and
produces a 128 bit message digest or “fingerprint.” This makes it
computationally infeasible to produce two messages having the same
message digest, or to produce any message having a given pre-specified
target message digest.
◆ Authentication Key – Specifies the key to use for authenticating RIPv2 packets.
For authentication to function properly, both the sending and receiving
interface must use the same password. (Range: 1-16 characters, case sensitive)
◆ Instability Prevention – Specifies the method used to reduce the convergence
time when the network topology changes, and to prevent RIP protocol
messages from looping back to the source router.
■
Split Horizon – This method never propagate routes back to an interface
from which they have been acquired.
■
Poison Reverse – This method propagates routes back to an interface from
which they have been acquired, but sets the distance-vector metrics to
infinity. This provides faster convergence. (This is the default setting.)
■
None – No loopback prevention method is employed. If a loop occurs
without using any prevention method, the hop count for a route may be
gradually incremented to infinity (that is, 16) before the route is deemed
unreachable.