Routing Information Protocol

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

The Routing Information Protocol (RIP) is one of the oldest distance-vector routing protocols which employ the hop count as a routing metric. RIP prevents routing loops by implementing a limit on the number of hops allowed in a path from source to destination. The largest number of hops allowed for RIP is 15, which limits the size of networks that RIP can support.

RIP implements the split horizon, route poisoning and holddown mechanisms to prevent incorrect routing information from being propagated.

In RIPv1 router broadcast updates with their routing table every 30 seconds. In the early deployments, routing tables were small enough that the traffic was not significant. As networks grew in size, however, it became evident there could be a massive traffic burst every 30 seconds, even if the routers had been initialized at random times.

In most networking environments, RIP is not the preferred choice for routing as its time to converge and scalability are poor compared to EIGRP, OSPF, or IS-IS. However, it is easy to configure, because RIP does not require any parameters unlike other protocols.

RIP uses the User Datagram Protocol (UDP) as its transport protocol, and is assigned the reserved port number 520.[1]

Development of distance-vector routing[edit]

Based on the Bellman–Ford algorithm and the Ford–Fulkerson algorithm distant-vector routing protocols started to be implemented from 1969 onwards in data networks such as the ARPANET and CYCLADES. The predecessor of RIP was the Gateway Information Protocol (GWINFO) which was developed by Xerox in the mid-1970s to route its experimental network. As part of the Xerox Network Systems (XNS) protocol suite GWINFO transformed into the XNS Routing Information Protocol. This XNS RIP in turn became the basis for early routing protocols, such as Novell's IPX RIP, AppleTalk's Routing Table Maintenance Protocol (RTMP), and the IP RIP. The 1982 Berkley Software Distribution of the UNIX operating system implemented RIP in the routed daemon. The 4.2BSD release proved popular and became the basis for subsequent UNIX versions, which implemented RIP in the routed or gated daemon. Ultimately RIP had been extensively deployed before the standard written by Charles Hedrick was passed as RIPv1 in 1988.[2]

The RIP hop count[edit]

The routing metric used by RIP counts the number of routers that need to be passed to reach a destination IP network. The hop count 1 denotes a network that is directly connected to the router. 16 hops denote a network that is unreachable, according to the RIP hop limit.[3]

Versions[edit]

There are three standardised versions of the Routing Information Protocol: RIPv1 and RIPv2 for IPv4, and RIPng for IPv6.

RIP version 1[edit]

The original specification of RIP, defined in RFC 1058, was published in 1988.[4] When starting up, and every 30 seconds thereafter, a router with RIPv1 implementation broadcasts to 255.255.255.255 a request message through every RIPv1 enabled interface. Neighbouring routers receiving the request message respond with a RIPv1 segment, containing their routing table. The requesting router updates its own routing table, with the reachable IP network address, hop count and next hop, that is the router interface IP address from which the RIPv1 response was sent. As the requesting router receives updates from different neighbouring routers it will only update the reachable networks in its routing table, if it receives information about a reachable network it has not yet in its routing table or information that a network it has in its routing table is reachable with a lower hop count. Therefore a RIPv1 router will in most cases only have one entry for a reachable network, the one with the lowest hop count. If a router receives information from two different neighbouring router that the same network is reachable with the same hop count but via two different routes, the network will be entered into the routing table two times with different next hop routers. The RIPv1 enabled router will then perform what is known as equal-cost load balancing for IP packets.[5]

RIPv1 enabled routers not only request the routing tables of other routers every 30 seconds, they also listen to incoming requests from neighbouring routers and send their own routing table in turn. RIPv1 routing tables are therefore updated every 25 to 35 seconds.[6] The RIPv1 protocol adds a small random time variable to the update time, to avoid routing tables synchronising across a LAN.[7] It was thought, as a result of random initialization, the routing updates would spread out in time, but this was not true in practice. Sally Floyd and Van Jacobson showed in 1994 that, without slight randomization of the update timer, the timers synchronized over time.[8]

RIPv1 can be configured into silent mode, so that a router requests and processes neighbouring routing tables, and keeps its routing table and hop count for reachable networks up to date, but does not needlessly sends its own routing table into the network. Silent mode is commonly implemented to hosts.[9]

RIPv1 uses classful routing. The periodic routing updates do not carry subnet information, lacking support for variable length subnet masks (VLSM). This limitation makes it impossible to have different-sized subnets inside of the same network class. In other words, all subnets in a network class must have the same size. There is also no support for router authentication, making RIP vulnerable to various attacks.

RIP version 2[edit]

Due to the deficiencies of the original RIP specification, RIP version 2 (RIPv2) was developed in 1993[4] and last standardized in 1998 in RFC 2453[10] It included the ability to carry subnet information, thus supporting Classless Inter-Domain Routing (CIDR). To maintain backward compatibility, the hop count limit of 15 remained. RIPv2 has facilities to fully interoperate with the earlier specification if all Must Be Zero protocol fields in the RIPv1 messages are properly specified. In addition, a compatibility switch feature[10] allows fine-grained interoperability adjustments.

In an effort to avoid unnecessary load on hosts that do not participate in routing, RIPv2 multicasts the entire routing table to all adjacent routers at the address 224.0.0.9, as opposed to RIPv1 which uses broadcast. Unicast addressing is still allowed for special applications.

(MD5) authentication for RIP was introduced in 1997.[11][12]

RIPv2 is Internet Standard STD56 (which is RFC 2453).

Route tags were also added in RIP version 2. This functionality allows a distinction between routes learned from the RIP protocol and routes learned from other protocols.

RIPng[edit]

RIPng (RIP next generation), defined in RFC 2080,[13] is an extension of RIPv2 for support of IPv6, the next generation Internet Protocol. The main differences between RIPv2 and RIPng are:

  • Support of IPv6 networking.
  • While RIPv2 supports RIPv1 updates authentication, RIPng does not. IPv6 routers were, at the time, supposed to use IPsec for authentication.
  • RIPv2 encodes the next-hop into each route entry, RIPng requires specific encoding of the next hop for a set of route entries.

RIPng sends updates on UDP port 521 using the multicast group FF02::9.

RIP messages between routers[edit]

RIP messages use the User Datagram Protocol on port 520 and all RIP messages exchanged between routers are encapsulated in a UDP segment.[14]

RIPv1 Messages[edit]

RIP defined two types of messages:[15]

  1. Request Message: asking a neigbouring IPv1 enabled router to send its routing table.[16]
  2. Response Message: carries the routing table of a router.[17]

Timers[edit]

The routing information protocol uses the following timers as part of its operation:[18]

  • Update Timer: controls the interval between two gratuitous Response Messages. By default the value is 30 seconds. The response message is broadcast to all its RIP enabled interface.[18]
  • Invalid Timer: The invalid timer specifies how long a routing entry can be in the routing table without being updated. This is also called as expiration Timer. By default, the value is 180 seconds. After the timer expires the hop count of the routing entry will be set to 16, marking the destination as unreachable.[18]
  • Flush Timer: The flush timer controls the time between the route is invalidated or marked as unreachable and removal of entry from the routing table. By default the value is 240 seconds. This is 60 seconds longer than Invalid timer. So for 60 seconds the router will be advertising about this unreachable route to all its neighbours. This timer must be set to a higher value than the invalid timer.[18]
  • Holddown Timer: The hold-down timer is started per route entry, when the hop count is changing from lower value to higher value. This allows the route to get stabilized. During this time no update can be done to that routing entry. This is not part of the RFC 1058. This is Cisco's implementation. The default value of this timer is 180 seconds.[18]

Limitations[edit]

  • The hop count cannot exceed 15, or routes will be dropped.
  • Variable Length Subnet Masks are not supported by RIP version 1 (which is obsolete).
  • RIP has slow convergence and count to infinity problems.[19]

Implementations[edit]

  • Cisco IOS, software used in Cisco routers (supports version 1, version 2 and RIPng)
  • Cisco NX-OS software used in Cisco Nexus data center switches (supports RIPv1 and RIPv2)
  • Junos software used in Juniper routers, switches, and firewalls (supports RIPv1 and RIPv2)
  • Routing and Remote Access, a Windows Server feature, contains RIP support
  • Quagga, a free open source routing software suite based on GNU Zebra
  • BIRD, a free open source routing software suite
  • Zeroshell, a free open source routing software suite
  • A RIP implementation first introduced in 4.2BSD, routed, survives in several of its descendants, including FreeBSD[20] and NetBSD.[21]
  • OpenBSD introduced a new implementation, ripd, in version 4.1[22] and retired routed in version 4.4.
  • Netgear routers commonly offer a choice of two implementations of RIPv2;[23] these are labelled RIP_2M and RIP_2B. RIP_2M is the standard RIPv2 implementation using multicasting - which requires all routers on the network to support RIPv2 and multicasting, whereas RIP_2B sends RIPv2 packets using subnet broadcasting - making it more compatible with routers that do not support multicasting, including RIPv1 routers.

Similar protocols[edit]

Cisco's proprietary Interior Gateway Routing Protocol (IGRP) was a somewhat more capable protocol than RIP. It belongs to the same basic family of distance-vector routing protocols. Cisco has ceased support and distribution of IGRP in their router software. It was replaced by the Enhanced Interior Gateway Routing Protocol (EIGRP) which is a completely new design. While EIGRP still uses a distance-vector model, it relates to IGRP only in using the same routing metrics. IGRP supports multiple metrics for each route, including bandwidth, delay, load, MTU, and reliability.

See also[edit]

References[edit]

  1. ^ "Port Numbers" (plain text). The Internet Assigned Numbers Authority (IANA). 22 May 2008. Retrieved 25 May 2008. 
  2. ^ Jeff Doyle & Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 169. ISBN 9781587052026. 
  3. ^ Jeff Doyle & Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 170. ISBN 9781587052026. 
  4. ^ RFC 1058, Routing Information Protocol, C. Hendrik, The Internet Society (June 1988)
  5. ^ Jeff Doyle & Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 170. ISBN 9781587052026. 
  6. ^ Jeff Doyle & Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 170. ISBN 9781587052026. 
  7. ^ Jeff Doyle & Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 171. ISBN 9781587052026. 
  8. ^ The Synchronization of Periodic Routing Messages, S. Floyd & V. Jacobson,April 1994
  9. ^ Jeff Doyle & Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 175. ISBN 9781587052026. 
  10. ^ a b RFC 2453, RIP Version 2, G. Malkin, The Internet Society (November 1998)
  11. ^ RFC 2082, RIP-2 MD5 Authentication, F. Baker, R. Atkinson, The Internet Society (January 1997)
  12. ^ RFC 4822, RIPv2 Cryptographic Authentication, R. Atkinson, M. Fanto, The Internet Society (January 2007)
  13. ^ RFC 2080, RIPng for IPv6, G. Malkin, R. Minnear, The Internet Society (January 1997)
  14. ^ Jeff Doyle & Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 170. ISBN 9781587052026. 
  15. ^ Jeff Doyle & Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 170. ISBN 9781587052026. 
  16. ^ Jeff Doyle & Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 170. ISBN 9781587052026. 
  17. ^ Jeff Doyle & Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 170. ISBN 9781587052026. 
  18. ^ a b c d e Balchunas, Aaron. "Routing Information Protocol (RIP v1.03)" (PDF). http://www.routeralley.com. Retrieved 25 April 2014. 
  19. ^ C. Hendrik. "RFC 1058 Section 2.2". Routing Information Protocol. The Internet Society. 
  20. ^ "routed, rdisc — network RIP and router discovery routing daemon". FreeBSD manual pages. 
  21. ^ "routed, rdisc — network RIP and router discovery routing daemon". NetBSD manual pages. 
  22. ^ "ripd — Routing Information Protocol daemon". OpenBSD manual pages. 
  23. ^ "How do I change the LAN TCP/IP settings on my Nighthawk router?". Netgear Support pages. 

Further reading[edit]

  • Malkin, Gary Scott (2000). RIP: An Intra-Domain Routing Protocol. Addison-Wesley Longman. ISBN 0-201-43320-6.
  • Edward A. Taft, Gateway Information Protocol (revised) (Xerox Parc, Palo Alto, May, 1979)
  • Xerox System Integration Standard - Internet Transport Protocols (Xerox, Stamford, 1981)

External links[edit]