Mastering Network Connectivity: My First Two-Router Static Routing Lab in Packet Tracer

Every network begins as islands.

In this lab, I wasn’t just looking at two routers and two PCs — I was staring at three isolated IP spaces:

• 192.168.0.0/24 on the left
• 192.168.100.0/24 on the right
• And a tiny /30 bridge — 10.10.10.0/30 — barely wide enough to carry two router interfaces

My mission was to turn islands into a connected system using pure fundamentals: configure interfaces, set gateways, and build static routes that guide packets beyond their own borders.

No automation. No dynamic routing protocols. Just intentional engineering — IP by IP, hop by hop.

And the moment those pings returned across both routers, the diagram stopped being shapes on a screen and became a live network — one I built.

Breaking Down the Lab

The goal was simple: Make PC0 on one network talk to PC1 on a totally different network through two routers.

The Layout

• LAN #1: 192.168.0.0/24
• LAN #2: 192.168.100.0/24
• Router-to-Router Link: 10.10.10.0/30

That /30 jumped out immediately — only two usable IP addresses, perfect for connecting router interfaces.

My mission became clear:

1. Configure the router interfaces
2. Assign PC IPs + default gateway
3. Teach each router where the other network lives
4. Test — and celebrate the pings 🎉

Step 1 — Check First, Configure Later

Instead of typing blindly, I checked what the routers already knew.

enable
do show run

Router0 was almost fully configured:

• Gig0/0/0 → 192.168.0.1/24
• Gig0/0/1 → 10.10.10.1/30

Router1 was halfway there:

• Gig0/0/0 → 192.168.100.1/24
• Gig0/0/1 → no IP address yet

Boom. Now I knew exactly where to start — and what not to touch.

⚙️ Step 2 — Give Router1 a Voice

I configured the missing interface on Router

Suddenly, both routers were speaking on the same subnet:

• Router0 ➝ 10.10.10.1
• Router1 ➝ 10.10.10.2

That’s the digital equivalent of exchanging phone numbers.

Step 3 — Bringing the PCs to Life

Every device needs an identity and a gateway to leave home.

PC0

• 192.168.0.10
• Gateway: 192.168.0.1

PC1

• 192.168.100.10
• Gateway: 192.168.100.1

If routers are mail carriers, the gateway is the mailbox — all outgoing letters go there first.

Step 4 — Add Static Routes (GPS for Routers)

Routers are smart — but not psychic. They only know networks attached directly to them.

So I taught each router where the remote LAN lived.

On Router0 (point to Router1):

ip route 192.168.100.0 255.255.255.0 10.10.10.2

On Router1 (point to Router0):

ip route 192.168.0.0 255.255.255.0 10.10.10.1

Suddenly the roadmap was complete.

🎯 Step 5 — The Ping That Made My Day

Validation time.

1️⃣ PC0 → its gateway 2️⃣ Router → router

3️⃣ PC0 ⇆ PC1

When the replies came back across both routers, it wasn’t a surprise — it was confirmation. The network was doing exactly what I built it to do.

🌟 Lessons Learned

Here’s what this lab taught me — beyond commands and subnets:

Check before you configure A five-second do show run can save you twenty minutes of confusion.

Networking is storytelling Interfaces, routes, gateways — they all work together to move information from one place to another.

Small wins build big confidence Every successful ping is a reminder: You’re learning. You’re leveling up.

Fear shrinks when you touch the keyboard Most of the time, the only thing between you and understanding is a willingness to try.

Final Thoughts🔚

This lab started with two completely isolated PCs — no communication, no routes, no way to see beyond their own subnet.

With a few well-chosen IP addresses, properly set gateways, and two precise static routes, those islands became a single connected network.

That’s the real beauty of networking: we don’t just plug things in — we build bridges where none existed before.

If you’re studying for the CCNA like I am, or just leveling up your routing fundamentals, remember:

✨ Don’t rush. ✨ Think in terms of paths and next hops. ✨ Take it one interface, one route, one test at a time.

And when you want to see how it all comes together in real time, you can watch the full step-by-step walkthrough of this project here:

[embed]