The Lazy Networker

In RIPv2 we can tune its updates there are so many ways , Lets see some of them

RIPv2 Broadcast updates

Normally RIPv2 uses 224.0.0.9 as the multicast address but we can change it to global broadcast address.

debug ip rip of R1 is given below

*Sep 25 14:38:38.069: RIP: sending v2 update to 224.0.0.9 via Serial1/1 (172.16.14.1)
*Sep 25 14:38:38.069: RIP: build update entries
*Sep 25 14:38:38.069: 10.2.2.0/24 via 0.0.0.0, metric 2, tag 0
*Sep 25 14:38:38.069: 172.16.12.0/30 via 0.0.0.0, metric 1, tag 0
*Sep 25 14:38:38.069: 172.16.23.0/30 via 0.0.0.0, metric 2, tag 0

I am going to change this
interface Serial1/1
ip rip v2-broadcast

Now RIPv2 is using 255.255.255.255 for its updates
*Sep 25 15:21:33.899: RIP: sending v2 update to 255.255.255.255 via Serial1/1 (172.16.14.1)
*Sep 25 15:21:33.899: RIP: build update entries
*Sep 25 15:21:33.899: 10.2.2.0/24 via 0.0.0.0, metric 2, tag 0
*Sep 25 15:21:33.899: 172.16.12.0/30 via 0.0.0.0, metric 1, tag 0
*Sep 25 15:21:33.899: 172.16.23.0/30 via 0.0.0.0, metric 2, tag 0

RIPv2 Unicast Updates

To change to uni cast updates follow these mentioned commands
router rip
version 2
passive-interface Serial1/0
passive-interface Serial1/1
network 172.16.0.0
neighbor 172.16.12.1
neighbor 172.16.23.1
no auto-summary

Now RIP is sending updates to those neighbors only
*Sep 25 15:26:54.423: RIP: sending v2 update to 172.16.12.1 via Serial1/0 (172.16.12.1)
*Sep 25 15:26:54.423: RIP: build update entries
*Sep 25 15:26:54.423: 10.4.4.0/24 via 0.0.0.0, metric 2, tag 0
*Sep 25 15:26:54.423: 172.16.14.0/30 via 0.0.0.0, metric 1, tag 0
*Sep 25 15:26:54.423: 172.16.34.0/30 via 0.0.0.0, metric 2, tag 0
*Sep 25 15:26:54.423: RIP: sending v2 update to 172.16.23.1 via Serial1/0 (172.16.12.1)
*Sep 25 15:26:54.423: RIP: build update entries
*Sep 25 15:26:54.423: 10.4.4.0/24 via 0.0.0.0, metric 2, tag 0
*Sep 25 15:26:54.423: 172.16.14.0/30 via 0.0.0.0, metric 1, tag 0
*Sep 25 15:26:54.423: 172.16.34.0/30 via 0.0.0.0, metric 2, tag 0
R1#
*Sep 25 15:26:54.434: RIP: ignored v2 packet from 172.16.12.1 (sourced from one of our addresses)
*Sep 25 15:26:54.738: RIP: received v2 update from 172.16.14.2 on Serial1/1
*Sep 25 15:26:54.738: 10.4.4.0/24 via 0.0.0.0 in 1 hops
*Sep 25 15:26:54.738: 172.16.23.0/30 via 0.0.0.0 in 2 hops
*Sep 25 15:26:54.738: 172.16.34.0/30 via 0.0.0.0 in 1 hops