RFC 1388 was
then superseded in November 1994 by RFC 1723, which describes RIPv2 (the second version of RIP). These
RFCs did not attempt to make obsolete the previous version of RIP, but proposed extensions and enhancements
to the RIP capabilities. RIPv2 enabled RIP messages to carry more information and scale further with more
features, such as multicast support and a next-hop router address. The next-hop router address is an
authentication mechanism; its most important function is to support subnet masks and is therefore a critical
feature that was not available in RIPv1. RIP is a dynamic, distance-vector routing protocol that uses UDP as the
transport protocol. RIP packets are transmitted on UDP port 520 for route updates.
The Security Appliance supports both RIPv1 and RIPv2 protocols. Using RIP has advantages over using static
routes, because the initial configuration for RIP is simple and does not require updating the configuration when
the topology changes. The downside to RIP (or any other dynamic protocol) is that there is more network and
processing overhead than with static routing.
By default, the Security Appliance sends RIPv1 updates and accepts RIPv1 and RIPv2 updates.
Pages:
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290