Routing Information Protocol

<h2 id="development-of-distance-vector-routing">Development of distance-vector routing</h2>
Based on the <a href="/facts/Bellman%25E2%2580%2593Ford_algorithm/Sx6INcdr">Bellman–Ford algorithm</a> and the <a href="/facts/Ford%25E2%2580%2593Fulkerson_algorithm/wwk3tw52">Ford–Fulkerson algorithm</a>, <a href="/facts/Distance-vector_routing_protocol/x7caJ1QI">distance-vector routing protocols</a> started to be implemented from 1969 onwards in <a href="/facts/Data_networks/3w5RM99p">data networks</a> such as the <a href="/facts/ARPANET/LyMGWurJ">ARPANET</a> and <a href="/facts/CYCLADES/kJX66P6D">CYCLADES</a>. The predecessor of RIP was the Gateway Information Protocol (GWINFO) which was developed by <a href="/facts/Xerox/qyxVVqaa">Xerox</a> in the mid-1970s to route its experimental network. As part of the <a href="/facts/Xerox_Network_Systems/2pfVfFgY">Xerox Network Systems</a> (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 <a href="/facts/Novell/lABGMT7U">Novell</a>'s IPX RIP, <a href="/facts/AppleTalk/6j3NRgTl">AppleTalk</a>'s Routing Table Maintenance Protocol (RTMP), and the IP RIP. The 1982 <a href="/facts/Berkeley_Software_Distribution/XQKcURrh">Berkeley Software Distribution</a> of the <a href="/facts/UNIX/0pNL2seI">UNIX</a> operating system implemented RIP in the routed <a href="/facts/Daemon_(computing)/bzuEVGGX">daemon</a>. 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<a class="footnote-ref" id="fnref:2" href="#fn:2">2</a> before the standard, written by Charles Hedrick, was passed as RIPv1 in 1988.<a class="footnote-ref" id="fnref:3" href="#fn:3">3</a>

<h2 id="the-rip-hop-count">The RIP hop count</h2>
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 0 denotes a network that is directly connected to the router. 16 hops denote a network that is unreachable, according to the RIP hop limit.<a class="footnote-ref" id="fnref:4" href="#fn:4">4</a>

<h2 id="versions">Versions</h2>
There are three standardized versions of the Routing Information Protocol: RIPv1 and RIPv2 for <a href="/facts/IPv4/bnQ5MEqm">IPv4</a>, and RIPng for <a href="/facts/IPv6/d4dg7kIL">IPv6</a>.

<h3>RIP version 1</h3>
The original specification of RIP was published in 1988.<a class="footnote-ref" id="fnref:5" href="#fn:5">5</a> When starting up, and every 30 seconds thereafter, a router with RIPv1 implementation <a href="/facts/Broadcasting_(networking)/NRj7gHre">broadcasts</a> 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 <a href="/facts/Routing_table/tufajWvV">routing table</a>. 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.<a class="footnote-ref" id="fnref:6" href="#fn:6">6</a>
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.<a class="footnote-ref" id="fnref:7" href="#fn:7">7</a> The RIPv1 protocol adds a small random time variable to the update time, to avoid routing tables synchronizing across a LAN.<a class="footnote-ref" id="fnref:8" href="#fn:8">8</a> 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 <a href="/facts/Van_Jacobson/WD2r6Mll">Van Jacobson</a> showed in 1994 that, without slight randomization of the update timer, the timers synchronized over time.<a class="footnote-ref" id="fnref:9" href="#fn:9">9</a>
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 send its own routing table into the network. Silent mode is commonly implemented to hosts.<a class="footnote-ref" id="fnref:10" href="#fn:10">10</a>
RIPv1 uses <a href="/facts/Classful_address/A2gWJtyX">classful</a> routing. The periodic routing updates do not carry <a href="/facts/Subnetwork/s1rQsNDv">subnet</a> information, lacking support for <a href="/facts/VLSM/YU0SEmfp">variable length subnet masks</a> (VLSM). This limitation makes it impossible to have different-sized <a href="/facts/Subnetwork/s1rQsNDv">subnets</a> inside of the same <a href="/facts/Network_class/A2gWJtyX">network class</a>. 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.

<h3>RIP version 2</h3>
Due to the deficiencies of the original RIP specification, RIP version 2 (RIPv2) was developed in 1993,<a class="footnote-ref" id="fnref:11" href="#fn:11">11</a> published in 1994,<a class="footnote-ref" id="fnref:12" href="#fn:12">12</a> and declared <a href="/facts/Internet_Standard/LT6VEfhg">Internet Standard</a> 56 in 1998.<a class="footnote-ref" id="fnref:13" href="#fn:13">13</a> It included the ability to carry subnet information, thus supporting <a href="/facts/Classless_Inter-Domain_Routing/YU0SEmfp">Classless Inter-Domain Routing</a> (CIDR). To maintain <a href="/facts/Backward_compatibility/FbHFBu5y">backward compatibility</a>, 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<a class="footnote-ref" id="fnref:14" href="#fn:14">14</a> allows fine-grained interoperability adjustments.
In an effort to avoid unnecessary load on hosts that do not participate in routing, RIPv2 <a href="/facts/Multicast/D9IspSfl">multicasts</a> the entire routing table to all adjacent routers at the address <a href="/facts/Multicast_address/cIau2Hee">224.0.0.9</a>, as opposed to RIPv1 which uses <a href="/facts/Broadcasting_(networking)/NRj7gHre">broadcast</a>. <a href="/facts/Unicast/PHStTfFe">Unicast</a> addressing is still allowed for special applications.
(<a href="/facts/MD5/8WIXb9Dq">MD5</a>) authentication for RIP was introduced in 1997.<a class="footnote-ref" id="fnref:15" href="#fn:15">15</a><a class="footnote-ref" id="fnref:16" href="#fn:16">16</a>
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.

<h3>RIPng</h3>
RIPng (RIP next generation) is an extension of RIPv2 for support of <a href="/facts/IPv6/d4dg7kIL">IPv6</a>, the next generation <a href="/facts/Internet_Protocol/Qq6VeEal">Internet Protocol</a>.<a class="footnote-ref" id="fnref:17" href="#fn:17">17</a> The main differences between RIPv2 and RIPng are:

<ul><li>Support of IPv6 networking.</li>
<li>While RIPv2 supports RIPv1 updates authentication, RIPng does not. IPv6 routers were, at the time, supposed to use <a href="/facts/IPsec/01MwcET1">IPsec</a> for authentication.</li>
<li>RIPv2 encodes the next-hop into each route entry, RIPng requires specific encoding of the next hop for a set of route entries.</li></ul>
RIPng sends updates on UDP port 521 using the multicast group ff02::9.

<h2 id="rip-messages-between-routers">RIP messages between routers</h2>
RIP messages use the <a href="/facts/User_Datagram_Protocol/dxLU0D6q">User Datagram Protocol</a> on port 520 and all RIP messages exchanged between routers are encapsulated in a UDP datagram.<a class="footnote-ref" id="fnref:18" href="#fn:18">18</a>

<h3>RIPv1 Messages</h3>
RIP defined two types of messages:

Request Message
Asking a neighbouring RIPv1 enabled router to send its routing table.
Response Message
Carries the routing table of a router.
<h2 id="timers">Timers</h2>
The routing information protocol uses the following timers as part of its operation:<a class="footnote-ref" id="fnref:19" href="#fn:19">19</a>

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.<a class="footnote-ref" id="fnref:20" href="#fn:20">20</a>
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.<a class="footnote-ref" id="fnref:21" href="#fn:21">21</a>
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.<a class="footnote-ref" id="fnref:22" href="#fn:22">22</a>
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 <a href="/facts/Cisco_Systems/ocDgQt6T">Cisco's</a> implementation. The default value of this timer is 180 seconds.<a class="footnote-ref" id="fnref:23" href="#fn:23">23</a>
<h2 id="limitations">Limitations</h2>
<ul><li>The hop count cannot exceed 15, or routes will be dropped.</li>
<li>Variable Length Subnet Masks are not supported by RIP version 1 (which is obsolete).</li>
<li>RIP has slow convergence and <a href="/facts/Count_to_infinity/x7caJ1QI">count to infinity</a> problems.<a class="footnote-ref" id="fnref:24" href="#fn:24">24</a></li></ul>
<h2 id="implementations">Implementations</h2>
<ul><li><a href="/facts/Cisco_IOS/jwcRuzX8">Cisco IOS</a>, software used in Cisco routers (supports version 1, version 2 and RIPng)</li>
<li>Cisco NX-OS software used in Cisco Nexus data center switches (supports RIPv2 only<a class="footnote-ref" id="fnref:25" href="#fn:25">25</a>)</li>
<li><a href="/facts/Junos/osUAt6qS">Junos</a> software used in Juniper routers, switches, and firewalls (supports RIPv1 and RIPv2)</li>
<li>Routing and Remote Access, a <a href="/facts/Windows_Server_2003/3vIJam5L">Windows Server</a> feature, contains RIP support</li>
<li><a href="/facts/Quagga_(software)/qJy65FnE">Quagga</a>, a <a href="/facts/Free_software/IaoVtJXn">free</a> <a href="/facts/Open_source_software/HzTaB8E9">open source software</a> routing suite based on <a href="/facts/GNU_Zebra/Wa8xmgfh">GNU Zebra</a></li>
<li><a href="/facts/Bird_Internet_routing_daemon/zuFMMlMf">BIRD</a>, a <a href="/facts/Free_software/IaoVtJXn">free</a> <a href="/facts/Open_source_software/HzTaB8E9">open source software</a> routing suite</li>
<li><a href="/facts/Zeroshell/QsuND1qB">Zeroshell</a>, a <a href="/facts/Free_software/IaoVtJXn">free</a> <a href="/facts/Open_source_software/HzTaB8E9">open source software</a> routing suite</li>
<li>A RIP implementation first introduced in <a href="/facts/Berkeley_Software_Distribution/XQKcURrh">4.2BSD</a>, routed, survives in several of its descendants, including <a href="/facts/FreeBSD/RKsFTm7F">FreeBSD</a><a class="footnote-ref" id="fnref:26" href="#fn:26">26</a> and <a href="/facts/NetBSD/PTm5HWls">NetBSD</a>.<a class="footnote-ref" id="fnref:27" href="#fn:27">27</a></li>
<li><a href="/facts/OpenBSD/xmPS9tek">OpenBSD</a> introduced a new implementation, ripd, in version 4.1<a class="footnote-ref" id="fnref:28" href="#fn:28">28</a> and retired routed in version 4.4.</li>
<li><a href="/facts/Netgear/jCMtPgpD">Netgear</a> routers commonly offer a choice of two implementations of RIPv2;<a class="footnote-ref" id="fnref:29" href="#fn:29">29</a> 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.</li>
<li><a href="/facts/Huawei/Qwu0tbnL">Huawei</a> HG633 ADSL/VDSL routers support passive and active routing with RIP v1 & v2 on the LAN and WAN side.</li></ul>
<h2 id="similar-protocols">Similar protocols</h2>
<a href="/facts/Cisco/ocDgQt6T">Cisco</a>'s proprietary <a href="/facts/Interior_Gateway_Routing_Protocol/L6w91wYM">Interior Gateway Routing Protocol</a> (IGRP) was a somewhat more capable protocol than RIP. It belongs to the same basic family of <a href="/facts/Distance-vector_routing_protocol/x7caJ1QI">distance-vector routing protocols</a>. 
Cisco has ceased support and distribution of IGRP in their router software. It was replaced by the <a href="/facts/Enhanced_Interior_Gateway_Routing_Protocol/KIcfLjbh">Enhanced Interior Gateway Routing Protocol</a> (EIGRP) which is a completely new design. While EIGRP still uses a distance-vector model, it relates to IGRP only in using the same composite routing metric. Both IGRP and EIGRP calculated a single composite metric for each route, from a formula of five variables: <a href="/facts/Bandwidth_(computing)/lY6Tb4gX">bandwidth</a>, <a href="/facts/Network_delay/JK7jmoJu">delay</a>, <a href="/facts/Reliability_(computer_networking)/v3kGvfvs">reliability</a>, <a href="/facts/Load_(computing)/J2v5XarQ">load</a>, and <a href="/facts/Maximum_transmission_unit/l2FdKoLa">MTU</a>; though on Cisco routers, by default, only bandwidth and delay are used in this calculation.

<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Convergence_(routing)/p9Y4xIlJ">Convergence (routing)</a></li></ul>

<h2 id="further-reading">Further reading</h2>
<ul><li>Malkin, Gary Scott (2000). RIP: An Intra-Domain Routing Protocol. Addison-Wesley Longman. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 0-201-43320-6.</li>
<li>Edward A. Taft, Gateway Information Protocol (revised) (Xerox Parc, Palo Alto, May, 1979)</li>
<li>Xerox System Integration Standard - Internet Transport Protocols (Xerox, Stamford, 1981)</li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1">"Service Name and Transport Protocol Port Number Registry". www.iana.org. The Internet Assigned Numbers Authority (IANA). p. 10. Retrieved 25 February 2022. <a href="https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?&page=10" target="_blank">https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?&page=10</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></li>
<li id="fn:2">Jeff Doyle; Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 169. ISBN 9781587052026. <a href="9781587052026" target="_blank">9781587052026</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></li>
<li id="fn:3">C. Hedrick (June 1988). Routing Information Protocol. Network Working Group. doi:10.17487/RFC1058. RFC 1058. Historic. Updated by RFC 1388 and 1723.
 <a href="https://datatracker.ietf.org/doc/html/rfc1058" target="_blank">https://datatracker.ietf.org/doc/html/rfc1058</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></li>
<li id="fn:4">Jeff Doyle; Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 170. ISBN 9781587052026. <a href="9781587052026" target="_blank">9781587052026</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></li>
<li id="fn:5">C. Hedrick (June 1988). Routing Information Protocol. Network Working Group. doi:10.17487/RFC1058. RFC 1058. Historic. Updated by RFC 1388 and 1723.
 <a href="https://datatracker.ietf.org/doc/html/rfc1058" target="_blank">https://datatracker.ietf.org/doc/html/rfc1058</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></li>
<li id="fn:6">Jeff Doyle; Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 170. ISBN 9781587052026. <a href="9781587052026" target="_blank">9781587052026</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></li>
<li id="fn:7">Jeff Doyle; Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 170. ISBN 9781587052026. <a href="9781587052026" target="_blank">9781587052026</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></li>
<li id="fn:8">Jeff Doyle; Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 171. ISBN 9781587052026. <a href="9781587052026" target="_blank">9781587052026</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></li>
<li id="fn:9">The Synchronization of Periodic Routing Messages, S. Floyd & V. Jacobson,April 1994 <a href="http://www.icir.org/floyd/papers/sync_94.pdf" target="_blank">http://www.icir.org/floyd/papers/sync_94.pdf</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></li>
<li id="fn:10">Jeff Doyle; Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 175. ISBN 9781587052026. <a href="9781587052026" target="_blank">9781587052026</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></li>
<li id="fn:11">Jeff Doyle; Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 170. ISBN 9781587052026. <a href="9781587052026" target="_blank">9781587052026</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></li>
<li id="fn:12">G. Malkin (November 1994). RIP Version 2 - Carrying Additional Information. Network Working Group. doi:10.17487/RFC1723. RFC 1723. Obsolete. Obsoleted by RFC 2453. Obsoletes RFC 1388. Updates RFC 1058.
 <a href="https://datatracker.ietf.org/doc/html/rfc1723" target="_blank">https://datatracker.ietf.org/doc/html/rfc1723</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></li>
<li id="fn:13">G. Malkin (November 1998). RIP Version 2. Network Working Group. doi:10.17487/RFC2453. STD 53. RFC 2453. Internet Standard 53. Obsoletes RFC 1723 and 1388. Updated by RFC 4822.
 <a href="https://datatracker.ietf.org/doc/html/rfc2453" target="_blank">https://datatracker.ietf.org/doc/html/rfc2453</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></li>
<li id="fn:14">G. Malkin (November 1998). RIP Version 2. Network Working Group. doi:10.17487/RFC2453. STD 53. RFC 2453. Internet Standard 53. Obsoletes RFC 1723 and 1388. Updated by RFC 4822.
 <a href="https://datatracker.ietf.org/doc/html/rfc2453" target="_blank">https://datatracker.ietf.org/doc/html/rfc2453</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></li>
<li id="fn:15">F. Baker; R. Atkinson (January 1997). RIP-2 MD5 Authentication. Network Working Group. doi:10.17487/RFC2082. RFC 2082. Obsolete. Obsoleted by RFC 4822.
 <a href="/wiki/Fred_Baker_(IETF_chair)" target="_blank">/wiki/Fred_Baker_(IETF_chair)</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></li>
<li id="fn:16">R. Atkinson; M. Fanto (February 2007). RIPv2 Cryptographic Authentication. Network Working Group. doi:10.17487/RFC4822. RFC 4822. Proposed Standard. Obsoletes RFC 2082. Updates RFC 2453.
 <a href="https://datatracker.ietf.org/doc/html/rfc4822" target="_blank">https://datatracker.ietf.org/doc/html/rfc4822</a> <a href="#fnref:16" class="footnote-back-ref">↩</a></li>
<li id="fn:17">G. Malkin; R. Minnear (January 1997). RIPng for IPv6. Network Working Group. doi:10.17487/RFC2080. RFC 2080. Proposed Standard.
 <a href="https://datatracker.ietf.org/doc/html/rfc2080" target="_blank">https://datatracker.ietf.org/doc/html/rfc2080</a> <a href="#fnref:17" class="footnote-back-ref">↩</a></li>
<li id="fn:18">Jeff Doyle; Jennifer Carroll (2005). CCIE Professional Development: Routing TCP/IP Volume I, Second Edition. ciscopress.com. p. 170. ISBN 9781587052026. <a href="9781587052026" target="_blank">9781587052026</a> <a href="#fnref:18" class="footnote-back-ref">↩</a></li>
<li id="fn:19">Balchunas, Aaron. "Routing Information Protocol (RIP v1.03)" (PDF). routeralley.com. Archived (PDF) from the original on 10 October 2022. Retrieved 25 April 2014. <a href="http://www.routeralley.com/guides/rip.pdf" target="_blank">http://www.routeralley.com/guides/rip.pdf</a> <a href="#fnref:19" class="footnote-back-ref">↩</a></li>
<li id="fn:20">Balchunas, Aaron. "Routing Information Protocol (RIP v1.03)" (PDF). routeralley.com. Archived (PDF) from the original on 10 October 2022. Retrieved 25 April 2014. <a href="http://www.routeralley.com/guides/rip.pdf" target="_blank">http://www.routeralley.com/guides/rip.pdf</a> <a href="#fnref:20" class="footnote-back-ref">↩</a></li>
<li id="fn:21">Balchunas, Aaron. "Routing Information Protocol (RIP v1.03)" (PDF). routeralley.com. Archived (PDF) from the original on 10 October 2022. Retrieved 25 April 2014. <a href="http://www.routeralley.com/guides/rip.pdf" target="_blank">http://www.routeralley.com/guides/rip.pdf</a> <a href="#fnref:21" class="footnote-back-ref">↩</a></li>
<li id="fn:22">Balchunas, Aaron. "Routing Information Protocol (RIP v1.03)" (PDF). routeralley.com. Archived (PDF) from the original on 10 October 2022. Retrieved 25 April 2014. <a href="http://www.routeralley.com/guides/rip.pdf" target="_blank">http://www.routeralley.com/guides/rip.pdf</a> <a href="#fnref:22" class="footnote-back-ref">↩</a></li>
<li id="fn:23">Balchunas, Aaron. "Routing Information Protocol (RIP v1.03)" (PDF). routeralley.com. Archived (PDF) from the original on 10 October 2022. Retrieved 25 April 2014. <a href="http://www.routeralley.com/guides/rip.pdf" target="_blank">http://www.routeralley.com/guides/rip.pdf</a> <a href="#fnref:23" class="footnote-back-ref">↩</a></li>
<li id="fn:24">C. Hendrik (June 1988). "RFC 1058 Section 2.2". Routing Information Protocol. The Internet Society. doi:10.17487/RFC1058. <a href="https://tools.ietf.org/html/rfc1058" target="_blank">https://tools.ietf.org/html/rfc1058</a> <a href="#fnref:24" class="footnote-back-ref">↩</a></li>
<li id="fn:25">"Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x - Configuring RIP [Cisco Nexus 9000 Series Switches]". <a href="https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/6-x/unicast/configuration/guide/l3_cli_nxos/l3_rip.html" target="_blank">https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/6-x/unicast/configuration/guide/l3_cli_nxos/l3_rip.html</a> <a href="#fnref:25" class="footnote-back-ref">↩</a></li>
<li id="fn:26">"routed, rdisc – network RIP and router discovery routing daemon". FreeBSD manual pages. <a href="http://www.freebsd.org/cgi/man.cgi?query=routed&sektion=8" target="_blank">http://www.freebsd.org/cgi/man.cgi?query=routed&sektion=8</a> <a href="#fnref:26" class="footnote-back-ref">↩</a></li>
<li id="fn:27">"routed, rdisc – network RIP and router discovery routing daemon". NetBSD manual pages. <a href="http://netbsd.gw.com/cgi-bin/man-cgi?routed+8+NetBSD-current" target="_blank">http://netbsd.gw.com/cgi-bin/man-cgi?routed+8+NetBSD-current</a> <a href="#fnref:27" class="footnote-back-ref">↩</a></li>
<li id="fn:28">"ripd – Routing Information Protocol daemon". OpenBSD manual pages. <a href="https://man.openbsd.org/ripd.8" target="_blank">https://man.openbsd.org/ripd.8</a> <a href="#fnref:28" class="footnote-back-ref">↩</a></li>
<li id="fn:29">"How do I change the LAN TCP/IP settings on my Nighthawk router?". Netgear Support pages. <a href="http://kb.netgear.com/app/answers/detail/a_id/24088" target="_blank">http://kb.netgear.com/app/answers/detail/a_id/24088</a> <a href="#fnref:29" class="footnote-back-ref">↩</a></li>
</ol>

Routing Information Protocol open-in-new

Routing Information Protocol