Solved: RIP Query

wasiimcisco · ‎05-30-2011

Hi

I have three Routers connected in the LAN.

R1-------------->R2------------------>R3
RIP Static RIP

I wanted to exchange the RIP Routes between R1 and R3 but I cant run the RIP or any other protocol on R2.

I can only add the Static routes in R2. My objective if I will advertise any route in R1 it should goes to

R3 via RIP update.

Please let me know how to achieve this.

Giuseppe Larosa · ‎05-31-2011

Hello Wasiim,

you need to instruct routers to avoid to check RIP IP source:

>> RIP: ignored v2 update from bad source 155.1.13.5 on FastEthernet0/1/0

no validat-update-source

see

http://www.cisco.com/en/US/docs/ios/iproute_rip/command/reference/irr_rip.html#wp1012874

be aware that in real world no one will never do something like this

Hope to help

Giuseppe

View solution in original post

Thotsaphon Lueangwattanaphong · ‎05-30-2011

Hi,

You can create a tunnel interface to connect between R1 and R3 and run RIP on the tunnel interface.

HTH,

Toshi

wasiimcisco · ‎05-31-2011

Hi,

Thanks for the reply. But I discussed this with my Friend but he is saying there is another way to do this. Actually this is a lab setup and my friend has put this question how to achieve this RIP routing exchange between two routers when the middle router is only having static routes.

Any idea how to achieve this without making tunnel.

Shahzad Qadir · ‎05-31-2011

Hi,

You will have to configure static route on R1 to reach R3 and vice versa. Once they have reachability they can share rip unicast updates without any problem, you will have to configure a neighbor statement on R1& R3 so they start sending unicast updates rather than default broadcast.

wasiimcisco · ‎05-31-2011

Hi,

Thanks for the reply i tired the same but no luck

5.5.5.5.5 and 6.6.6.6(----------R5--------------------------------------->R4<-------------------------------------------->R3-----) 3.3.3.3 & 1.1.1.1

.5 155.1.13.x .4 .4 155.1.23.x .3

ENOC-R3-HO#show ip int brief

Interface IP-Address OK? Method Status Protocol

FastEthernet0/1/0 155.1.23.3 YES manual up up

Loopback0 3.3.3.3 YES manual up up

Loopback1 1.1.1.1 YES manual up up

ENOC-R3-HO#show run | b r r
router rip
version 2
network 1.0.0.0
network 3.0.0.0
network 155.1.0.0
neighbor 155.1.13.5
no auto-summary
!
ip forward-protocol nd
ip route 155.1.13.0 255.255.255.0 155.1.23.4

ENOC-R3-HO#show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater

Device ID Local Intrfce Holdtme Capability Platform Port ID
ENOC-R4-HO Fas 0/1/0 178 R S I 1841 Fas 0/1/0

ENOC-R3-HO#ping 155.1.13.5

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 155.1.13.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms

*May 31 15:06:34.744: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/1/0 (155.1.23.3)
*May 31 15:06:34.744: RIP: build update entries
*May 31 15:06:34.744:   1.1.1.1/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:06:34.744:   3.3.3.3/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:06:34.744:   155.1.23.0/24 via 0.0.0.0, metric 1, tag 0
*May 31 15:06:34.744: RIP: sending v2 update to 155.1.13.5 via FastEthernet0/1/0 (155.1.23.3)
*May 31 15:06:34.744: RIP: build update entries
*May 31 15:06:34.744:   1.1.1.1/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:06:34.744:   3.3.3.3/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:06:34.744:   155.1.23.0/24 via 0.0.0.0, metric 1, tag 0

=========================================================================================
R5#show ip int brief
Interface IP-Address OK? Method Status Protocol

Loopback0 6.6.6.6 YES manual up up

Loopback1 5.5.5.5 YES manual up up

Vlan1 155.1.13.5 YES manual up up

R5#show run | b r r
router rip
version 2
network 5.0.0.0
network 6.0.0.0
neighbor 155.1.23.3
no auto-summary
!
ip route 155.1.23.0 255.255.255.0 155.1.13.4
!
!
ip http server
no ip http secure-server
!
!
!
!
!
!
!
control-plane
!
!
line con 0

R5#ping 155.1.23.3

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 155.1.23.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms

*May 31 15:15:43.755: RIP: sending v2 update to 224.0.0.9 via Loopback1 (5.5.5.5)
*May 31 15:15:43.755: RIP: build update entries
*May 31 15:15:43.755: 5.5.5.5/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:15:43.755: 6.6.6.6/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:15:43.755: RIP: ignored v2 packet from 5.5.5.5 (sourced from one of our addresses)u all

========================================================================================

ENOC-R4-HO#ping 155.1.23.3

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 155.1.23.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
ENOC-R4-HO#ping 155.1.13.5

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 155.1.13.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
ENOC-R4-HO#

ENOC-R4-HO#show ip int brief
Interface                  IP-Address      OK? Method Status                Protocol

FastEthernet0/1            155.1.13.4      YES manual up                    up
FastEthernet0/1/0          155.1.23.4      YES manual up                    up

================================================================================================

Please let me know what I am missing

Shahzad Qadir · ‎05-31-2011

R3's config is fine. On router 5 you are missing network statement for 155.1.23.0

if look at debugs you will see r3 is sending updates to unicast address of R5 but R5 is still sending updates to 224.0.0.9

wasiimcisco · ‎05-31-2011

Hi,

R5(config)#do sh run | b r r
router rip
version 2
network 5.0.0.0
network 6.0.0.0
network 155.1.0.0
neighbor 155.1.23.3
no auto-summary
!
ip route 155.1.23.0 255.255.255.0 155.1.13.4

May 31 15:56:09.370: RIP: ignored v2 update from bad source 155.1.23.3 on Vlan1
*May 31 15:56:10.434: RIP: sending v2 update to 224.0.0.9 via Loopback1 (5.5.5.5)
*May 31 15:56:10.434: RIP: build update entries
*May 31 15:56:10.434:   5.5.5.5/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:56:10.434:   6.6.6.6/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:56:10.434:   155.1.13.0/24 via 0.0.0.0, metric 1, tag 0
*May 31 15:56:10.434: RIP: ignored v2 packet from 5.5.5.5 (sourced from one of our addresses)
*May 31 15:56:14.946: RIP: sending v2 update to 224.0.0.9 via Vlan1 (155.1.13.5)
*May 31 15:56:14.946: RIP: build update entries
*May 31 15:56:14.946:   5.5.5.5/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:56:14.946:   6.6.6.6/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:56:14.946:   155.1.13.0/24 via 0.0.0.0, metric 1, tag 0
*May 31 15:56:14.946: RIP: sending v2 update to 155.1.23.3 via Vlan1 (155.1.13.5)
*May 31 15:56:14.946: RIP: build update entries
*May 31 15:56:14.946:   5.5.5.5/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:56:14.946:   6.6.6.6/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:56:14.946:   155.1.13.0/24 via 0.0.0.0, metric 1, tag 0

=====================================================================================================

ENOC-R3-HO#sh run | b r r
router rip
version 2
network 1.0.0.0
network 3.0.0.0
network 155.1.0.0
neighbor 155.1.13.5
no auto-summary
!
ip forward-protocol nd
ip route 155.1.13.0 255.255.255.0 155.1.23.4

ENOC-R3-HO#sh
*May 31 15:40:39.375: RIP: sending v2 update to 224.0.0.9 via Loopback1 (1.1.1.1)
*May 31 15:40:39.375: RIP: build update entries
*May 31 15:40:39.375:   3.3.3.3/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:40:39.375:   155.1.23.0/24 via 0.0.0.0, metric 1, tag 0
*May 31 15:40:39.375: RIP: ignored v2 packet from 1.1.1.1 (sourced from one of our addresses) ru
*May 31 15:40:40.543: RIP: sending v2 update to 224.0.0.9 via Loopback0 (3.3.3.3)
*May 31 15:40:40.543: RIP: build update entries
*May 31 15:40:40.543:   1.1.1.1/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:40:40.543:   3.3.3.3/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:40:40.543:   155.1.23.0/24 via 0.0.0.0, metric 1, tag 0
*May 31 15:40:40.543: RIP: ignored v2 packet from 3.3.3.3 (sourced from one of our addresses)
*May 31 15:40:42.707: RIP: sending v2 update to 224.0.0.9 via FastEthernet0/1/0 (155.1.23.3)
*May 31 15:40:42.707: RIP: build update entries
*May 31 15:40:42.707:   1.1.1.1/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:40:42.707:   3.3.3.3/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:40:42.707:   155.1.23.0/24 via 0.0.0.0, metric 1, tag 0
*May 31 15:40:42.707: RIP: sending v2 update to 155.1.13.5 via FastEthernet0/1/0 (155.1.23.3)
*May 31 15:40:42.707: RIP: build update entries
*May 31 15:40:42.707:   1.1.1.1/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:40:42.707:   3.3.3.3/32 via 0.0.0.0, metric 1, tag 0
*May 31 15:40:42.707:   155.1.23.0/24 via 0.0.0.0, metric 1, tag 0
*May 31 15:40:47.323: RIP: ignored v2 update from bad source 155.1.13.5 on FastEthernet0/1/0

Giuseppe Larosa · ‎05-31-2011