IP RIP Receive Command on CISCO Router/Switch

Command

IP RIP Receive

Use

This command is used tell RIP what version to receive its updates in for a specified interface. Updates can be sent in Version 1, Version 2, or both.
It is useful if you have a legacy host that runs RIP but only supports Version 1.

Syntax

Router(config-if)#ip rip receive version <version> <version>

Example

IP RIP Receive Command on CISCO Router/Switch 1

In this example, we will configure RIP on R2 to receive R1’s RIPv1 updates.

First, we will configure RIPv1 for all interfaces on R1. Notice that, by default, RIPv1 will allow RIPv2 packets to be received.

R1(config)#router rip
R1(config-router)#no auto
R1(config-router)#network 0.0.0.0

R1(config-router)#do show ip protocol
Routing Protocol is “rip”
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 0 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Redistributing: rip
Default version control: send version 1, receive any version
Interface Send Recv Triggered RIP Key-chain
FastEthernet0/0 1 1 2
Serial1/0 1 1 2
Serial1/1 1 1 2
Loopback0 1 1 2
Loopback1 1 1 2
Loopback11 1 1 2
Loopback12 1 1 2
Loopback22 1 1 2
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
0.0.0.0
Routing Information Sources:
Gateway Distance Last Update
Distance: (default is 120)

Now we will configure RIPv2 for all interfaces on R2. Notice how RIPv2 only allows RIPv2 packets to be received

R2(config)#router rip
R2(config-router)#version 2
R2(config-router)#no auto
R2(config-router)#network 0.0.0.0

R2(config)#do show ip protocols
Routing Protocol is “rip”
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Sending updates every 30 seconds, next due in 23 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Redistributing: rip
Default version control: send version 2, receive version 2
Interface Send Recv Triggered RIP Key-chain
FastEthernet0/0 2 2
FastEthernet1/0 2 2
NVI0 2 2
Loopback0 2 2
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
0.0.0.0
Routing Information Sources:
Gateway Distance Last Update
10.2.2.3 120 00:00:02
Distance: (default is 120)

Currently, we are not receiving any routes from R1 due to the difference in versions.

R2(config-if)#do show ip route rip

R2(config-if)#

Next we will configure R1’s Fa0/0 to allow RIP to receive either version 1 or version 2 packets.

R2(config-if)#int fa0/0

R2(config-if)#ip rip receive version 1 2

Now we have entries in the routing table.

R2(config-if)#do show ip route rip
R 1.0.0.0/8 [120/1] via 10.1.1.1, 00:00:13, FastEthernet0/0
R 111.0.0.0/8 [120/1] via 10.1.1.1, 00:00:13, FastEthernet0/0
R 11.0.0.0/8 [120/1] via 10.1.1.1, 00:00:13, FastEthernet0/0
Subscribe
Notify of
guest

0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x