Routing Configuration Window
QuickSET Configuration Guide
127
Routing Information Protocol Options
The following options are available in the Modify RIP panel:
Do Not Send —
do not send any Routing Information Protocol packets from this interface.
Do Not Receive —
do not allow any Routing Information Protocol packets to be received by this
interface.
RIP Version 1 —
only RIP-1 messages are (sent/received). RIP-1 does not allow subnet
addressing and does not use authentication.
RIP-1 Compatible —
a RIP-2 mode in which RIP-2 messages are broadcast and multicast. RIP-1
messages and unauthenticated RIP-2 messages can be accepted.
RIP-2 —
allows sending and receiving of RIP-2 messages, authenticated RIP-2 messages, allows
subnet addressing, and IP Multicasting.
RIP-1 vs. RIP-2
A comparison of the features of RIP-1 and RIP-2 protocols (excerpted from RFC 2453, Copyright,
The Internet Society, 1998) follows:
RIP-2 is essentially an extension of RIP-1 - it is not a new protocol. It is a superset of the
environments in which RIP-1 has been traditionally used. It should be noted that RIP-2 is not
intended to be a substitute for OSPF (Open Shortest Path First) protocol in large autonomous
systems. The restrictions on autonomous system diameter and complexity which applied to RIP-1
also apply to RIP-2.
Subnet Masks
RIP-2 allows the smaller, simpler, distance-vector protocol to be used in environments which
require authentication or the use of variable length subnet masks, but are not of a size or
complexity which require the use of the larger, more complex link-state OSPF protocol.
The original impetus behind the creation of RIP-2 was the desire to include subnet masks in the
routing information exchanged by RIP, as this was not included in the original definition of RIP. As
long as the subnet mask was fixed for a network, and well known by all the nodes on that network,
a heuristic could be used to determine if a route was a subnet route or a host route.
The inclusion of the subnet mask in RIP-2 effectively creates a 64-bit address which eliminates the
network, subnet, and host distinction. Therefore the inclusion of a subnet mask in RIP-2 allows it
to be used in an autonomous system which requires precise knowledge of the subnet mask for a
given route, but does not otherwise require OSPF protocol.