Why This Test Matters
When your internet is slow or unreliable, the problem could be at any of several points: the Wi-Fi radio, the router's NAT engine, the Ethernet cable to the modem, the modem itself, or the ISP's infrastructure. Wi-Fi is the most common culprit, but the router is the second most common — and it is the one that customers and ISPs tend to disagree about most. The modem-bypass test isolates the router definitively. If you connect a laptop directly to the modem and speeds are excellent, your router is the problem. If speeds are still bad directly on the modem, the issue is on the ISP's side.
This test is also the thing ISP support will ask you to do when you call. Running it before you call — and having the results ready — shortens the conversation considerably and gives you evidence that moves the case to a technician dispatch rather than another round of router reboots.
Before You Start: Check Your Setup Type
| Setup Type | Can You Bypass? | How |
|---|---|---|
| Separate modem + separate router | Yes — easy | Disconnect router from modem; plug laptop directly into modem's Ethernet port |
| ISP combo gateway (modem + router in one box) | Partial — use IP passthrough or DMZ mode | Put the router in the gateway's IP passthrough / DMZ, or connect directly if the gateway has multiple LAN ports |
| Fiber ONT + separate router | Yes | Disconnect router from ONT's Ethernet port; plug laptop directly into ONT |
| Starlink or fixed wireless (router built in) | Limited | Starlink has a bypass mode when using a third-party router; most fixed wireless units cannot be fully bypassed |
The Bypass Procedure: Step by Step
- Note your current speeds first: run a speed test from your normal setup so you have a baseline to compare against. Write down the download speed, upload speed, and latency.
- Power everything down: shut down your laptop, turn off the router, and unplug the modem from power. Wait 30 seconds. This matters because the modem will have registered a DHCP lease to the router's MAC address, and needs a moment to clear it so it will issue a new lease to your laptop.
- Disconnect the router: unplug the Ethernet cable connecting your router's WAN port to the modem's LAN port (or the coaxial cable gateway's output port).
- Connect the laptop directly: plug the Ethernet cable into your laptop. If your laptop does not have an Ethernet port, use a USB-to-Ethernet adapter. Do not use Wi-Fi for this test — Wi-Fi is still going through the router's radio, which defeats the purpose.
- Power up the modem first: plug in the modem and wait for it to fully reconnect — this takes 1–3 minutes for cable, 30–60 seconds for fiber. Watch for the online or internet LED to turn solid.
- Run a speed test: once the modem is online, run a speed test from your laptop. Use the same test service you used for your baseline.
- Run a packet loss test: ping 1.1.1.1 with 100 or more packets (
ping -c 100 1.1.1.1on Mac/Linux,ping -n 100 1.1.1.1on Windows) and note whether any packets are lost.
Reading the Results
| Result on Direct Modem Test | What It Means | Next Step |
|---|---|---|
| Speed matches plan; no packet loss | ISP connection is healthy. The problem is in your router, Wi-Fi, or local network. | Test your router — try a factory reset, firmware update, or replacement |
| Speed significantly higher than through router | Router is the bottleneck — CPU overload, SQM/QoS misconfiguration, old hardware, or failing NAT table | Check router CPU load, disable QoS temporarily, update firmware, or replace an old router |
| Speed still slow on direct modem connection | ISP's infrastructure is the problem, not your router or local network | Call your ISP with the direct-modem test result as evidence. This definitively rules out your equipment. |
| Packet loss on direct modem connection | The packet loss is between your modem and the ISP — a line problem | Check modem signal levels, event log, then call ISP for a technician visit |
| No IP address / no connection at all | Modem may need longer to re-register, or ISP may need to see your laptop's MAC address | Wait 3–5 minutes; power cycle the modem again; if still no connection, call ISP |
The MAC Address Problem
Some ISPs bind the modem connection to the MAC address of the device they last saw on the WAN port — usually your router's MAC. When you plug in a laptop directly, the modem sees a different MAC address and may not hand out a DHCP lease. This is why the 30-second modem power-cycle after disconnecting the router is important. If you still get no IP after waiting, a longer modem reboot (unplug for 2 minutes) usually clears the binding. In rare cases, especially with some ISP-provided equipment, you may need to call the ISP to release the MAC binding from their side.
If the Router Is the Problem: What to Check
When the direct modem test shows good speeds but speeds through the router are poor, work through these in order:
- Check the Ethernet cable between the modem and router's WAN port — a failing cable causes intermittent and hard-to-diagnose slowdowns. Swap it with a known-good cable.
- Log into the router's admin page and check CPU and memory utilization. A router with CPU above 80% under normal load is struggling — this happens with heavily connected households, high peer-to-peer traffic, or aggressive QoS/DPI settings.
- Disable QoS or SQM temporarily and retest. These features are CPU-intensive on older routers and can limit throughput on fast connections.
- Check that the router's WAN port has negotiated the correct link speed (it should show 1Gbps for a Gigabit connection, not 100Mbps — a speed mismatch cuts throughput dramatically).
- Update router firmware. Many throughput and stability bugs are fixed in firmware updates that owners never apply.
Frequently Asked Questions
Will connecting directly to the modem damage anything?
No. Connecting a laptop directly to the modem is a normal diagnostic procedure. The modem does not care what device is on its Ethernet port. The only practical concern is security — your laptop gets a public or semi-public IP address directly from the ISP while connected this way, bypassing the router's NAT firewall. Do not leave it connected this way longer than needed for the test, and avoid doing anything sensitive (online banking, etc.) while bypassed.
My ISP gave me a combo modem/router gateway. Can I still do this test?
Not in the pure sense, because the modem and router are one device. However, you can test within the gateway by connecting your laptop via Ethernet directly to one of the gateway's LAN ports and running a speed test. This bypasses Wi-Fi and isolates whether Wi-Fi is the problem. If speeds on a wired LAN port of the gateway are also poor, the issue is either the gateway itself or the ISP connection coming into it. You can then call the ISP and tell them you tested on a wired connection directly on their device and still get slow speeds — that shifts responsibility to their equipment.
I get a great speed on the direct modem test. How do I fix the router?
Start with the cable between the modem and router's WAN port — swap it even if it looks fine. Then check the router's admin panel for CPU load, update firmware, and temporarily disable any advanced features like QoS, traffic monitoring, or parental controls. If throughput improves when features are disabled, that feature is the bottleneck — either the router's hardware is underpowered for those features at your connection speed, or the feature has a configuration problem. If nothing helps, a router replacement is often the most cost-effective fix, particularly if the router is more than 4–5 years old.
The speed was fine on the direct modem test, but the problem is only at certain times of day. What now?
Time-of-day problems on a direct modem connection point to ISP congestion or a line issue that worsens under load. Document the problem with timestamps — run your speed test and a 200-packet ping to 1.1.1.1 every hour between 5 and 10 pm and record the results. If the direct-modem test also shows degradation in the evening, call your ISP and provide the time-stamped results. Evening congestion at the neighborhood node is an ISP capacity problem, not something you can fix with router settings.