RIP
— Routing Information ProtocolRIP is a distance-vector interior gateway protocol that measures reachability in hop counts rather than link cost. RIPv2 (RFC 2453) adds classless prefixes, a next-hop field, and MD5 authentication to the original design, and it caps usable paths at 15 hops because a metric of 16 is defined as unreachable.
Interactive Session: How RIP Works
Step through the packet exchange sequence between nodes.
Interactive Execution Sandbox
Interact with a live or clearly-labelled simulated instance of RIP.
Threat Model & Attack Simulation
How this protocol is attacked in practice, what defenders can see, and which control stops it.
Threat model & attack simulation
SimulatedDefensive education. Every step runs in this page; no traffic is generated or sent.
RIP route injection
SpoofingA forged RIP update advertises a shorter route for a prefix and attracts traffic to the attacker.
Send an update
The attacker multicasts a RIPv2 response with a low hop count.
RIP updates from an unapproved router.
Traffic redirection or outage for the affected prefixes.
Defences that matter
- RIPv2 authentication
- Passive interfaces and prefix filters
- Maximum-path and route-change monitoring
This is a conceptual model for defenders, not an exploit toolkit. It contains no payloads, tooling or instructions for attacking systems you do not own.
Protocol Specification & Architecture
Key characteristics, real-world deployment patterns, and trade-offs.
Core Technical Features
- Distance-vector algorithm derived from the Bellman-Ford computation
- UDP port 520 with multicast updates to 224.0.0.9
- Maximum usable metric of 15 hops, with 16 meaning unreachable
- Classless prefixes, next-hop field, and MD5 authentication in RIPv2
- Loop prevention through split horizon, poison reverse, and hold-down timers
Real-World Use Cases
- Small branch and campus networks with simple flat topologies
- Legacy equipment that supports no newer routing protocol
- Lab and certification practice for distance-vector concepts
Advantages & Strengths
- Very simple to configure and easy to reason about
- Low memory and CPU footprint on small routers
Limitations & Vulnerabilities
- Hop count ignores bandwidth and latency, so it can pick a slow path
- Slow convergence and a hard 15-hop diameter limit its scalability