Last updated: May 1, 2026
Most “the network is broken” tickets are routing tickets. A bad static route, a redistribution loop, an OSPF metric mismatch, an asymmetric path through a stateful firewall — every one of them ends with a packet that reaches its destination but cannot find its way back. This module gives you the mental model for routing decisions, the protocols (static, OSPF, EIGRP, RIP for completeness), and how VLANs slice a single switch into separate Layer-2 domains for segmentation.
The forwarding table — what every router actually does
A router’s job is short: receive packet, look up destination IP in forwarding table, send to next-hop, repeat. Lookup uses
longest-prefix matchamong all matching prefixes, the most specific wins. If your table has 0.0.0.0/0 via 1.1.1.1 (default route), 10.0.0.0/8 via 10.0.0.1, and 10.10.10.0/24 via 10.10.0.1, then a packet for 10.10.10.5 matches all three but the /24 wins because /24 is more specific than /8 which is more specific than /0. The Linux command ip route get 10.10.10.5 performs exactly this lookup.
Cisco IOSshow ip route 10.10.10.5.
Juniper Junosshow route 10.10.10.5. Memorise these — they are the first thing you type when something is broken.
Custom team training + practitioner advisory
Beyond the free academy — we run private workshops, vCISO advisory, and red-team exercises tailored to your stack. For Indian SMBs scaling past their first hire.