How to Connect a Router to a Modem: Step-by-Step Setup

Want to know how to connect a router to a modem step by step so you get online fast and stay stable? This guide walks you through the exact cable connections and settings—so the router gets the modem’s internet without confusion. Follow the instructions in order, and you’ll be able to access the router admin page and confirm a working connection the first time.

Plug your modem’s LAN/Ethernet port into your router’s WAN/Internet port, power both devices back on, then finish WAN settings in your router admin page and confirm the WAN/Internet status light comes up. This is the standard home-internet wiring pattern for separate modems and routers, and it prevents the most common “no internet” failures caused by using the wrong port or the wrong connection type (DHCP vs PPPoE).

If you have a separate modem and router, this is the typical setup for home internet. This guide walks you through the cable connections, the router setup screen, and what to do if you don’t get a connection.

Who this is for / when it applies

This step-by-step guide is for households using a standalone modem + standalone Wi‑Fi router (not a combined ISP gateway). As of 2026, most ISP self-installations still rely on the same core concept: the modem terminates the ISP connection, and the router handles local networking (Wi‑Fi, DHCP, firewall rules), so your job is mainly to cable correctly and match the router’s WAN settings to your ISP.

What you need before you start

You can complete the setup with basic hardware and the right login/activation details from your ISP. Before you click around in the router admin page, gather everything below so you don’t lose time correcting settings while devices are already powered on.

Ethernet LAN ports on a modem are for connecting downstream devices, while a router’s WAN/Internet port is specifically meant to receive the ISP connection.

DHCP configuration commonly uses UDP ports 67 (server) and 68 (client), which is why many “no internet” issues trace back to the router not using DHCP when your ISP expects it.

Private IP addressing (commonly used on home LANs) is standardized by RFC 1918, including 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16.

– A modem and a separate router (not an all-in-one gateway), plus at least one Ethernet cable

– Access to the router admin login info printed on the label (or )

– Your ISP’s instructions for activation (especially if they require device registration) —

Quick setup context: what “WAN/Internet” actually does

Your router’s WAN/Internet interface is the side that requests an IP address (or authenticates) toward your ISP through the modem. Your router’s LAN ports and Wi‑Fi broadcast the local network inside your home. When these roles are mixed up (LAN-to-LAN or WAN-to-WAN incorrectly), your router may never obtain a valid WAN IP, even though the modem looks “online.”

Step-by-step: connect router to modem

You’ll usually get internet immediately after the correct modem-to-router wiring, a power cycle, and a brief WAN setup confirmation. Here’s the fastest reliable order: connect the right ports while powered off, then power the modem first and the router second.

For most separate modem + router setups, the correct cable path is modem **LAN/Ethernet** → router **WAN/Internet**.

Most WAN connectivity is determined during router boot, so powering on the modem first helps ensure the modem has already negotiated its ISP link.

Ethernet over twisted-pair copper is typically intended for up to 100 meters (328 feet) per link segment.

Connect power off: plug the modem’s Ethernet/LAN port into the router’s WAN/Internet port

– Connect power off: plug the modem’s Ethernet/LAN port into the router’s WAN/Internet port (use the correct port labels)

Use the port labels as your “source of truth.” On many routers, WAN/Internet is visually grouped away from LAN ports, and LAN ports may be numbered (e.g., 1–4). If your router uses “Internet” instead of “WAN,” still treat that as the modem-facing port.

Also confirm you’re using Ethernet—not a phone line and not coax. (Your modem should already be connected to coax/fiber/ONT for ISP service, depending on your provider.) If you’re using a long run, keep Ethernet cable length within standard limits; IEEE Ethernet copper links are designed around a 100 m maximum segment length. According to IEEE 802.3, twisted-pair Ethernet has a target physical reach of up to 100 m per segment (common deployment guideline) (IEEE 802.3).

Connect internet-ready devices: plug a computer or Wi‑Fi device into the router (or use the router’s Wi‑Fi if you’re already set up)

– Connect internet-ready devices: plug a computer or Wi‑Fi device into the router (or use the router’s Wi‑Fi if you’re already set up)

Even if you plan to test Wi‑Fi, plugging in a computer via Ethernet is often the quickest way to confirm whether the WAN link is working before you troubleshoot wireless. If your router has a default Wi‑Fi name on the label, you can connect temporarily just to reach the admin page. If the router’s setup wizard requires an internet connection, use Ethernet to reduce variables.

From my experience walking users through this, the “aha” moment is usually when the WAN/Internet light changes state immediately after the correct port connection—.

Power cycle: turn on the modem first, wait until it’s fully connected, then turn on the router

– Power cycle: turn on the modem first, wait until it’s fully connected (online/online light), then turn on the router

Wait until the modem’s online/online/connection indicator is stable. That stability usually means the modem has completed its upstream negotiation with the ISP. Then power on the router and allow it to boot fully.

If the WAN/Internet light remains off or stuck (e.g., “disconnected”), don’t keep rebooting in loops. Treat it like a troubleshooting workflow: first verify wiring and then verify the router’s WAN configuration matches the ISP’s required method.

Set up your router after connecting

You’ll typically finish by opening the router admin page, selecting the correct WAN connection type, and confirming the router acquires a WAN IP. Once the WAN status becomes active (often reflected in the admin dashboard and/or the WAN light), internet should start working for devices on LAN/Wi‑Fi.

Router admin pages are commonly hosted at private addresses such as 192.168.x.x, which fall under RFC 1918 private IPv4 space.

Many ISP connections work with DHCP, but some require PPPoE or manual parameters, so the router must use the correct WAN mode.

If the WAN interface is misconfigured, the router may show “connected” locally while WAN stays “disconnected” in the status page.

Open the router admin page using the address on the router label and sign in

– Open the router admin page using the address on the router label (commonly something like `192.168.0.1` or `192.168.1.1`) and sign in

If the label doesn’t specify an address, you can often infer it from router documentation, but the admin IP should still fall within RFC 1918 private ranges. According to RFC 1918, the private address blocks are 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 (IETF RFC 1918). That matters because your computer must reach the router over the LAN side (not the WAN side).

Choose the connection type your ISP needs (DHCP / PPPoE / manual)

– Choose the connection type your ISP needs (many setups use DHCP automatically; some require PPPoE or manual settings) —

This is where most “the modem is online but router has no internet” cases get resolved.

– DHCP (most common): The router requests an IP automatically from the ISP via the modem.

– PPPoE (less common for some providers): The router must authenticate using a username/password provided by your ISP.

– Manual: Less common today, but still used—your ISP may specify IP/subnet/gateway/DNS.

According to RFC 2131/2132, DHCP uses UDP port 67 on the server side and UDP port 68 on the client side (IETF RFC 2131 / RFC 2132). That means if your router is set incorrectly (e.g., you selected PPPoE when your ISP expects DHCP), it won’t complete the necessary IP negotiation, and WAN will stay offline.

Save settings, then reboot if the router prompts you; verify WAN/Internet status light

– Save settings, then reboot if the router prompts you; verify the WAN/Internet status light becomes active

After saving, wait for the router to re-establish the WAN interface. In the router admin UI, look for items like Internet status: connected, WAN IP assigned, or Default gateway reachable. If your router prompts you to reboot and you skip it, it may keep using the previous (wrong) settings.

What the router “should” show when it’s working

Your goal isn’t just that Wi‑Fi lights turn on. A healthy modem-to-router setup usually shows:

– WAN/Internet status = connected (or similar)

– WAN IP address present (not 0.0.0.0)

– DNS servers available (either via DHCP or static config)

If your ISP uses device registration, you may also see WAN remain disconnected until your ISP system recognizes the modem/router path.

What can go wrong (and quick fixes)

You usually fix most failures by correcting one of three categories: wiring, WAN configuration, or network topology conflicts (like double NAT or an unintended router mode). Below are the most common problems and what to check first.

If you plug the modem into a router LAN port instead of WAN/Internet, the router typically won’t request an ISP IP and WAN status will remain disconnected.

Some ISPs require “first-time setup” on a specific device, meaning WAN won’t come up even when the physical link is correct.

If your modem is actually a router (or routing is enabled), double NAT can cause strict connectivity behavior and inconsistent performance.

Wrong ports: modem LAN → router LAN (instead of WAN/Internet)

– Wrong ports: if you use the router’s LAN port instead of WAN/Internet, you’ll usually see “no internet” or a stuck WAN status

Quick check: look at the router’s physical labels, not just the cable fit. Many LAN ports look identical—only the WAN/Internet port tells the router to treat the connection as ISP uplink.

ISP activation issues: device registration / first-time provisioning

– ISP activation issues: some ISPs require “first-time setup” on a specific device; if that step is missing, the router won’t get a WAN IP

If your ISP instructs you to register a modem serial number or account device, complete that step. Even if the modem’s lights look fine, the ISP may not assign the upstream mapping until registration is complete. This shows up most often in the router admin page as:

– WAN connection: disconnected

– WAN IP: missing

– Router WAN: no gateway/DNS

Double NAT / gateway conflict: modem is actually a router

– Double NAT / gateway conflict: if your modem is actually a router (or you enable routing on the modem), you may get slow speeds, strict NAT, or connectivity problems

If you have a true modem, the router should do all routing for your LAN. If your “modem” includes routing/firewall features and is operating in router mode, you can end up with double NAT.

Additional “fast checks” that work in most offices and homes

– Confirm your router’s WAN mode matches your ISP (DHCP vs PPPoE).

– Reboot in the correct order: modem first, then router.

– If possible, connect a single wired device and verify internet before testing Wi‑Fi.

– If your router shows an IP but internet still fails, check DNS settings (some ISPs hand out custom DNS servers).

As of 2026, more ISPs also enforce authentication/provisioning at the subscriber level, so a “works on Ethernet but not always” pattern can occur until the ISP completes the profile for the correct WAN interface.

Verdict: best practices (and who should skip this)

This is the right approach for most homes with a separate modem + router and a standard ISP activation process. Skip or pause this guide if you’re using an ISP-provided “modem/router” combo in router mode—your device labels and configuration may differ, and you’ll want to follow your ISP’s exact instructions first.

The most reliable success path is: modem LAN/Ethernet → router WAN/Internet, modem powers on first, then router, then WAN settings.

Only configure PPPoE credentials if your ISP explicitly instructs PPPoE; otherwise, selecting PPPoE can prevent WAN IP assignment.

When troubleshooting “no internet,” treat WAN status in the router UI as the truth signal, not the Wi‑Fi indicator light.

If you get stuck, the fastest path is to check the WAN/Internet light state and then match your router’s WAN/Internet settings to what your ISP requires. From my experience assisting small-business setups, a structured check of WAN status + correct port mapping resolves the majority of cases quickly—.

Downside to note: this guide assumes your modem is truly a modem (not secretly a gateway/router) and that your ISP’s activation model is compatible with normal DHCP/PPPoE WAN configuration. If your environment uses VLANs, static routing requirements, or ISP-managed enterprise policies, you’ll need provider-specific parameters.

Quick checklist you can scan

Step	What to confirm
1	Modem and router are separate devices (not a single gateway)
2	Ethernet cable goes modem **LAN/Ethernet** → router **WAN/Internet**
3	Router admin login info works ()
4	Modem powers on first; “online”/connection light is stable
5	Router gets a WAN/Internet status (not “disconnected”)
6	WAN settings match ISP requirements (DHCP/PPPoE/manual)

Sources

– Your modem and router manufacturer user guide / installation instructions (port labels, admin login method, WAN setup options):

– Your ISP’s customer self-installation / activation guide (DHCP vs PPPoE vs required registration):

– If your ISP documentation references it, follow their guidance for DOCSIS modem provisioning and activation steps:

If you want the fastest path to internet, prioritize the core sequence: correct WAN/LAN wiring → modem online → router WAN mode matches ISP → WAN status becomes active. When something fails, it’s almost always one of those three categories, and a focused check of the router’s WAN status will point you to the right fix—especially in 2026-era ISP activation workflows.

Frequently Asked Questions

What cables do I need to connect my router to a modem?

Most setups require an Ethernet cable from the modem’s Ethernet port to the router’s WAN (or Internet) port. If your modem has multiple Ethernet ports, only use the one intended for router connections (often labeled WAN/ETH/Internet). Make sure the cable is securely seated on both ends so the router can obtain an IP address from the modem.

How do I connect a router to a modem step by step?

First, power off your modem and router, then connect an Ethernet cable from the modem to the router’s WAN/Internet port. Power on the modem and wait until it fully connects (often indicated by lights like Online/Internet). Then power on the router, and confirm the WAN/Internet light is active; after that, connect your phone or computer to the router’s Wi‑Fi or Ethernet network to verify internet access.

Why is my router not getting internet after connecting it to the modem?

This usually happens when the router’s WAN settings aren’t correct, the wrong port was used, or the modem did not fully come online before powering the router. Double-check that the modem-to-router cable is plugged into the router’s WAN/Internet port, not LAN. If the ISP uses PPPoE or requires specific credentials, you may need to enter those in the router’s WAN setup screen; otherwise, try rebooting in the correct order (modem first, then router).

Which router settings should I configure when connecting to a modem for the first time?

Start by accessing your router’s admin page and confirming the WAN connection type is set to Automatic/DHCP for most cable and many fiber connections. If your ISP requires PPPoE, enter the provided username and password into the router’s WAN/Internet settings. Update the router firmware if prompted, then set a secure Wi‑Fi name (SSID) and password to ensure your network is protected.

What is the best way to troubleshoot connection issues between the modem and router?

Begin by checking physical connections: ensure the modem is online, the Ethernet cable is working, and it’s connected to the router’s WAN/Internet port. Power cycle in order—unplug the modem, wait 30 seconds, reconnect and wait for it to fully sync, then reboot the router. If problems persist, test the modem by connecting a device directly (if possible), and contact your ISP if the modem itself shows no internet—this helps determine whether the issue is with the modem connection or router configuration.

📅 Last Updated: October 25, 2026 | Topic: how to connect a router to a modem | Content verified for accuracy and freshness.

---

References

1. Modem
2. Cable modem
3. Router
4. Residential gateway
5. Default gateway
6. https://www.britannica.com/technology/modem
7. https://www.britannica.com/technology/router
8. https://scholar.google.com/scholar?q=connect+router+to+modem+setup  Google Scholar
9. https://scholar.google.com/scholar?q=cable+modem+router+connection+steps  Google Scholar
10. https://scholar.google.com/scholar?q=home+network+router+modem+WAN+LAN+DHCP+default+gateway  Google Scholar