LevelOne GTL-2691 - Manual (Page 663)

C HAPTER 20 | Unicast Routing
Configuring the Routing Information Protocol
– 663 –
◆ "ip rip authentication mode" on page 1467
◆ "ip rip authentication string" on page 1468
◆ "ip rip split-horizon" on page 1471
C OMMAND U SAGE
Specifying Receive and Send Protocol Types
◆ Specify the protocol message type accepted (that is, RIP version) and
the message type sent (that is, RIP version or compatibility mode) for
each RIP interface.
◆ Setting the RIP Receive Version or Send Version for an interface
overrides the global setting specified in the RIP General Settings screen
(see "Configuring General Protocol Settings" on page 651 ).
◆ The Send Version can be specified based on these options:
■
Use “RIPv1” or “RIPv2” if all routers in the local network are based
on RIPv1 or RIPv2, respectively.
■
Use “RIPv1 Compatible” to propagate route information by
broadcasting to other routers on the network using the RIPv2
advertisement list, instead of multicasting as normally required by
RIPv2. (Using this mode allows older RIPv2 routers which only
receive RIP broadcast messages to receive all of the information
provided by RIPv2, including subnet mask, next hop and
authentication information. (This is the default setting.)
■
Use “Do Not Send” to passively monitor route information
advertised by other routers attached to the network.
◆ The Receive Version can be specified based on these options:
■
Use “RIPv1” or “RIPv2” if all routers in the local network are based
on RIPv1 or RIPv2, respectively.
■
Use “RIPv1 and RIPv2” if some routers in the local network are
using RIPv2, but there are still some older routers using RIPv1.
(This is the default setting.)
■
Use “Do Not Receive” if dynamic entries are not required to be
added to the routing table for an interface. (For example, when only
static routes are to be allowed for a specific interface.)
Protocol Message Authentication
RIPv1 is not a secure protocol. Any device sending protocol messages from
UDP port 520 will be considered a router by its neighbors. Malicious or
unwanted protocol messages can be easily propagated throughout the
network if no authentication is required.
RIPv2 supports authentication using a simple password or MD5 key
encryption. When a router is configured to exchange authentication
messages, it will insert the password into all transmitted protocol packets,
and check all received packets to ensure that they contain the authorized