Configure Satellite Routers with DHCP (Iteration 2)
This guide covers the second iteration of a wireless mesh deployment: converting each satellite (secondary) router so it receives its LAN IP from the main router via DHCP, turning it into a true "dumb AP" that only bridges traffic. WAN and the firewall are also disabled on the satellite.
This guide implements the concept introduced in Chapter 2.2.4 — One Router to Rule Them All.
This is the second iteration of the mesh deployment
This guide is the recommended evolution of the Static IP Mesh guide (Iteration 1). In Iteration 1 you assign each satellite a hard-coded static LAN IP and disable its DHCP server manually. Here, the satellite instead requests its address via DHCP from the main router, and you pin that address with a static lease — matching the "one router to rule them all" model from Chapter 2.2.4. Use this guide to upgrade the satellites you configured in Iteration 1, or to set up new satellites directly in this mode.
What You'll Learn
- How to convert a satellite router from static IP to DHCP client
- How to disable unnecessary services (DHCP server, firewall, WAN)
- How to find the satellite's new IP after reconfiguration
- How to create a static DHCP lease for stable management access
Prerequisites
- Main router configured and reachable on the network
- Satellite router with OpenWrt and mesh interface already connected (see Static IP Mesh guide)
- Access to LuCI web interface on both routers
Configure one at a time
Configure one satellite router at a time. Expect the satellite's IP address to change after applying these settings.
Network Architecture Goal
After completing this guide:
- The main router provides DHCP, DNS, internet connectivity, and firewalling
- The satellite router only bridges traffic — it doesn't hand out IP addresses or route packets
- The satellite gets its management IP from the main router via DHCP
Step-by-Step Implementation
1. Open the satellite router in LuCI
- Connect to the satellite router's current IP address in your web browser.
- Log in to LuCI with your credentials.
2. Change LAN from static IP to DHCP client
- Go to Network → Interfaces.
-
Find the LAN interface and click Edit.

-
In General Settings, change Protocol to DHCP client.
-
Click Save but do not apply yet.

Why DHCP client?
By setting the satellite's LAN interface to DHCP client mode, it will request an IP address from the main router instead of using a manually configured static IP. This simplifies management and avoids IP conflicts.
3. Ensure WiFi interfaces are attached to LAN
- Go to Network → Wireless.
-
Review your wireless interfaces.

-
Check the client-facing WiFi AP interface — ensure Network is set to lan.

-
Check the 802.11s mesh interface — ensure Network is also set to lan.

Why attach to LAN?
All wireless interfaces must be bridged to the LAN interface so that traffic from WiFi clients flows through to the main router. If an interface isn't attached to LAN, devices connecting to it won't get internet access.
4. Disable the DHCP server on the satellite
- Go to Network → Interfaces → LAN → DHCP Server tab.
- Check the box to Disable DHCP for this interface (or set it to ignore).
- Click Save.

Critical step
The satellite must not hand out IP addresses. If two DHCP servers run on the same network, devices will get conflicting addresses and connectivity will break randomly.
5. Remove WAN usage from the satellite
- Go to Network → Interfaces.
- Find WAN and WAN6 interfaces.
- Either delete them or set them to unmanaged/disabled.

Why disable WAN?
The satellite should not provide routing for clients — all routing happens through the main router. Keeping WAN interfaces active can cause traffic to be routed incorrectly.
6. Disable the firewall on the satellite
- Go to System → Startup.
- Find firewall in the list of services.
- Click Stop to stop the service.
- Click Disable to prevent it from starting on boot.

Why disable the firewall?
A dumb AP that only bridges traffic doesn't need a firewall — the main router handles all security. Running a firewall on the satellite can block legitimate traffic and cause connectivity issues.
7. Apply changes
- Click Save & Apply.
- Wait for the satellite router to reconnect to the network.
- The old IP address will likely stop working.
You will lose connection
After applying, the satellite will request a new IP from the main router. Your current connection will drop. This is expected.
8. Find the new management IP
- Open LuCI on the main router.
- Go to Network → DHCP and DNS → Active DHCP Leases.
- Find the satellite router by its MAC address or hostname.
- Note the new IP address assigned by DHCP.

- Use this new IP to reconnect to the satellite router's LuCI interface.
9. Reserve the satellite IP on the main router
To ensure the satellite always gets the same IP address (for easy management), create a static lease:
- On the main router, go to Network → DHCP and DNS.
- Scroll to Static Leases section.
- Click Add to create a new static lease:
- Hostname: A descriptive name (e.g.,
satellite-classroom) - MAC address: The satellite's MAC address
- IPv4 address: The IP you want to assign permanently
- Lease time: Set to
infinitefor a permanent assignment
- Hostname: A descriptive name (e.g.,
- Click Save & Apply.

Why the new IP doesn't apply immediately
After creating the static lease, the satellite may still show the old dynamically-assigned IP. This is because the DHCP "handshake" already completed. You need to restart the satellite's LAN interface to request a new lease.
10. Restart the satellite's LAN interface
- Connect to the satellite router using its current IP.
- Go to Network → Interfaces → LAN.
- Click Restart to force the interface to request a new DHCP lease.

The satellite will now receive the static IP you configured in the previous step.
11. Verify the result
From the satellite router, confirm:
- It received an IP address from the main router
- It has a default gateway pointing to the main router
- It has DNS servers configured
- Clients connected to the satellite can browse the internet
Quick test
Connect a phone or laptop to the satellite's WiFi. Check that it gets an IP in the main router's DHCP range and can load a website.
Common Mistakes
| Problem | Cause | Solution |
|---|---|---|
| Clients get no IP | DHCP server still running on satellite | Disable DHCP server (Step 4) |
| Clients get IP but no internet | WAN interface still active | Disable WAN interfaces (Step 5) |
| Can't reach satellite after applying | IP changed | Find new IP in main router's DHCP leases (Step 8) |
| Satellite IP keeps changing | No static lease | Create a static DHCP lease (Step 9) |
Revision History
| Date | Version | Changes | Author | Contributors |
|---|---|---|---|---|
| 2026-04-04 | 1.0 | Initial guide creation | Maria Jover |