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

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T

Fixing Tanzu Kubernetes Pod to External Services Connectivity Issues with NSX-T Last month I got a call from a customer who was pulling their hair out over a networking issue. They had just deployed VMware Tanzu Kubernetes Grid on their vSphere with Tanzu environment, everything looked good in the dashboards, all pods were running, but their applications inside the pods could not reach external databases running on traditional VMs in the same datacenter. The frustrating part was that some pods could reach external services perfectly fine, while others would just timeout. There was no clear pattern. Let me tell you how we figured this out and fixed it. The Initial Problem Here is what the customer setup looked like: vSphere 8.0 with Tanzu enabled NSX-T 4.1.2 for networking Three Tanzu Kubernetes clusters running different microservices applications External PostgreSQL database running on traditional VMs (non-Kubernetes) External API services running on another se...

Troubleshooting vSAN Storage Policy Migration Failures in VMware Cloud Foundation 9.0

Recently I had a customer who migrated their VMware infrastructure from vSphere 7.0 to VMware Cloud Foundation 9.0. After the migration, they wanted to update their vSAN storage policies to take advantage of the new vSAN ESA (Express Storage Architecture) features. However, when they tried to change the storage policy for their production VMs, the operation kept failing with a cryptic error message. The error they were getting was: "Cannot complete operation due to insufficient resources to satisfy current storage policy." This was strange because they had plenty of disk space available. The vSAN cluster was only at 45% capacity, and all the hosts were healthy. Let me walk through how we troubleshooted and fixed this issue. Understanding the Problem First, let's understand what was happening in their environment: They had a 6-node vSAN cluster running VCF 9.0 vSAN was configured with the new ESA architecture They were trying to migrate VMs fro...

Unlocking VMware Cloud Foundation 9.0: A Strategic Blueprint for Enterprise Transformation

The evolution of VMware under Broadcom represents not disruption, but clarification—a focused vision toward unified private cloud excellence. As organizations navigate this transformation, the opportunity has never been greater to build truly modern, efficient, and powerful infrastructure with VMware Cloud Foundation. After architecting VMware solutions across diverse enterprise environments, I've observed a pattern: organizations that embrace VMware Cloud Foundation (VCF) strategically—rather than viewing the transition as a burden—emerge with significantly more capable, cost-effective, and future-ready infrastructure. This post shares a practical framework for successfully modernizing your VMware environment, maximizing your investment, and positioning your organization for the AI-driven, cloud-native future. Understanding the VMware Cloud Foundation Vision Let's start with clarity about what Broadcom and VMware are building: VMware Cloud Foundati...