RIPv2

Classless Routing Protocols

Benefits:

All-zeros and all-ones subnets

- Although some vendors, like Cisco, can also handle this with classful routing protocols.
Can have discontiguous subnets Better IP addressing allocation More control over route summarization

VLSM

CIDR

Classless Routing Protocols

Classless Routing Protocols:

RIPv2 EIGRP OSPF IS-IS BGPv4

Few RIP facts

RIP still working on routers and hosts today.

IP RIP derived from RIP by Xerox for its XNS protocol stack. Initially implemented in Berkeley UNIX routed program. RIPv1 Charles Hedrick, RFC 1058, 1988 RIPv2 Gary Malkin, RFC 1723, 1994 RIPng for IPv6 Gary Malkin, RFC 2080, 1997 (proposed standard), extension to RIPv2 message format.

RIP version 1
Classful Routing Protocol, sent over UDP port 520 Does not include the subnet mask in the routing updates. Automatic summarization done at major network boundaries. Updates sent as broadcasts unless the neighbor command is uses which sends them as unicasts.

RIP version 1
0 1 2 3 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | command (1) | version (1) | must be zero (2) | +---------------+---------------+-------------------------------+ | address family identifier (2) | must be zero (2) | +-------------------------------+-------------------------------+ | IP address (4) | +---------------------------------------------------------------+ | must be zero (4) | +---------------------------------------------------------------+ | must be zero (4) | +---------------------------------------------------------------+ | metric (4) | +---------------------------------------------------------------+

RIP version 2
Classless Routing Protocol, sent over UDP port 520 Includes the subnet mask in the routing updates. Automatic summarization at major network boundaries can be disabled. Updates sent as multicasts unless the neighbor command is uses which sends them as unicasts.

RIP version 2
0 1 2 3 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | command (1) | version (1) | must be zero (2) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Address Family Identifier (2) | Route Tag (2) | +-------------------------------+-------------------------------+ | IP Address (4) | +---------------------------------------------------------------+ | Subnet Mask (4) | +---------------------------------------------------------------+ | Next Hop (4) | +---------------------------------------------------------------+ | Metric (4) | +---------------------------------------------------------------+

RIP v2 operation

All of the operational procedures, timers, and stability functions of RIP v1 remain the same in RIP v2, with the exception of the broadcast updates.

RIP v2 updates use reserved Class D address 224.0.0.9.

Issues addressed by RIP v2

Authentication of the transmitting RIP v2 node to other RIP v2 nodes Subnet Masks RIP v2 allocates a 4-octet field to associate a subnet mask to a destination IP address. Next Hop IP addresses The inclusion of a Next Hop identification field helps make RIP v2 more efficient than RIP v1 by preventing unnecessary hops. Multicasting RIP v2 messages Multicasting is a technique for simultaneously advertising routing information to multiple RIP or RIP v2 devices.

RIP v2 message format

Address Family Identifier (AFI) IP = 2
The only exception is a request for a full routing table of a router or host, in which case it will be set to zero.

RIP v2 message format

Route Tag - provides a way to differentiate between internal and external routes.

External routes are those that have been redistributed into the RIP v2.

Next Hop - IP address of a better next hop if one exists.

Next hop on same subnet, that is metrically closer to the destination than the advertising router.

Metric - how many internetwork hops, between 1 and 15 for a valid route, or 16 for an unreachable route.

Compatibility with RIP v1

RFC 1723 defines a compatibility switch with four settings, which allows versions 1 and 2 to interoperate:
RIP v1 - Only RIP v1 messages are transmitted RIP v1 Compatibility - RIP v2 will broadcast its messages instead of multicast them so that RIP v1 may receive them RIP v2 - RIP v2 messages are multicast to destination address 224.0.0.9 None - no updates are sent

Authentication
Authentication is supported by modifying what would normally be the first route entry of the RIP message

The Authentication Type for simple password authentication is two (0x0002) The remaining 16 octets carry an alphanumeric password of up to 16 characters.

Authentication

RFC 1723 describes only simple password authentication Cisco IOS provides the option of using MD5 authentication instead of simple password authentication. Cisco uses the first and last route entry spaces for MD5 authentication purposes. MD5 computes a 128-bit hash value from a plain text message of arbitrary length and a password.

Authentication

Limitations of RIPv2

Slow convergence
RIPv2 continues to rely on counting to infinity as a means of resolving certain error conditions within the network.

Dependent upon holddown timers to reduce the possibility of routing loops.

Limitations of RIPv2

Perhaps the single greatest limitation that RIPv2 inherited from RIP is that its interpretation of infinity remained at 16. Redistributed RIPv2 static cost metrics. The default value of 1 is just like RIP.

This metric remains constant, and can only be changed by the administrator.

Basic RIPv2 configuration

Basic RIPv2 configuration

Other: passive interface command stops the router from sending updates to a particular neighbor, but the router continues to listen and use routing updates from that neighbor.
Router(config-router)# passiveinterface interface Default behavior of version 1 restored: Router(config-router)# no version

Compatibility with RIP v1

interface fastethernet0/0 ip address 192.168.50.129 255.255.255.192 ip rip send version 1 ip rip receive version 1 interface fastethernet0/1 ip address 172.25.150.193 255.255.255.240 ip rip send version 1 2 interface fastethernet0/2 ip address 172.25.150.225 225.255.255.240 router rip version 2 network 172.25.0.0 network 192.168.50.0

Interface FastEthernet0/0 is configured to send and receive RIP v1 updates. FastEthernet0/1 is configured to send both version 1 and 2 updates. FastEthernet0/2 has no special configuration and therefore sends and receives version 2 by default.

Configuring authentication

Configuring authentication
Router(config)#key chain Romeo Router(config-keychain)#key 1 Router(config-keychain-key)#key-string Juliet The password must be the same on both routers, but the name of the key can be different. Router(config)#interface fastethernet 0/0 Router(config-if)#ip rip authentication key-chain Romeo Router(config-if)#ip rip authentication mode md5

If the command ip rip authentication mode md5 is not added, the interface will use the default clear text authentication.

Show commands

show ip rip database

Router# show ip rip database 172.19.0.0/16 auto-summary 172.19.64.0/24 directly connected, Ethernet0 172.19.65.0/24 [1] via 172.19.70.36, 00:00:17, Serial1 [2] via 172.19.67.38, 00:00:25, Serial0 172.19.67.0/24 directly connected, Serial0 172.19.67.38/32 directly connected, Serial0 172.19.70.0/24 directly connected, Serial1 172.19.86.0/24[1] via 172.19.67.38, 00:00:25, Serial0 [1] via 172.19.70.36, 00:00:17, Serial1

The show ip rip database command to check summary address

entries in the RIP database.

Show commands

RIPv2: Sending and Receiving Updates

ISP#debug ip rip Includes mask RIP protocol debugging is on ISP#01:23:34: RIP: received v2 update from 192.168.4.22 on Serial1 01:23:34: 172.30.100.0/24 -> 0.0.0.0 in 1 hops 01:23:34: 172.30.110.0/24 -> 0.0.0.0 in 1 hops ISP# 01:23:38: RIP: received v2 update from 192.168.4.26 on Serial0 01:23:38: 172.30.2.0/24 -> 0.0.0.0 in 1 hops multicast 01:23:38: 172.30.1.0/24 -> 0.0.0.0 in 1 hops ISP# 01:24:31: RIP: sending v2 update to 224.0.0.9 via Ethernet0 (10.0.0.1) 01:24:31: 172.30.2.0/24 -> 0.0.0.0, metric 2, tag 0 01:24:31: 172.30.1.0/24 -> 0.0.0.0, metric 2, tag 0 01:24:31: 172.30.100.0/24 -> 0.0.0.0, metric 2, tag 0 01:24:31: 172.30.110.0/24 -> 0.0.0.0, metric 2, tag 0 01:24:31: 192.168.4.24/30 -> 0.0.0.0, metric 1, tag 0 01:24:31: 192.168.4.20/30 -> 0.0.0.0, metric 1, tag 0

Other RIPv2 Commands

Router(config-router)# neighbor ip-address

Defines a neighboring router with which to exchange unicast routing information. (RIPv1 or RIPv2)
Router(config-if)# ip rip send|receive version 1 | 2 | 1 2 Configures an interface to send/receive RIP Version 1 and/or Version 2 packets Router(config-if)# ip summary-address rip ip_address ip_network_mask Specifies the IP address and network mask that identify the routes to be summarized.