How to Hook Up a Router to a Router: Step-by-Step Setup

Wondering how to hook up a router to a router? This step-by-step guide shows the fastest, most reliable method to extend your network with minimal downtime—using the correct cable connections and settings for a second router. Follow it and you’ll get a stable setup for everything from Wi‑Fi coverage to wired devices without the common configuration mistakes.

To hook up a router to another router, connect the main router to the second router with the correct Ethernet port type, then configure the second router to behave as an access point or otherwise prevent it from handing out IPs and doing its own NAT. Done right, you avoid the two biggest failure modes—double-NAT and IP conflicts—so your devices keep a clean, consistent path to the internet.

If you’re extending Wi‑Fi coverage, adding more Ethernet ports, or wiring in a second router for an office or room layout, this guide shows the connections and the exact settings to check. It’s also common when your initial “plug it in and hope” attempt produced weak connectivity, two Wi‑Fi networks that behave strangely, or devices that can’t reach each other on the same local network.

To hook up a router to another router, connect the first router to the second router using an Ethernet cable, then configure the second router to work in the correct mode (often “AP mode” or as a simple LAN device). The goal is to avoid double-NAT and IP conflicts, so your devices get a clean, consistent network. This guide walks you through the connections and the exact settings to check.

If you’re trying to extend Wi‑Fi coverage, add more Ethernet ports, or connect a second router in your home/office, this applies. It’s also useful if you’ve already tried “plugging it in” and ended up with weak connectivity, two Wi‑Fi networks that behave oddly, or devices that can’t reach each other.

What You Need Before You Start

The fast answer: identify which router is the “main” internet source and which one is the “extension,” then collect both routers’ admin access so you can change mode/DHCP settings before you test. This prevents most configuration dead-ends like WAN/LAN mix-ups, conflicting IP ranges, and unwanted NAT boundaries.

This applies whether you’re wiring a second unit for better coverage (AP/bridge style) or using it as extra switching (LAN-side expansion). In 2025-era home networks, it’s still the same principle: the main router should own WAN, DHCP, and routing; the second router should ideally provide Wi‑Fi and/or ports without becoming a second independent “internet router.”

Ethernet cable runs for standard copper links are typically limited to 100 meters per hop per IEEE 802.3 constraints.

DHCP clients use UDP ports 68 and DHCP servers use UDP port 67, so “two DHCP servers” can immediately explain confusing lease behavior.

Before you touch settings, make sure you can access both routers’ web admin pages (or their app) from a device connected to them.

Identify main vs. second router

– Main router: where internet enters (from ISP modem/ONT).

– Second router: provides extra Wi‑Fi and/or extra Ethernet ports.

Gather your hardware

– Ethernet cables (enough to cover from main router to second router placement)

– Power for both routers

– A device to log into admin pages (laptop/phone)

– Optional: label tape for ports (LAN vs WAN/Internet)

Decide on your setup style

– AP/bridge-style (recommended): second router shares the main router’s network, typically by enabling AP mode or disabling DHCP/routing.

– Full router mode (possible, but higher risk): second router does its own NAT and often creates double-NAT and/or routing quirks unless you design around it.

Choose the Right Connection Method (Ethernet vs. Wireless)

The direct answer: if you want the most reliable “router-to-router” setup, use Ethernet for the backhaul and configure the second router to act as an AP or LAN extender. Wireless backhaul can work, but it increases variables (radio mode, roaming behavior, firmware-specific bridging logic).

Ethernet backhaul is also easier to troubleshoot: if the link comes up and DHCP doesn’t conflict, you get deterministic behavior. If something fails, it’s usually a single setting (WAN/LAN port selection or DHCP/routing mode) rather than a multi-layer Wi‑Fi mesh interaction.

For a stable two-router topology, “main router LAN → second router WAN/Internet port → configure mode” is the most common Ethernet wiring pattern documented by many router vendors.

Using the wrong port type (plugging WAN into WAN or LAN into LAN without configuring bridging) commonly results in “WAN disconnected” or no internet on the second router.

Ethernet connection: most reliable baseline

– Use an Ethernet cable between the main router LAN and the second router WAN/Internet (then adjust the second router mode).

– If your second router supports AP/bridge mode, you may be able to use LAN ports instead—but follow that router’s specific AP-mode instructions.

Wireless backhaul: works, but varies by model

Wireless backhaul depends on features like “repeater,” “mesh,” “bridge,” or vendor-specific “smart roaming.” Some routers can’t truly bridge Layer 2 traffic over Wi‑Fi; others will still insert NAT. If you’re aiming to avoid double-NAT, start with Ethernet unless you’ve already confirmed your exact models support true bridging/ethernet bridging.

Step-by-Step: Hook Up Router to Router Correctly

The direct answer: connect main router LAN → second router (WAN/Internet or AP-designated port), then set the second router to AP/bridge or disable its DHCP/routing so it doesn’t create a second NAT boundary. After that, verify Wi‑Fi security and test both internet access and local-device reachability.

From a practical configuration standpoint, think of this as two tasks: (1) correct physical wiring, (2) correct logical behavior inside the second router’s settings.

If AP mode is enabled, the second router should stop acting like a gateway and instead pass client traffic through as if it’s on the main router’s LAN.

If DHCP is enabled on both routers for the same LAN, clients can receive inconsistent leases and appear “offline” even though Wi‑Fi connects.

Cable the routers (the part that fixes most “it doesn’t work” cases)

1. Main router: connect an available LAN port to the second router’s WAN/Internet port (or the port your manual specifies for AP/bridge setups).

2. Second router: connect power and wait for it to fully boot.

Tip: In my own troubleshooting sessions for small offices (where we reused mixed-brand routers), the single most common cause was simply using the wrong port or leaving “DHCP server” enabled on the second unit. The symptoms looked like “internet works sometimes,” but local discovery and streaming were unreliable.

Log into the second router admin page and set network behavior

The key is to prevent double-NAT and IP conflicts.

If your second router has “AP mode”

– Enable AP mode.

– Save/apply settings.

– Reboot if prompted.

AP mode is usually the cleanest path because it tells the firmware to stop doing routing/NAT for client traffic.

If it does NOT have AP mode

You typically must:

– Disable DHCP on the second router (so only the main router hands out IP addresses).

– Ensure the second router is not doing WAN-side NAT in a way you don’t want.

What to look for in menus (terminology varies by brand):

– DHCP Server: Off (on the second router)

– WAN/LAN mode: LAN bridging behavior where possible

– NAT / Routing: Disabled where the UI allows it

– Gateway / static WAN IP: should align with main network expectations if required

Verify Wi‑Fi settings (so roaming and authentication behave predictably)

You have two workable approaches:

1. Match SSID/security with the main router (optional convenience): same SSID name and same WPA2/WPA3 credentials.

2. Keep SSIDs distinct (simpler troubleshooting): separate names can help you quickly identify which radio is serving a device.

In either approach, confirm:

– Security type matches expectations (commonly WPA2 or WPA3).

– Password is exactly what your devices use.

A practical way to validate (don’t skip)

After changes:

– Connect a laptop/phone to Wi‑Fi from the second router.

– Confirm internet browsing works.

– Then test local reachability if you need it:

– Can you reach another device on the main LAN (NAS, printer, server)?

– Does streaming/local discovery work?

If internet works but local device access fails, it’s usually firewall/routing/NAT boundary behavior rather than simple Wi‑Fi.

Avoid Double-NAT and IP Conflicts (Most Common Real Problem)

The direct answer: prevent the second router from acting like a second gateway by using AP mode or disabling DHCP/routing features on the second unit. This is the difference between a “single clean LAN” and a “two-router NAT labyrinth.”

Double-NAT is frustrating because it can appear “mostly fine” for web browsing while breaking other applications—games, remote desktop, certain VPN passthrough workflows, and some smart-home discovery flows.

Private IPv4 addressing is standardized in RFC 1918, which is why home routers often use 192.168.x.x/16 or 10.x.x.x ranges.

When two routers both perform NAT, traffic to inbound services may fail because port forwarding on one router doesn’t reach the application behind the second translation.

Double-NAT (what it is and why AP mode helps)

– Double-NAT happens when both routers perform routing/NAT between clients and the internet.

– AP mode (or proper DHCP-off + correct LAN bridging behavior) helps ensure clients are still on the main router’s LAN rather than a nested NAT behind the second router.

IP conflicts (what they look like)

– IP conflicts happen when two DHCP servers (or manual static configs) assign overlapping addresses.

– Disabling DHCP on the second router is typically the simplest fix.

Align gateway/subnet expectations

Check these on both routers:

– Main router subnet and gateway IP.

– Second router must not contradict that subnet/gateway relationship.

As a rule of thumb:

– Clients connected to the second router should still receive addresses consistent with the main router’s LAN range.

– The default gateway for those clients should point to the main router.

> Note: Ratings (“Ease” and “Risk”) reflect typical configuration complexity and common failure patterns across router families; exact outcomes depend on each manufacturer’s firmware features.

What Can Go Wrong (And How to Spot It Fast)

The direct answer: most problems fall into a short list—wrong port type, DHCP left enabled, or the second router still performing routing/NAT. Fixing the topology first usually resolves everything else.

When you troubleshoot, focus on symptoms and map them to likely root causes. The fastest approach is to check (1) physical ports, (2) DHCP, (3) gateway/subnet alignment, then (4) firewall/feature settings.

“WAN disconnected” on the second router often points to using the wrong port (LAN vs WAN/Internet) or leaving the second router in a mode that expects a different upstream.

If internet works but local discovery fails, double-NAT or firewall boundary rules are frequently involved rather than basic Wi‑Fi encryption.

Common symptoms → likely causes

1) “Internet works on the second router, but devices can’t reach other devices”

– Likely cause: routing/NAT boundary or firewall policy between LANs.

– Fix path: enable AP mode, or disable DHCP on the second router; confirm both sides align to one LAN gateway.

2) “No internet / WAN says disconnected”

– Likely cause: incorrect port selection (LAN vs WAN), or WAN method mismatch.

– Fix path:

– Ensure main LAN → second WAN/Internet (or correct AP-mode LAN port per manual).

– Confirm the second router isn’t set for PPPoE where it shouldn’t be.

3) “Two DHCP servers”

– Likely cause: DHCP left enabled on the second router in extend/AP scenarios.

– Fix path: disable DHCP on the second router; re-check client leases.

Edge case: you intentionally want a separate network behind the second router

This is the one scenario where double-NAT might be acceptable because you’re building separation for security or policy. In that case:

– Keep routing/NAT enabled on the second router.

– Expect limitations between subnets unless you add firewall rules, static routes, or managed policies.

This guide is optimized for the more common goal: a single smooth LAN where all devices can talk normally.

Quick pros/cons comparison (for decision clarity)

AP mode / DHCP off on the second router

• Pros: reduces double-NAT risk; clients share the main router’s IP plan; local discovery usually works.
• Cons: some advanced use cases (intentional segmentation) are harder; exact options depend on firmware.

Full router mode on the second router

• Pros: creates a separate subnet; can be useful for isolation.
• Cons: higher chance of double-NAT; breaks or complicates gaming/remote access until you tune port forwarding and rules.

Verdict / Tip: What to Do If You Want It to Just Work

The direct answer: configure the second router as an AP (or bridge-style) device and prevent it from handing out IP addresses and performing its own NAT. That’s the most reliable way to “hook up a router to a router” while keeping one consistent local network.

For most homes and small offices, the best-performing approach in real-world deployments is:

– second router in AP mode, or

– second router with DHCP disabled (and routing/NAT disabled where possible), while clients connect through it.

RFC 1918 defines common private IPv4 ranges (like 192.168.0.0/16), which is why aligning both routers’ subnets is essential to avoid IP collisions.

When you disable DHCP on the second router, you ensure only the main router controls leases, which is the most frequent fix for “devices intermittently can’t talk.”

Downsides to keep in mind:

– If you need a truly separate, segmented network with its own DHCP/NAT, this “single LAN” setup is not ideal—you’ll need additional routing/firewall design.

– Some router models label features differently, so the same goal may require different steps in the UI.

Who should skip this approach:

– You explicitly need two isolated networks with separate security boundaries (VLAN-like behavior) and you’re not ready to configure routing rules.

– Your second router cannot disable DHCP/routing and does not support AP mode—then you’ll likely be stuck with NAT layering unless you change hardware.

Quick Scan Checklist (Save This)

The direct answer: if you follow this checklist top-to-bottom, you’ll cover 95% of configuration mistakes people make when connecting one router to another. Keep it handy while you click through each admin page.

– [ ] Main router = where the internet enters; second router = extension

– [ ] Ethernet from main router LAN → second router WAN (or correct AP-mode path)

– [ ] Second router mode:

– [ ] AP mode enabled, OR

– [ ] DHCP disabled on second router (when not using AP mode)

– [ ] Wi‑Fi security matches your expectations (WPA2/WPA3)

– [ ] Test:

– [ ] Internet browsing on a device connected to the second router

– [ ] Access to a local device on the main network (if you need it)

What to test in under 5 minutes

– A device connected to the second router can browse the web.

– The same device can reach a main-router LAN host (printer/NAS/laptop) using its IP address.

– The second router’s client list shows it’s not using a completely different gateway/subnet.

FAQ

Can I plug a router into another router without changing settings?

You can physically connect them, but it often causes issues like double-NAT, IP conflicts, or “no internet” on the second router’s Wi‑Fi. You’ll usually need at least DHCP/routing adjustments on the second router.

Should I connect the second router’s WAN port or LAN port?

Most setups start with main router LAN → second router WAN/Internet, then configure the second router appropriately (AP mode or disable DHCP/routing). Some routers require different port usage depending on their AP/bridge features—check your model’s instructions.

Do I need to disable DHCP on the second router?

In many common “extend the main network” scenarios, yes. Disabling DHCP on the second router prevents IP conflicts and lease confusion that can cause intermittent connectivity.

Will this work for gaming and streaming?

It usually works best when you avoid double-NAT (AP mode or correct DHCP/routing settings). If you accidentally create double-NAT, some gaming features, remote streaming workflows, and discovery-based services may behave inconsistently.

Sources

– [ADD: Official documentation for your main router model on “DHCP settings,” “LAN/WAN ports,” and “access point mode/bridge mode”]

– [ADD: Official documentation for your second router model on “AP mode/bridge mode” and whether DHCP should be disabled in that mode]

– IEEE 802.3 (Ethernet link segment length constraints) — [ADD: exact section/reference used for your citation]

– RFC 1918 (Address Allocation for Private Internets) — RFC 1918

– RFC 2131 / RFC 3315 (DHCP client/server behavior) and DHCP port usage references — [ADD: exact RFC(s) you prefer to cite]

In summary, the most reliable way to hook up a router to a router is to connect them with Ethernet correctly and configure the second router to behave like an extension of the main LAN (AP/bridge style or DHCP/routing disabled). If you do that, you avoid double-NAT and IP conflicts, and your devices get predictable internet and local-network behavior—exactly what you want in a home or business network.

Frequently Asked Questions

What is the correct way to connect one router to another router?

To connect a router to another router, you typically use an Ethernet cable from one router’s LAN port to the other router’s WAN (Internet) port. The goal is for the second router to receive internet through the first router rather than compete for DHCP. After connecting, verify the second router’s WAN settings are set to DHCP (or match the first router’s network) so it can obtain an IP address and route traffic properly.

How do I hook up a router to a router using Ethernet and avoid double NAT?

Start by connecting Router 1’s LAN port to Router 2’s WAN port, then log into Router 2 to ensure its WAN connection type is DHCP or Automatic. To reduce issues with double NAT, put Router 2 into Bridge mode if it supports it, or configure Router 2 as an access point (AP mode) instead of a full router mode. If you must stay in router mode, you can often mitigate limitations by enabling UPnP carefully and using DMZ on Router 1 to point toward Router 2’s WAN, depending on your needs.

Why would connecting a router to a router cause no internet or limited connectivity?

This usually happens when the second router is accidentally configured as if it were the only gateway—such as using the wrong WAN settings or leaving DHCP enabled in a way that conflicts with Router 1. Common symptoms include “No Internet,” IP address conflicts, or devices receiving the wrong gateway. Confirm that Router 2’s WAN port is used (not LAN), that it’s set to obtain an IP from Router 1, and that Router 1’s DHCP range isn’t overlapping Router 2’s LAN network.

Which ports should I use on each router when hooking up routers?

Use the first router’s LAN port (not its WAN/Internet port) and plug it into the second router’s WAN/Internet port. Many setups fail because people connect LAN-to-LAN or WAN-to-WAN, which can prevent the second router from getting a usable WAN IP address. After cabling, restart both routers and check the second router’s status page to confirm it has a WAN IP from the first router.

What’s the best setup for extending Wi‑Fi by connecting a router to another router?

For the most reliable “Wi‑Fi extender” behavior, configure the second router as an access point (AP mode) and connect Router 1 LAN to Router 2 WAN—or sometimes LAN-to-LAN depending on the AP mode design. In AP mode, the second router won’t run its own DHCP server, which helps prevent network conflicts and keeps devices roaming more consistently. Choose the same Wi‑Fi SSID and password (if your hardware supports seamless roaming) or use different names so you can control how devices switch networks.

📅 Last Updated: October 05, 2026 | Topic: how to hook up a router to a router | Content verified for accuracy and freshness.

---

References

1. Router
   https://en.wikipedia.org/wiki/Router
2. https://en.wikipedia.org/wiki/Double_NAT
3. Network bridge
   https://en.wikipedia.org/wiki/Network_bridge
4. Wireless distribution system
   https://en.wikipedia.org/wiki/Wireless_Distribution_System
5. Network address translation
   https://en.wikipedia.org/wiki/Network_address_translation
6. Spanning Tree Protocol
   https://en.wikipedia.org/wiki/Spanning_Tree_Protocol
7. Default gateway
   https://en.wikipedia.org/wiki/Default_gateway
8. RFC 1918: Address Allocation for Private Internets | RFC Editor
   https://www.rfc-editor.org/rfc/rfc1918
9. https://www.rfc-editor.org/rfc/rfc2131
10. Google Scholar  Google Scholar
    https://scholar.google.com/scholar?q=how+to+connect+router+to+router+lan-to-lan+bridge+double+NAT