Next: , Previous: , Up: RIP   [Contents][Index]


5.3 RIP Version Control

RIP can be configured to send either Version 1 or Version 2 packets. The default is to send RIPv2 while accepting both RIPv1 and RIPv2 (and replying with packets of the appropriate version for REQUESTS / triggered updates). The version to receive and send can be specified globally, and further overriden on a per-interface basis if needs be for send and receive seperately (see below).

It is important to note that RIPv1 can not be authenticated. Further, if RIPv1 is enabled then RIP will reply to REQUEST packets, sending the state of its RIP routing table to any remote routers that ask on demand. For a more detailed discussion on the security implications of RIPv1 see RIP Authentication.

RIP Command: version version

Set RIP version to accept for reads and send. version can be either ‘1” or ‘2”.

Disabling RIPv1 by specifying version 2 is STRONGLY encouraged, See RIP Authentication. This may become the default in a future release.

Default: Send Version 2, and accept either version.

RIP Command: no version

Reset the global version setting back to the default.

Interface command: ip rip send version version

version can be ‘1’, ‘2’ or ‘1 2’.

This interface command overrides the global rip version setting, and selects which version of RIP to send packets with, for this interface specifically. Choice of RIP Version 1, RIP Version 2, or both versions. In the latter case, where ‘1 2’ is specified, packets will be both broadcast and multicast.

Default: Send packets according to the global version (version 2)

Interface command: ip rip receive version version

version can be ‘1’, ‘2’ or ‘1 2’.

This interface command overrides the global rip version setting, and selects which versions of RIP packets will be accepted on this interface. Choice of RIP Version 1, RIP Version 2, or both.

Default: Accept packets according to the global setting (both 1 and 2).


Next: , Previous: , Up: RIP   [Contents][Index]