Static IP Routing Basics — A No-Nonsense Guide
Static IP routing is one of those topics that gets taught in networking courses but almost nobody actually uses in its pure form anymore. That doesn't mean you shouldn't know it cold. It means you need to understand both the theory and the reality of when it breaks. The quiz format you're looking at breaks down into three main chunks. The "15 6 4" notation typically refers to subnetting questions where you work with a /24 network (255.255.255.0) and need to calculate subnets, broadcast addresses, and valid host ranges. The "M Dulo" section covers the configuration side — setting up static routes on actual routers or Layer 3 switches. And the "Enrutamiento Estático IP" portion tests whether you can trace packet paths through a multi-router topology without a dynamic protocol doing the work for you. I remember working through a similar exam once where the trick question involved two routers connected to the same subnet with a static route pointing the wrong way due to an admin typo. The answer wasn't about the routing table at all — it was about verifying the exit interface IP matched the next-hop address. Simple mistake. Common on tests.
How Static Routing Actually Works in Practice
A static route is just a manually entered entry in a routing table. When a router receives a packet, it checks its table for the best match using the longest prefix rule. If it finds a match, it forwards the packet to the next-hop IP or out the specified exit interface. That's it. No advertisements, no convergence, no automatic path changes. The command syntax varies by vendor. On Cisco equipment it looks like this: ip route <destination_network> <subnet_mask> <next_hop_ip>
Or on some platforms: ip route <destination_network> <subnet_mask> <exit_interface> The key difference between next-hop and exit-interface matters more than people realize. Using an exit interface works fine for point-to-point links like serial connections, but on broadcast segments like Ethernet, the router still needs to resolve the MAC address of the next hop. Without a directly connected route to that next-hop IP, the static route goes nowhere. I once spent an hour troubleshooting a lab where the static route had the right destination but the next-hop IP wasn't in any directly connected subnet. The route appeared in the table but packets never left the router.
Get the Full Details
Subnetting for the 15 6 4 Section
Here's what the subnetting questions are really testing. Given a network like 192.168.1.0/24, you need to subnet it into smaller networks. If the question asks for 6 subnets, you borrow 3 bits (2^3 = 8 subnets, which covers 6). The new subnet mask becomes /27 or 255.255.255.224. Each subnet gets 32 addresses, 30 of which are usable hosts. The subnets would be: 192.168.1.0/27 — hosts .1 through .30, broadcast .31
192.168.1.32/27 — hosts .33 through .62, broadcast .63
192.168.1.64/27 — hosts .65 through .94, broadcast .95
192.168.1.96/27 — hosts .97 through .126, broadcast .127
192.168.1.128/27 — hosts .129 through .158, broadcast .159
192.168.1.160/27 — hosts .161 through .190, broadcast .191
For the "4" part of the quiz, you'd likely subnet further or work with a different base network. The math stays the same regardless. The trick questions usually involve overlapping ranges or asking for the total usable hosts across all subnets combined.
When Static Routing Fails — And What to Do Instead
Static routes don't adapt. If a link goes down, traffic keeps trying to use it until you manually remove or update the route. In a small lab or a single-exit branch office, this is manageable. In anything with redundancy requirements, it's a liability. I've seen production environments where a static default route caused a 45-minute outage because a failover path was configured manually and someone forgot to update it after a cable change. Dynamic protocols like OSPF handle this automatically. The tradeoff is complexity and occasional instability during convergence. For the quiz context, you should know when static is appropriate and when it isn't. Static makes sense for stub networks, default routes at the edge, and simple topologies with one path to a destination. It breaks down in meshed topologies where multiple paths exist and links can fail independently.
Common Exam Pitfalls
The most frequent mistake on these quizzes is confusing the administrative distance values. A directly connected route has an AD of 0. A static route has an AD of 1. If both exist for the same prefix, the router prefers the static route unless you configure a floating static with a higher AD. This comes up in questions about redundant paths. Another trap: the router needs a route back to the source network for two-way communication. A static route only solves one direction. I saw a question once where the topology had correct outbound routes but no return path, and the answer was simply that the ping would fail despite the routing table looking correct. Always verify bidirectional reachability in your head before picking an answer. The final common error involves summarization. Static routes can be aggregated, but only if the summarized range doesn't include networks you don't actually want to route. Accidental summarization sends traffic to the wrong place. This is why summary routes on production routers are usually reviewed carefully and documented.
How to Study This Material Effectively
Don't just memorize the subnetting chart. Work through the math by hand for at least ten different base networks and masks. Then configure a real topology in GNS3 or Packet Tracer. Set up three routers, configure static routes in both directions, and break things on purpose. Change an IP, delete a route, misconfigure a mask. See what happens and fix it. The practical knowledge you gain from breaking things is worth more than any number of practice quizzes. The exam questions test whether you can think through the forwarding decision, not whether you can recite commands. Understand what the router is doing at each step and you'll handle any variation the quiz throws at you.
