Concepts:
RIPv2: Extensions to RIP: subnet masks, hop-count, external route-tags
authentication, uses multicast (224.0.0.9)
Compatibility: RIPv2 accepts v1 messages. RIPv1 discards the update if ver = 1 & unused fields are set. If ver > 1, then the unused field bits are ignored and the rest of the update is processed. Compatibility is set both in the RIP process and at the interface level
router rip –> Send and receive only V1 updates
version 1
router rip –> Send and receive only V2 updates
version 2
router rip –> Default Send only V1 but recieve V1 and V2
at the interface: ip rip send version 1 2
ip rip receive version 1 2
Authentication: The first route entry in the message is replaced with Authentication parameters. ID’ed by setting : Family address 0xffff; route-tag 2 (clear-text)/3 (md5 -purely Cisco, non-rfc)
———–xxx———-
RIPng: m/c address ff02::9, UDP 521, uses IPV6 Auth headers (AH/ESP)
RIPng uses a special message for the next-hop. All routes following which, uses it, until a new next-hop message is seen.
Configuration:
RIPv2
Enabling rip version 2 causes updates to be multicast. If the v2 update needs to be sent to a V1 router, other than by using the interface send/receive command (for eg if split horizon prevents a V1 send/receive enabled router to update a V1 only router). solution:
router rip
neighbor <ip of V1 only Rtr>
or
interface <broadcast segment>
no ip split-horizon
Summarization: Default behaviour – summarize networks to the interface subnet. In RIPv2, this can be disabled to send the subnnet mask with the update by:
router rip
no auto-summary
Authentication:
simple
(config)#key chain MyKeyChain
(config-keychain)#key 1
(config-keychain-key)#key-string test1
(config-if)#ip rip authentication mode md5
(config-if)#ip rip authentication key-chain MyKeyChain
Key Management (Used to roll-over the password)
(config)#key chain MyKeyChain
(config-keychain)#key 1
(config-keychain-key)#key-string test1
(config-keychain-key)#accept-lifetime <hh:mm:ss> <date> <Month> duration/infinite
(config-keychain-key)#send-lifetime <hh:mm:ss> <date> <Month> duration/infinite
RIPng:
Configured with a single interface command:
interface fa0/0
ipv6 enable Multiple such processes can be enabled per interface.
ipv6 address <>
ipv6 rip MyProc1 enable Inserts a “ipv6 router rip MyProc1″ into the global running config.
ipv6 rip MyProc2 enable
No 2 processes should use the same UDP ports on the same i/f
ipv6 router rip MyProc1
port 527 multicast ff02::9
Parameter Customization:
ipv6 router rip MyProc1
timers <update> <invalidate> <holddown> <flush>
maximum-paths <1-64> ; default 16 equal-cost paths
distance <AD> ; changes the value of the AD for this process locally.
Metrics: Unlike v1/v2, where the hop-count to an update (inbound or out) could be changed by using an offset-list, in ‘ng’ the hop-count can only be changed for all updates on an incoming interface. By default, the process increments the metric by 1.
At an interface: ipv6 rip MyProc1 metric-offset 3
Summarization: IPv6 => subnetting happens in the network bits
at an interface: ipv6 rip MyProc1 summary-address 2001:db8:0:10::/62
