PlantUML DiagramBroadcast vs. Point-to-Point OSPF
A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
You're configuring OSPF in a lab with three routers. You configure the loopback IPs after OSPF is running, and suddenly your neighborships drop. Why? The Router IDs changed — and OSPF doesn't tolerate that without renegotiation.
Router IDs are the fundamental identifiers in OSPF. Every LSA, every neighbor relationship, every DR election references them. Understanding how they're selected — and when they change — prevents a whole class of OSPF problems.
The Router ID is fixed when the OSPF process starts. If you configure a loopback afterward, the Router ID doesn't change until OSPF restarts or you use `clear ip ospf process`. That's why best practice is to configure the Router ID explicitly — it's deterministic and doesn't depend on interface state.
! Explicit Router ID — the right wayR1(config)# router ospf 1R1(config-router)# router-id 10.255.255.1R1(config-router)# exit! Common pattern: use the loopback IP as the Router IDR1(config)# interface loopback0R1(config-if)# ip address 10.255.255.1 255.255.255.255R1(config-if)# exitR1(config)# router ospf 1R1(config-router)# router-id 10.255.255.1! VerifyR1# show ip ospf | include Router ID
The convention of Loopback0 as 10.255.255.X/32 combined with an explicit `router-id` command gives you a stable, human-readable ID that matches your documentation. The Router ID format looks like an IPv4 address, but it's really just a 32-bit identifier — the octets mean nothing to OSPF.
| Network type | DR/BDR | Hello timer | Used for |
|---|---|---|---|
| Broadcast | Yes | 10s | Ethernet (default) |
| Point-to-point | No | 10s | Serial, /31 links, GRE tunnels |
| Non-broadcast (NBMA) | Yes | 30s | Frame Relay, ATM (legacy) |
| Point-to-multipoint | No | 30s | Hub-and-spoke, Frame Relay |
| Loopback | No | N/A | Loopback interfaces (automatic) |
On a broadcast segment with N routers, a full mesh of adjacencies would be N × (N-1) / 2. For 5 routers, that's 10 adjacencies — each router exchanging LSAs with every other. The DR/BDR mechanism reduces this: every router forms a FULL adjacency with the DR and BDR only, not with each other.
A router connected via Ethernet to a WAN provider's handoff expects OSPF neighbors but sees none. The provider says they're running OSPF on their side. You see no Hellos. What's the likely cause?
Select the safest next action.
Finish the lesson once you have worked through the material. This awards ★ 35 XP.