This episode opens the world of dynamic routing: the classification of IGP and EGP, and the differences between distance vector, link-state, and path-vector. You learn EIGRP from neighbor adjacency, AS number, and K-values metrics, then configure EIGRP on a Cisco Router, understand the topology table with successor and feasible successor, and secure neighbors with passive-interface.

In episode 9 you configured routes manually. Imagine a network with hundreds of routers — manual configuration becomes impossible to manage. This is where dynamic routing comes in: protocols that learn routes automatically, propagate them between routers, and adapt when the topology changes.
Episode 10 opens with the classification of routing protocols, then moves into EIGRP — Cisco's distance vector protocol that converges quickly and is bandwidth efficient. You will build neighbor adjacency, configure EIGRP in PNETLab, read the topology table, and secure the network from rogue neighbors.
Routing is divided into static (manual, episode 9) and dynamic (automatic). Dynamic protocols are divided by scope: IGP (Interior Gateway Protocol) runs within a single organization, while EGP (Exterior Gateway Protocol) runs between organizations. Examples of IGP are RIP, EIGRP, and OSPF; an example of EGP is BGP, which will be discussed in episode 13.
EIGRP fixes the weaknesses of classic distance vector with the DUAL algorithm, so routing loops do not occur and convergence is faster.
EIGRP runs within a single Autonomous System (AS) — all routers in the
same AS share a database. Configuration starts with router eigrp <as>.
The EIGRP metric is calculated from K-values which by default only use
bandwidth and delay; enabling K2, K3, K4, K5 is only for special
cases.
Before exchanging routes, EIGRP routers build neighbor adjacency by sending
Hello packets periodically. Hello is sent to the multicast address
224.0.0.10. If a Hello from another router is received with matching
parameters (K-values and AS number), the two routers become neighbors and
begin exchanging topology.
Build R1 and R2 in PNETLab with a /30 link, then configure EIGRP on both:
configure terminal
router eigrp 100
router-id 1.1.1.1
network 192.168.10.0 0.0.0.255
network 10.0.0.0 0.0.0.3
no auto-summary
exitnetwork 192.168.10.0 0.0.0.255 advertises the subnet to EIGRP, and
no auto-summary prevents routes from being simplified to their default
class. Do not forget to configure R2's side with router eigrp 100 and the
appropriate network statements.
Every destination has two paths in the EIGRP topology table:
Show both:
R1# show ip eigrp topology
P 192.168.20.0/24, 2 successors, FD is 2816
via 10.0.0.2 (2816/2176), GigabitEthernet0/1
via 10.0.0.6 (3072/2816), GigabitEthernet0/2show ip eigrp topology displays all paths to a destination. The
first path is the successor, the second is the feasible successor ready to
take over without waiting for a recalculation — that is EIGRP's convergence
speed.
Without protection, EIGRP tries to build adjacency on every interface listed
in a network statement — including interfaces facing end users. A rogue
neighbor router could learn the entire internal topology. Use
passive-interface for interfaces that should not form adjacency:
configure terminal
router eigrp 100
passive-interface g0/0
exitpassive-interface g0/0 keeps EIGRP advertising the network on
that interface but stops sending Hello — adjacency will never form on the LAN
side.
Check the neighbor status and learned routes:
R1# show ip eigrp neighbors
R1# show ip route eigrpshow ip eigrp neighbors displays neighbors with established
adjacency complete with hold time, while show ip route eigrp confirms that
dynamic routes enter the routing table. If the adjacency column is empty,
check the AS number and K-values on both sides.
Key takeaways:
passive-interface prevents rogue neighbors on LAN interfaces.In the next episode, episode 11, we discuss single-area OSPF — a link-state protocol based on the Dijkstra algorithm, neighbor formation from Down to Full, DR and BDR election on multi-access networks, and full single-area OSPFv2 configuration verified with show ip ospf neighbor.