Table of Contents
Advertisement
Features
Route Tags
Authentication
Copyright © 2010, Juniper Networks, Inc.
RFC 1058—Routing Information Protocol (June 1998)
RFC 2453—RIP Version 2 (November 1998)
Some of the major RIP features supported by the router include:
authentication
BFD liveness detection
equal-cost multipath
multicast addressing
next hop
poison reverse
remote neighbors
A route tag is a field in a RIP message that allows boundary routers in an autonomous
system (AS) to exchange information about external routes. Route tags provide a method
of separating internal RIP routes (routes within the RIP routing domain) from external
RIP routes, which may have been imported from an EGP (exterior gateway protocol) or
another IGP (interior gateway protocol).
Routers supporting protocols other than RIP should be configurable to allow the route
tags to be configured for routes imported from different sources. For example, routes
imported from BGP should be able to have their route tags set to the number of the ASs
from which the routes were learned.
RIPv1 does not support authentication. If you are sending and receiving RIPv2 packets,
you can enable RIP authentication on an interface.
The router provides the simple authentication scheme for RIPv2. Because authentication
is a per message function and only one 2-octet field is available in the RIP message
header, authentication uses the space of an entire RIP message.
The first 20-byte entry in a RIP authentication message contains an address family
identifier value of 0xffff and a route tag value of 2. If the 0xffff address family is present
in the RIP message, the remaining 16 octets of the entry contain a plain text password.
If the password is fewer than 16 octets, it must be left-justified and padded to the right
with nulls (0x00).
Authentication is applied per RIP interface. You can specify either text or MD5
authentication. Text authentication uses a simple password that must be shared by the
Chapter 4: Configuring RIP
RIP version 1
RIP version 2
route summarization
route tags
split horizon
subnet masks
203
Advertisement
Table of Contents
