Skip to main content

When was the Routing Information Protocol Invented?



Hedrick of Rutgers University invented the Routing Information Protocol in the summer of 1988. Since then it has become the most common routing protocol on LANs and WANs and continues to be used today. Hedrick’s work was based on the Unix computer program “routed,” which was distributed with the 4.3 version of the BSD branch of the OS. At that time, the “routed” protocol was the de-facto standard for research laboratories to communicate via network gateways. The RIP protocols use the Bellman-Ford algorithm for distance vector computation and other work completed as early as 1969 on the ARPANET. The PUP protocol preceded Hedrick’s work and later became the RIP.
How does the Routing Information Protocol Work?

RIP relies on a routing database that stores information on the fastest routes that exist between destinations on the network. This lets each router tell others the fastest route(s) and uses an update algorithm that revises route updates for each router based on the latest information from neighboring routers. Each database stores the IP address, gateway, distance, route change flag, and timers for each destination within a given routers purview.
What is the Routing Information Algorithm?

The RIP algorithm requires each router to transmit an update message on regular intervals that describes its routing database’s contents to all of the routers it communicates with. Sometimes routers have to send this message as often as twice a minute in order to keep the networks’ routers updated with the most up-to-date information on the computers and routers that are currently on the network. Once a router discovers that a neighboring one has a shorter or faster path to a given destination, it revises its local database to include this faster path. This new path is then sent to the neighboring routers through the protocol’s update process until the entire network is updated. The RIP protocol uses the UDP data transmission packet to improve efficiency since it can rely on sending future updates on regular intervals.

Popular posts from this blog

HOW TO EDIT THE BCD REGISTRY FILE

The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N