RIP: Configuring RIP to send updates as unicast

RIP: Configuring RIP to send updates as unicast

 

·         RIP v2 sends updates to 229.0.0.9

·         But if we want RIP v2 router to send updates as Unicast??

 

·         Let me take a small topology to configure RIP v2, so that it sends unicast updates

 

R1------S1/0-------------s1/0----R2

 

10.1.12.1--------------10.1.12.2

 

R1#show run | sec router

router rip

 version 2

 network 1.0.0.0

 network 10.0.0.0

 no auto-summary

R1#

 

R2#show run | sec router

router ospf 1

 log-adjacency-changes

router rip

 version 2

 network 2.0.0.0

 network 10.0.0.0

 no auto-summary

R2#

 

R1#show ip route

Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP

       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

       E1 - OSPF external type 1, E2 - OSPF external type 2

       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2

       ia - IS-IS inter area, * - candidate default, U - per-user static route

       o - ODR, P - periodic downloaded static route

 

Gateway of last resort is not set

 

     1.0.0.0/32 is subnetted, 1 subnets

C       1.1.1.1 is directly connected, Loopback0

     2.0.0.0/32 is subnetted, 1 subnets

R       2.2.2.2 [120/1] via 10.1.12.2, 00:00:08, Serial1/0

     10.0.0.0/24 is subnetted, 1 subnets

C       10.1.12.0 is directly connected, Serial1/0

R1#

 

R2#show ip route

Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP

       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

       E1 - OSPF external type 1, E2 - OSPF external type 2

       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2

       ia - IS-IS inter area, * - candidate default, U - per-user static route

       o - ODR, P - periodic downloaded static route

 

Gateway of last resort is not set

 

     1.0.0.0/32 is subnetted, 1 subnets

R       1.1.1.1 [120/1] via 10.1.12.1, 00:00:22, Serial1/0

     2.0.0.0/32 is subnetted, 1 subnets

C       2.2.2.2 is directly connected, Loopback0

     10.0.0.0/24 is subnetted, 1 subnets

C       10.1.12.0 is directly connected, Serial1/0

     11.0.0.0/24 is subnetted, 1 subnets

C       11.1.23.0 is directly connected, Serial1/1

R2#

 

R1#

R1#debug ip rip

RIP protocol debugging is on

R1#

*Mar  1 04:49:44.134: RIP: received v2 update from 10.1.12.2 on Serial1/0

*Mar  1 04:49:44.134:      2.2.2.2/32 via 0.0.0.0 in 1 hops

R1#

*Mar  1 04:49:45.654: RIP: sending v2 update to 224.0.0.9 via Serial1/0 (10.1.12.1)

*Mar  1 04:49:45.654: RIP: build update entries

*Mar  1 04:49:45.654:   1.1.1.1/32 via 0.0.0.0, metric 1, tag 0

R1#

*Mar  1 04:49:50.602: RIP: sending v2 update to 224.0.0.9 via Loopback0 (1.1.1.1)

*Mar  1 04:49:50.602: RIP: build update entries

*Mar  1 04:49:50.602:   2.2.2.2/32 via 0.0.0.0, metric 2, tag 0

*Mar  1 04:49:50.602:   10.1.12.0/24 via 0.0.0.0, metric 1, tag 0

*Mar  1 04:49:50.610: RIP: ignored v2 packet from 1.1.1.1 (sourced from one of our addresses)

R1#

*Mar  1 04:50:13.834: RIP: received v2 update from 10.1.12.2 on Serial1/0

*Mar  1 04:50:13.834:      2.2.2.2/32 via 0.0.0.0 in 1 hops

R1#

*Mar  1 04:50:15.030: RIP: sending v2 update to 224.0.0.9 via Serial1/0 (10.1.12.1)

*Mar  1 04:50:15.030: RIP: build update entries

*Mar  1 04:50:15.030:   1.1.1.1/32 via 0.0.0.0, metric 1, tag 0

R1#

 

R2#debug ip rip

RIP protocol debugging is on

R2#

*Mar  1 04:49:38.830: RIP: sending v2 update to 224.0.0.9 via Loopback0 (2.2.2.2)

*Mar  1 04:49:38.830: RIP: build update entries

*Mar  1 04:49:38.830:   1.1.1.1/32 via 0.0.0.0, metric 2, tag 0

*Mar  1 04:49:38.830:   10.1.12.0/24 via 0.0.0.0, metric 1, tag 0

*Mar  1 04:49:38.838: RIP: ignored v2 packet from 2.2.2.2 (sourced from one of our addresses)

R2#

*Mar  1 04:49:44.198: RIP: sending v2 update to 224.0.0.9 via Serial1/0 (10.1.12.2)

*Mar  1 04:49:44.198: RIP: build update entries

*Mar  1 04:49:44.198:   2.2.2.2/32 via 0.0.0.0, metric 1, tag 0

R2#

*Mar  1 04:49:45.778: RIP: received v2 update from 10.1.12.1 on Serial1/0

*Mar  1 04:49:45.778:      1.1.1.1/32 via 0.0.0.0 in 1 hops

R2#

*Mar  1 04:50:04.942: RIP: sending v2 update to 224.0.0.9 via Loopback0 (2.2.2.2)

*Mar  1 04:50:04.942: RIP: build update entries

*Mar  1 04:50:04.942:   1.1.1.1/32 via 0.0.0.0, metric 2, tag 0

*Mar  1 04:50:04.942:   10.1.12.0/24 via 0.0.0.0, metric 1, tag 0

*Mar  1 04:50:04.950: RIP: ignored v2 packet from 2.2.2.2 (sourced from one of our addresses)

R2#

*Mar  1 04:50:13.874: RIP: sending v2 update to 224.0.0.9 via Serial1/0 (10.1.12.2)

*Mar  1 04:50:13.874: RIP: build update entries

*Mar  1 04:50:13.874:   2.2.2.2/32 via 0.0.0.0, metric 1, tag 0

R2#

 

Observation:

·         By default RIP v2 send updates as multicast

 

·         Now, let me configure RIPv2 in such a way that it sends updates as Unicast:

 

R1(config)#router rip

R1(config-router)#neighbor 10.1.12.1

R1(config-router)#

R1(config-router)#passive-interface default

R1(config-router)#

 

R2(config)#router rip

R2(config-router)#neighbor 10.1.12.1

R2(config-router)#

R2(config-router)#passive-interface default

R2(config-router)#

 

R1#

*Mar  1 05:16:53.202: RIP: sending v2 update to 10.1.12.2 via Serial1/0 (10.1.12.1)

*Mar  1 05:16:53.202: RIP: build update entries

*Mar  1 05:16:53.202:   1.1.1.1/32 via 0.0.0.0, metric 1, tag 0

R1#

*Mar  1 05:17:16.918: RIP: received v2 update from 10.1.12.2 on Serial1/0

*Mar  1 05:17:16.918:      2.2.2.2/32 via 0.0.0.0 in 1 hops

R1#

*Mar  1 05:17:19.502: RIP: sending v2 update to 10.1.12.2 via Serial1/0 (10.1.12.1)

*Mar  1 05:17:19.502: RIP: build update entries

*Mar  1 05:17:19.502:   1.1.1.1/32 via 0.0.0.0, metric 1, tag 0

R1#

 

R2#

*Mar  1 05:16:50.286: RIP: sending v2 update to 10.1.12.1 via Serial1/0 (10.1.12.2)

*Mar  1 05:16:50.286: RIP: build update entries

*Mar  1 05:16:50.286:   2.2.2.2/32 via 0.0.0.0, metric 1, tag 0

R2#

*Mar  1 05:16:53.350: RIP: received v2 update from 10.1.12.1 on Serial1/0

*Mar  1 05:16:53.354:      1.1.1.1/32 via 0.0.0.0 in 1 hops

R2#

R2#

*Mar  1 05:16:55.354: RIP: sending v2 flash update to 10.1.12.1 via Serial1/0 (10.1.12.2)

*Mar  1 05:16:55.354: RIP: build flash update entries - suppressing null update

R2#

R2#

*Mar  1 05:17:17.010: RIP: sending v2 update to 10.1.12.1 via Serial1/0 (10.1.12.2)

*Mar  1 05:17:17.010: RIP: build update entries

*Mar  1 05:17:17.010:   2.2.2.2/32 via 0.0.0.0, metric 1, tag 0

R2#

*Mar  1 05:17:19.650: RIP: received v2 update from 10.1.12.1 on Serial1/0

*Mar  1 05:17:19.650:      1.1.1.1/32 via 0.0.0.0 in 1 hops

R2#

 

Observation:

·         Now, RIP v2 is sending updates as Unicast