STEP 17 — Enable HQ ↔ Branch Routing (Static Routes)

Goal

Allow HQ LAN ↔ Branch LAN communication.

Still:
❌ No OSPF
❌ No VLANs
❌ No NAT

Just basic routing logic.

---

🔹 What needs to happen (concept)

• HO-R1 must know how to reach 10.20.10.0/24
• BR-R2 must know how to reach 10.10.10.0/24

Routers only know:

• Directly connected networks
• What you explicitly tell them

---

🔹 STEP 17.1 — Add static route on HO-R1

1. Click HO-R1 → CLI
2. Type:

enable
configure terminal
ip route 10.20.10.0 255.255.255.0 10.255.255.2
end
write memory

🔎 Meaning:

• “To reach Branch LAN, send traffic to BR-R2 over the WAN”

---

🔹 STEP 17.2 — Add static route on BR-R2

1. Click BR-R2 → CLI
2. Type:

enable
configure terminal
ip route 10.10.10.0 255.255.255.0 10.255.255.1
end
write memory

🔎 Meaning:

• “To reach HQ LAN, send traffic to HO-R1 over the WAN”

---

🔹 STEP 17.3 — Test end-to-end (this is BIG)

From Branch PC:

ping 10.10.10.10

From HQ PC:

ping 10.20.10.10

You should now get replies 🎉

---

🧠 What you just learned (VERY IMPORTANT)

• Routers don’t magically know paths
• Static routes explicitly teach paths
• WAN routing is logical, not physical
• This is the foundation of OSPF

---

🚫 Still NOT doing

❌ OSPF
❌ VLANs
❌ DHCP
❌ NAT