RIP (Routing Information Protocol) is a distance-vector routing protocol that enables routers to exchange reachability information and select paths based on hop count, with a maximum network depth of 15 hops before routes are marked unreachable at metric 16. The protocol operates simply with minimal configuration and memory requirements by having routers periodically broadcast their full routing tables to directly connected neighbors every 30 seconds, adding one hop to each metric along the way. While RIP's simplicity made it common in early IP networks, its operational weaknesses—including slow convergence after failures that can take minutes to propagate, lack of authentication in version 1, and inability to consider link speed—have made OSPF and BGP the preferred choices for larger deployments today.
How RIP works
RIP routers build routing tables by exchanging reachability information with directly connected neighbors. Each route carries a metric equal to the number of routers that must be crossed to reach the destination.
- Initial advertisement: A router starts with its directly connected networks at a metric of 1 and sends them to neighbors in response messages. It can also send a request to ask neighbors for their full tables.
- Table update: A router that receives a route adds one hop to the metric. It installs the route if the destination is new or the metric is lower than the one it already holds.
- Periodic exchange: Each router sends its full routing table to its neighbors on a regular timer, which is 30 seconds in the standard. Version 2 uses multicast; version 1 uses broadcast.
- Timeout and removal: If updates for a route stop arriving, the route is marked unreachable with a metric of 16 and later removed from the table.
A metric of 16 means unreachable, so the longest usable path is 15 hops. RIP version 2 adds subnet masks, authentication and multicast updates, while RIPng extends the protocol to IPv6. Mechanisms such as split horizon and triggered updates reduce routing loops and slow convergence.
Common RIP issues
When a link fails, routers learn of it through timeouts or neighbor updates, so traffic can be dropped or looped for minutes. Engineers often see this as intermittent reachability that clears only after route timers expire.
Networks deeper than 15 routers lose routes because a metric of 16 means unreachable. Remote subnets disappear from the table even though the links are up.
RIP version 1 does not carry subnet masks, while RIP version 2 does. Mixing them, or running version 1 on a network using variable-length subnets, causes missing or wrong routes.
If split horizon or poisoning is disabled, routers can keep advertising a dead route to each other and raise its metric slowly until it reaches 16. Packets circulate in the meantime.
Full table updates on every timer interval consume noticeable bandwidth on low-speed WAN links when route counts are large. Interface utilization shows regular bursts at each update.