Showing posts with label RIP. Show all posts
Showing posts with label RIP. Show all posts

RIPv2

RIPv2 is a classless, distance vector routing protocol as defined in RFC 1723. Because RIPv2 is a classless routing protocol, which means, it includes the subnet mask with the network addresses in the routing updates. As with other classless routing protocols, RIPv2 supports CIDR super-nets, VLSM and discontiguous networks.

Due to the deficiencies of RIPv1, RIP version 2 (RIPv2) was developed sometime in 1993. It’s equipped with the ability to support subnet information and supports Classless Inter-Domain Routing (CIDR). A router that receives routing updates from multiple routers advertising the same classful summary route cannot determine which subnets belong to which summary route. This inability leads to unexpected results including misrouted packets.

However, with RIPv2 automatic summarization can be disabled with the no auto-summary command. Automatic summarization must be disabled to support discontiguous networks.

RIPv2 still maintains the hop count limit of 15 and incorporated a password authentication mechanism. However, passwords were transmitted in clear-text format, which were found insufficient for secure communications on the Internet.

The default version of RIP is version 1. The command version 2 is used to modify RIPv1 to RIPv2.

Use The show ip protocols command to view that RIP is now sending and receiving version 2 updates and whether or not automatic summarization is in effect.

RIPv2 is actually an enhancement of RIPv1's features and extensions rather than an entirely new protocol. Some of these enhanced features include:

  • Next-hop addresses included in the routing updates
  • Use of multicast addresses in sending updates
  • Authentication option available
Like RIPv1, RIPv2 is a distance vector routing protocol. Both versions of RIP share the following features and limitations:
Use of hold down and other timers to help prevent routing loops.
  • Use of split horizon or split horizon with poison reverse to also help prevent routing loops.
  • Use of hold down and other timers to help prevent routing loops.
  • Use of triggered updates when there is a change in the topology for faster convergence.
  • Maximum hop count limit of 15 hops, with the hop count of 16 signifying an unreachable network.

For more information about NetworkzPeritus, you may visit our website at http://www.NetworkzPeritus.com/ & blog at http://networkzperitus.blogspot.com/

Posted by Shubham,Shushant & Viviek