"One Router to Rule Them All"

You've added more routers to cover the whole building. Each one has its own IP address. The mesh is working. But now you have a new problem: every router thinks it's in charge.

Each router is running its own DHCP server, handing out IP addresses to devices that connect. Your laptop connects to the classroom router and gets 192.168.70.50. You walk to the courtyard, your laptop roams to the courtyard router, and suddenly it gets 192.168.70.51 from a different DHCP server. Sometimes both routers try to answer at once. Your laptop gets confused. Connections drop. Pages half-load. You restart everything and it works for a while, then breaks again.

This is what happens when you have multiple DHCP servers fighting for control.

The Problem: Too Many Cooks

In a typical home setup, a single router does everything:

• Connects to the internet (WAN)
• Assigns IP addresses to devices (DHCP server)
• Resolves domain names (DNS)
• Protects the network (Firewall)
• Provides WiFi

When you add a second router with factory settings, it tries to do all of this too. Now you have two DHCP servers, two firewalls, two devices both thinking they're the gateway to the internet. The network becomes a confused mess of conflicting services.

The Solution: One Boss, Many Workers

The fix is simple in concept: pick one router to be the boss, and make the others dumb.

Your main router — the one connected to the internet — handles everything:

• DHCP server (assigns all IP addresses)
• DNS (resolves all domain names)
• Firewall (protects the entire network)
• Gateway (routes all traffic to the internet)

Your satellite routers become "dumb access points." They do exactly one thing: bridge wireless traffic to the main router. They don't hand out IP addresses. They don't run firewalls. They don't make routing decisions. They just pass packets along.

When a phone connects to a satellite router, it's as if it connected directly to the main router. The phone asks for an IP address, and the main router answers. The satellite just relays the message.

Why This Works

With one DHCP server, every device on your network gets its address from the same source. No conflicts. No confusion. When you look at the main router's DHCP lease table, you see every connected device in one place.

Troubleshooting becomes easier too. If a device isn't getting an IP, you check one place: the main router. If DNS isn't working, you check one place: the main router. The satellites become nearly invisible — they just move packets around.

The Catch: Finding Your Satellites

There's one downside. If your satellite routers get their IP addresses via DHCP from the main router, those addresses might change. You try to log into 192.168.70.10 to check the classroom router, but it's now 192.168.70.47 because the lease expired and it got a new address.

The solution is static DHCP leases. On the main router, you tell the DHCP server: "When you see a device with this MAC address, always give it this specific IP." Now your classroom router is always 192.168.70.10, but it's still getting that address from the main router — not from a manual configuration that could conflict with something else.

Best of both worlds: centralized control, predictable addresses.