← Module 03 · Layer 3: Network

Distance-Vector Routing (RIP, EIGRP)

A router running a distance-vector protocol never sees the whole map. It just trusts what its immediate neighbors report, and passes that along.

"Routing by rumor"

A distance-vector router doesn't know the network's actual topology. It only knows two things about each destination:

  1. Which direction, which neighbor, to send toward.
  2. How far away it is, by that neighbor's own count.

It's exactly like asking a coworker for directions and just trusting their word for how far it is, then repeating that secondhand distance to the next person who asks you. Nobody involved is looking at an actual map.

RIP: The simplest version

RIP (Routing Information Protocol) measures distance in pure hop count (the number of routers between here and the destination), with no regard for link speed at all. A single congested 1 Gbps hop looks identical to it as three empty fast ones. Every 30 seconds, a RIP router broadcasts its entire routing table to its neighbors, whether anything changed or not, and caps out at 15 hops, treating anything farther as unreachable.

To avoid loops, RIP uses split horizon (never advertise a route back out the same interface you learned it on) and route poisoning (explicitly advertise a failed route as a hop count of 16, "infinity," rather than just letting it quietly time out).

EIGRP: Distance-vector, sped up

EIGRP (Enhanced Interior Gateway Routing Protocol) is still fundamentally distance-vector, but fixes RIP's two biggest weaknesses. Instead of hop count, it uses a composite metric built from bandwidth and delay (and optionally reliability and load), so it actually reflects real path quality. Instead of broadcasting the whole table every 30 seconds, it forms proper neighbor relationships (via periodic Hello packets) and sends only incremental updates when something actually changes.

It also runs the DUAL algorithm (Diffusing Update Algorithm), which lets a router pre-compute a loop-free backup path (a feasible successor) for its important routes ahead of time, so it can fail over almost instantly instead of recalculating from scratch after a failure.

RIP: every 30 seconds, regardless entire table, every time EIGRP: Hellos always, updates only on change small Hello packets, constantly an actual topology change: only then, a real update
RIP re-sends everything on a timer. EIGRP only sends real updates when the topology actually changes.
RIPEIGRP
MetricHop count (max 15)Composite: bandwidth + delay
Update styleFull table, every 30sIncremental, only on change
ConvergenceSlowFast, pre-computed backup paths via DUAL
Where you'll see itMostly retired, still used to teach the conceptCommon in Cisco-heavy enterprise networks
WHY LEARN RIP IF IT'S RETIRED

RIP is the cleanest possible illustration of distance-vector logic precisely because it has nothing else going on. Understanding it first makes EIGRP read as "the same idea, with three specific improvements" instead of a wall of new concepts at once.