History
The routing algorithm used in RIP, the Bellman-Ford algorithm, was first deployed in a computer network in 1969, as the initial routing algorithm of the ARPANET.
The earliest version of the specific protocol that became RIP was the Gateway Information Protocol, part of Xerox Parc's PARC Universal Packet internetworking protocol suite. A later version, named the Routing Information Protocol, was part of Xerox Network Services.
A version of RIP which supported the Internet Protocol (IP) was later included in the Berkeley Software Distribution (BSD) of the Unix operating system as the routed daemon, and various other vendors would implement their own implementations of the routing protocol. Eventualy RFC 1058 was issued to unify the various implementations under a single standard.
Technical detail
RIP is a distance-vector routing protocol, which employs the hop count as a routing metric. The maximum number of hops allowed with RIP is 15, and the hold down time is 120 seconds. Each RIP router transmits full updates every 30 seconds by default, generating large amounts of network traffic in lower bandwidth networks. It runs above the network layer of the Internet protocol suite, using UDP port 520 to carry its data. A mechanism called split horizon with limited poison reverse is used to avoid routing loops. Routers of some brands also use a holddown mechanism known as heuristics, whose usefulness is arguable and is not a part of the standard protocol.
In many current networking environments RIP would not be the first choice for routing as its convergence times and scalability are poor compared to EIGRP, OSPF, or IS-IS (the latter two being link-state routing protocols), and the hop limit severely limits the size of network it can be used in. On the other hand, it is easier to configure
Versions
There are three versions of RIP, RIPv1, RIPv2, and RIPng.
RIPv1, defined in RFC 1058, uses classful routing. The routing updates do not carry subnet information, lacking support for variable length subnet masks. 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 be the same size. There is also no support for router authentication, making RIPv1 slightly vulnerable to various attacks.
Due to the above deficiencies of RIPv1, RIPv2 was developed in 1994 and included the ability to carry subnet information, thus supporting Classless Inter-Domain Routing. However to maintain backwards compatibility the 15 hop count limit remained. Rudimentary plain text authentication was added to secure routing updates; later, MD5 authentication was defined in RFC 2082.
RIPv2 is specified in RFC 2453 or STD 56.
RIPng, defined in RFC 2080, is an extension of the original protocol to support IPv6.
2006-12-12 17:51:34
·
answer #1
·
answered by abhi 2
·
0⤊
0⤋
I assume you've run some version of a show ip command, there should have been a line(s) above this one if that is the case which relates more fully to the routing table for the network shown. The beginning R states the source of the routing information, in this case, R being RIP. 190.158.2.2 is the first part of the route and the 32 is the subnet number. The first number in the brackets, 120, relates to administrative distance and the second, the 3, is the metric value for the route. 190.158.0.1 is the next hop IP address. 45 is your time as far as age of the route and the Fastethernet0/0 is the outgoing interface.
2016-05-22 23:58:13
·
answer #2
·
answered by ? 4
·
0⤊
0⤋
RIP isn't an "internal routing protocol." The name stands for Routing Internet Protocol. It's the simplest of distance-vector routing protocols. Routing decisions are made solely on hop count. A one-hop link running at 56k would be chosen over 2 hops across T-3 links.
2006-12-12 05:49:12
·
answer #3
·
answered by Bostonian In MO 7
·
0⤊
1⤋
Pls read RFC on RIP.They are the best for an intermediate/advanced user.
http://www.rfc-editor.org/cgi-bin/rfcsearch.pl
RIP Version 2 --- RFC 2453
2006-12-12 17:48:07
·
answer #4
·
answered by Anonymous
·
0⤊
0⤋
uh, actually study for your CCNA test?
2006-12-12 04:45:36
·
answer #5
·
answered by wardriver 2
·
0⤊
0⤋