RIPv1 is a Distance-Vector Routing protocol
RIPv1 is a Classful routing protocol. Classful routing protocols bolster just the systems which are not subnetted. Classful routing protocols don’t send subnet veil data with their routing updates. As it were, on the off chance that you have a subnetted arrange in your
RIPv1 directing area, RIPv1 will declare that network to different as un subnetted organize.
RIPv1 does not support VLSM (Variable Length Subnet Masking)
• RIPv1 bolster greatest metric (jump tally) estimation of 15. Any switch more remote than 15 jumps away is considered as inaccessible.
• RIPv1 send routing updates occasionally at regular intervals as communicates utilizing goal IP address as limited broadcast IP address
255.255.255.255. Since the updates are sent utilizing the goal IP address of constrained communicate IP address
255.255.255.255, each switch needs to process the directing refresh messages (regardless of whether they are running RIPv1 or not).
• RIPv1 does not bolster the verification of refresh messages (plain-content or MD5).
Routing Technologies-Protocol Version 2 (RIPv2)
RIPv2 is a
Hybrid Routing Protocol. A
Hybrid Routing Protocol is essentially a
Distance-Vector convention which a few attributes of
Link State steering conventions.
RIPv2 is classless routing, which enables us to utilize subnetted networks also. RIPv2 has the alternative for sending system veil in the refresh to permit awkward directing.
• RIPv2 bolster
VLSM (Variable Length Subnet Masking).
• RIPv2 bolster greatest
metric (hop count) estimation of 15. Any router more remote than 15 bounces away is considered as inaccessible.
• RIPv2 bolsters activated updates.
• RIPv2 routing updates are sent as
Multicast traffic at goal multicast address of
126.96.36.199. Multicast updates decrease network traffic. The Multicast routing updates likewise helps in reducing routing update message preparing overhead in running which is not running RIPv2. Just the switches running RIPv2 join to the multicast bunch
188.8.131.52. Other routers which are not running RIPv2 can just channel the routing update packet at Layer 2.
• RIPv2 support authentication of RIPv2 refresh messages (plain-content or MD5). Authentication helps in affirming that the updates are originating from approved sources.