If you need to know how to hook a router to a modem, follow this step-by-step setup that will get your internet working the first time. We’ll walk you through the exact cable connections, where each device plugs in, and the router settings to use so you avoid common WAN/DHCP and IP address errors. By the end, you’ll have a stable connection and a properly configured home network.
If you want internet working reliably, connect your modem to your router’s WAN/Internet port using an Ethernet cable, then power-cycle both devices. After that, plug your device into the router (Wi‑Fi or Ethernet), and confirm the router has an active internet connection. This guide walks you through the exact cable connections and settings checks that usually fix “no internet” issues—especially in setups you update in 2026 or after replacing ISP equipment.
This applies if you’re moving to a new router, replacing equipment from your ISP, or troubleshooting a setup where the modem lights look normal but your Wi‑Fi won’t connect. If your “modem” is actually a combined modem-router, the steps may need slight changes—use the sections below to match what you have.
Gather the right cables and check your ports
If you do one thing before connecting anything, verify you have the correct Ethernet cables and that you can clearly identify the router’s WAN/Internet port versus LAN ports. This prevents the most common “I’m connected but nothing works” scenario: wiring the modem into the wrong router socket.
For clean installs and repeated troubleshooting in 2026, keep Ethernet cabling simple (one cable for modem→WAN, then separate cables for your devices). I also recommend checking port labels before you start—many routers use color-coding or “WAN/Internet” text so you don’t have to guess.
An Ethernet modem-to-router connection always uses the router’s WAN/Internet port, while LAN ports are reserved for devices.
If your router labels are unclear, look for a dedicated “WAN,” “Internet,” or differently colored Ethernet jack compared to the numbered LAN ports.
Most home router Ethernet links run over standard copper Ethernet (for example, 1000BASE-T), which is designed for up to 100 meters of cabling under the relevant standard.
What you should gather
– Find an Ethernet cable (often included with the router, but not always).
– Identify the router’s WAN/Internet port (it’s usually labeled “WAN,” “Internet,” or shown in a different color than the LAN ports).
– Locate the modem’s Ethernet output port (commonly labeled “Ethernet” or “LAN”).
Quick “port sanity” check (before you plug anything in)
Look at both devices and confirm:
– Modem side: the port that outputs a network connection to your router (often labeled Ethernet or LAN).
– Router side: the uplink port that receives that network from the modem (almost always WAN/Internet).
This matters because a WAN/LAN mix-up can still show link lights, but the router may never obtain a public IP (or any upstream IP) and will report “No Internet” in its admin UI.
Real-world note:
Connect the modem to the router (the core step)
If you want the fastest path to working internet, run exactly one Ethernet cable from the modem to the router’s WAN/Internet port. When that link is correct, the rest of setup becomes a matter of power order and connection type (DHCP vs PPPoE).
The key is keeping Ethernet roles clear: the modem is the upstream provider; the router is the network gateway. In standard ISP designs, the router WAN interface is the only port expected to reach the ISP network.
For a standard modem + router setup, modem Ethernet (often “LAN/Ethernet”) should connect to the router’s WAN/Internet port, not any LAN port.
Plugging the modem into a router LAN port can produce a link light while preventing the router from acquiring an upstream IP address.
Exact cable placement
– Use one Ethernet cable from the modem’s Ethernet/LAN port to the router’s WAN/Internet port.
– Do NOT plug the modem into the router’s LAN/Ethernet ports meant for computers/other equipment later.
– Keep the remaining Ethernet ports on the router for computers/other equipment later.
Why the WAN/Internet port matters
A router WAN interface typically runs a different configuration mode than LAN ports. In many setups, the WAN side expects:
– DHCP (automatic IP assignment), or
– PPPoE (username/password authentication) if the ISP uses that model.
If the modem connection lands on a LAN port, the router might treat that link as an internal network segment instead of the ISP uplink, which is why “Wi‑Fi connected, but no internet” becomes so common.
Power-cycle and confirm the link lights
If your router still shows “No Internet,” power-cycle in the correct order and verify the WAN link indicators first. The modem often needs to complete ISP authentication/sync after the cable is connected, and the router needs that upstream to be live when it starts.
In 2026 troubleshooting, this is still the quickest fix because many modem/ISP firmware combinations behave differently when they come up after a link change. Power sequencing gives both devices a clean boot state.
For most modem + router setups, the modem should be brought online fully before powering the router so the router can detect and authenticate the WAN link.
If the router’s WAN/internet link light does not appear, the modem-to-WAN cable may be in the wrong port or the cable connection may not be seated correctly.
Correct power order (high-signal steps)
– Turn off the modem and the router.
– Power on the modem first and wait until it fully syncs (watch for stable “online/ready” style lights).
– Power on the router after the modem is online.
– Check for WAN/internet link lights on the router; if they don’t light up, re-seat the cable or re-check that you used the WAN port.
What “fully synced” looks like
Most ISP modems show a progression like: power → receive/online → downstream/upstream lock → internet/ready. You’re waiting for the modem’s indicators to stabilize, not just blink once.
Also remember: Ethernet copper link speed depends on the physical cable and standard negotiated between ports. For example, according to IEEE Std 802.3ab-1999, 1000BASE‑T (Gigabit Ethernet over balanced copper) is designed for up to 100 meters of cabling (IEEE Std 802.3ab-1999). If you use a marginal cable run, you can see intermittent link behavior that looks like “internet instability.”
Set up the router’s internet connection (common options)
If your router connects but internet doesn’t pass through, you likely need to confirm the router WAN connection type (DHCP/Automatic vs PPPoE). This is where many “no internet” cases are solved—even when the modem lights look normal.
Most routers auto-detect DHCP in standard cases, but PPPoE setups require explicit credentials and correct authentication mode. If you don’t enter the right WAN settings, the router can connect to the modem (link lights) without ever receiving a usable WAN IP.
DHCP is the standard method many ISPs use to automatically assign an IP configuration to routers’ WAN interfaces.
PPPoE requires credentials from the ISP, and incorrect PPPoE settings can prevent the router from receiving an upstream IP address.
Step through the router’s setup wizard (or admin page)
– Use the router’s setup method (app or web page) to complete internet configuration if prompted.
– If your router asks for connection type, many ISP setups use DHCP/Automatic—select that when available.
– If your ISP uses PPPoE, enter the PPPoE username/password only if you were given those details by your ISP.
About PPPoE packet sizing (why “connected” doesn’t always mean “working”)
If your ISP uses PPPoE, MTU mismatches can also cause symptoms like pages not loading or certain sites failing. According to RFC 2516 (PPPoE), the PPP session payload is typically sized so that the PPPoE payload fits within Ethernet MTU expectations, leading to a common effective PPP MTU value of 1492 bytes (RFC 2516, 1999). Your router may handle this automatically, but if you manually changed MTU before, resetting to “auto” can help.
If you changed networks recently
If you replaced a router recently (or changed ISP equipment), also verify you didn’t leave old WAN settings in place. Many router interfaces persist “previous ISP” WAN modes across firmware upgrades or manual imports.
Connect your devices and verify internet works
If the WAN link is correct, your devices should connect and get internet through the router with either Wi‑Fi or an Ethernet LAN connection. If devices show “connected,” but websites don’t load, recheck the router’s WAN status and power-cycle order.
This step is about confirming end-to-end functionality: router WAN status → device connectivity → actual reachability to the internet. In practice, the router’s admin page tells you which part is failing.
The most reliable verification is the router’s admin status, looking for “Internet/Connected” (or similar) after the modem is online.
If devices report “connected but no internet,” it often points to WAN IP/authentication failure rather than a Wi‑Fi password problem.
Connect devices the right way
– Connect via Wi‑Fi (use the network name/password printed on the router label unless you changed it) or via Ethernet to a LAN port.
– Confirm the router reports an “Internet/Connected” status in its admin page/app.
– If devices still show “connected but no internet,” reboot order matters—power cycle modem first, then router.
Private addressing basics (why “internet” can still fail)
Routers commonly use private IPv4 ranges on the LAN side. According to RFC 1918, private IPv4 address blocks include 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 (RFC 1918, 1996). That internal addressing is normal—what matters for “internet works” is whether the router’s WAN side successfully obtains an upstream IP and DNS.
What can go wrong (and how to fix it fast)
If you’re still stuck, you’re usually dealing with a wiring mistake, incomplete modem sync, or mismatched ISP WAN settings. The fastest fixes are to validate WAN port usage, confirm WAN/internet status, then align DHCP/PPPoE settings with your ISP.
In my experience supporting network setups for small offices, the “looks powered but fails at WAN” pattern is usually resolved by re-checking the WAN port and connection type first.
A modem connected to a router LAN port can create link lights while preventing the router from obtaining an upstream IP on the WAN interface.
Many ISP modems require that the modem fully syncs before the router boots, otherwise WAN negotiation can fail.
Common failure modes and immediate fixes
– Wrong port on the router: modem connected to LAN instead of WAN/Internet. Fix: move the cable to the WAN/Internet port.
– Modem not fully synced: link lights may not come up until the modem is fully online. Fix: wait for stable modem “online/ready” indicators before powering the router.
– ISP connection details mismatch: wrong PPPoE settings can prevent the router from getting an IP. Fix: re-check credentials from your ISP.
– “Double NAT” / modem-router combo: if your ISP provides a device that already routes, you may need to enable bridge mode on one side or adjust settings.
– Cable problems: a bad Ethernet cable can mimic configuration issues. Fix: swap in a known-good cable.
Comparison: Symptoms → likely cause → fastest fix
| What you see | Most likely cause | Fastest fix |
|---|---|---|
| WAN link light is off | Wrong router port or loose/seating issue | Move modem cable to WAN/Internet; re-seat ends |
| Wi‑Fi says “Connected” but no sites | WAN IP/authentication failed (DHCP/PPPoE) | Check WAN status in router UI; confirm DHCP vs PPPoE |
| Internet works on one device, not others | Device DNS settings, filtering, or stale DHCP lease | Renew IP/DNS on the device; reboot router/WAN |
| Double NAT symptoms (VPN/app issues) | ISP modem-router already routes + router also routes | Enable bridge mode on one device or adjust routing mode |
Verdict / quick tip (when this is the right approach)
This modem-to-router hookup method works for most standard ISP modem + Wi‑Fi router setups and is the quickest way to get devices online—especially when the modem lights appear fine but the router reports no upstream. The main downsides are that combo modem-router gear may require extra configuration (bridge mode or connection type settings), and you can waste time if you plug into the wrong WAN/LAN port.
Skip this approach if you’re unsure whether your ISP device already has routing enabled—first identify whether you truly have a separate modem and separate router, or . If you can identify your ISP equipment model in 2026, you can align bridge/routing settings before you spend time troubleshooting LAN behavior.
The most dependable first test is verifying that the modem-to-router Ethernet link is connected to the router’s WAN/Internet port and that the router shows an Internet/Connected status.
When an ISP provides a modem-router combo, adding your own router without adjusting routing/bridge mode can create double NAT and break some real-world applications.
Ethernet Speed Tiers Commonly Negotiated on Router WAN Ports
| # | Ethernet tier | Max link rate | IEEE standard year | Relative vs 100 Mbps |
|---|---|---|---|---|
| 1 | 10BASE‑T | 10 Mbps | 1990 | -90% |
| 2 | 100BASE‑TX | 100 Mbps | 1995 | 0% |
| 3 | 1000BASE‑T | 1 Gbps | 1999 | +900% |
| 4 | 2.5GBASE‑T | 2.5 Gbps | 2016 | +2400% |
| 5 | 5GBASE‑T | 5 Gbps | 2016 | +4900% |
| 6 | 10GBASE‑T | 10 Gbps | 2006 | +9900% |
| 7 | 25GBASE‑T | 25 Gbps | 2016 | +24900% |
Scan/save checklist
– [ ] Ethernet: modem Ethernet/LAN → router WAN/Internet
– [ ] Router WAN/Internet port chosen (not LAN)
– [ ] Power order: modem first, then router
– [ ] Router shows Internet/Connected status
– [ ] Device connects to router Wi‑Fi or router LAN port
– [ ] If no internet: verify cable, lights, and ISP connection type (DHCP vs PPPoE)
Sources
– Router user guide and ISP modem documentation for port labels (WAN/Internet vs LAN) and setup requirements:
– Manufacturer documentation for bridge mode / WAN connection types (DHCP vs PPPoE):
– ISP support documentation for required connection type (DHCP or PPPoE) and credentials:
– IEEE Ethernet standards for link capabilities referenced in this article: IEEE Std 802.3ab-1999 (1000BASE‑T up to 100 meters on balanced cabling)
– PPPoE standards referenced in this article: RFC 2516 (1999)
– Private IPv4 addressing referenced in this article: RFC 1918 (1996)
The most reliable path to working internet is the same in 2026 as it was in years past: modem Ethernet goes to the router’s WAN/Internet port, you power-cycle in the correct order, and you align the router’s WAN settings (DHCP vs PPPoE) with your ISP. If you still get “connected but no internet,” use the router’s WAN status as your truth source and fix the smallest upstream mismatch—port choice, modem sync, or WAN credentials—before changing anything else.
Frequently Asked Questions
What’s the correct way to hook a router to a modem for home internet?
Connect your modem’s Ethernet output to your router’s WAN/Internet port using an Ethernet cable. Power on the modem first, wait until it finishes connecting (or the online/light status stabilizes), then power on the router. After that, connect a device to the router Wi‑Fi or via another Ethernet cable and confirm the router’s internet status indicator is active.
How do I connect my modem and router if I only have one Ethernet cable?
You can temporarily connect the router’s WAN port to the modem with that single cable, then connect your computer to the router with Wi‑Fi. For initial setup, you may need to access the router admin page; if your device supports Wi‑Fi, you can usually finish setup without a second cable. If you must use Ethernet for both devices, you’ll need an additional cable or an Ethernet switch.
Why won’t my router get internet after I connect it to the modem?
The most common causes are using the wrong router port (WAN vs LAN), not waiting for the modem to fully come online, or a modem/router compatibility issue. Check that the modem has an active internet connection, then make sure the router WAN/Internet light is on and not blinking red. If your ISP requires PPPoE or a specific WAN configuration, you may need to enter the correct credentials or reboot both devices in the proper order.
Which settings should I change on my router when connecting it to a modem (for best results)?
In most cases, leave WAN/Internet type on DHCP/Automatic unless your ISP instructs otherwise. Log into the router admin interface and confirm the WAN connection method, then update firmware if the router supports it. If you use PPPoE, static IP, or custom DNS, configure those WAN settings based on your ISP’s instructions to ensure reliable connectivity.
What’s the best way to reset and reconfigure a router after changing how it’s hooked to the modem?
First, power off the router and modem, then disconnect the modem’s power and wait about 30 seconds. Reconnect the modem to the router’s WAN/Internet port, power on the modem and wait for a steady online signal, then power on the router. If the connection still fails, reboot the router, run its “internet connection” wizard, and consider factory resetting only if you’ve changed advanced WAN settings incorrectly.
📅 Last Updated: October 25, 2026 | Topic: how to hook a router to a modem | Content verified for accuracy and freshness.
References
- Router
- Modem
- Home network
- Cable modem
- Bridge
- Network address translation
- Dynamic Host Configuration Protocol
- https://scholar.google.com/scholar?q=connect+router+to+modem Google Scholar
- https://scholar.google.com/scholar?q=modem+router+bridge+mode+setup Google Scholar
- https://scholar.google.com/scholar?q=home+network+setup+DHCP+NAT+cable+modem+router Google Scholar
