OSPF: Passive Interface Surprise
A router advertises a subnet but never forms the intended adjacency. Diagnose the passive-interface scope and fix it yourself, live, right below.
Symptom
A router advertises a subnet but never forms the intended adjacency. Identify the passive-interface scope and restore only the required OSPF hello traffic.
Your mission
Prove the cause, then fix it
Format
Guided CLI investigation
Investigate before you configure.
Use the CLI evidence to isolate the fault, make the smallest safe correction, then verify the network state changed.
Observe the symptom and link state.
Diagnose by comparing the protocol evidence.
Verify the expected device state and confirm the original symptom is resolved.
Console access: R1 · R2
This workspace stacks for portrait phones. Rotate to landscape for the full split-screen console.
Need a hint?
Reveal the root cause when you're ready.
Try the investigation first, then use this as your escape hatch, not a dead end.
Lab debrief
Turn the session into a repeatable troubleshooting pattern.
Use this reference after your attempt: first explain the symptom, then verify the evidence, then confirm the repair.
The problem
R1 advertises its loopback but has no neighbor on the shared transit link because passive-interface default was configured and the transit interface was not exempted.
What you'll practice
- Read OSPF protocol configuration
- Distinguish advertisement from hello behavior
- Use passive-interface safely
- Verify a FULL neighbor
The topology
Two routers connect over one transit network and advertise loopbacks into a single OSPF area.
Commands to run yourself
The real diagnostic commands for this lab, copy-paste ready. Run these in the same order to reproduce the investigation on your own session.
show ip ospf neighborshow ip protocolsshow ip ospf interface Ethernet0/0Frequently asked
Why keep passive-interface default at all instead of removing it?
passive-interface default is a sound hardening control: it silences Hellos everywhere by default, so only interfaces explicitly exempted send them. The fix isn't removing the default, it's exempting the one transit interface that actually needs adjacencies.
Ready to run this lab yourself?
No setup, no image sourcing. Book a session or ask for a live demo.