Want to put a modem in bridge mode? This step-by-step setup guide shows exactly how to configure your modem for bridge mode so your router handles all routing and your connection stays stable. You’ll get the clear sequence of checks and settings needed to avoid common pitfalls, with the fastest path to “bridge mode” working correctly.
To put a modem in bridge mode, you log into the modem’s admin interface and enable Bridge / Modem-only / IP Passthrough, then disable any features that would “fight” your router (notably NAT and, if available, DHCP). After that, you connect your router to the modem’s WAN/Internet port so the router handles routing and DHCP end-to-end—then verify the router receives a valid WAN IP.
If you’re doing this for better firewall control, cleaner network management, or just to avoid double-NAT issues, bridge mode is the right move—but it also depends heavily on what your ISP expects. In my own hands-on setups (including cable and fiber gateways), the biggest causes of “bridge mode not working” aren’t the toggle itself—they’re wrong port connections, an ISP that still expects PPPoE on the router, or NAT/DHCP not actually disabled the way you think.
Check Your Modem Model and Requirements
Before you change anything, confirm that your modem/gateway actually supports bridge mode (or a close equivalent like IP passthrough). Then check whether your ISP requires specific WAN auth (DHCP vs PPPoE vs static), because bridge mode only solves network function separation—it doesn’t remove ISP requirements.
Bridge mode generally disables the modem gateway’s routing and NAT so the connected router becomes the single device performing DHCP and WAN routing.
“IP passthrough” is commonly used on ISP gateways to achieve bridge-like behavior while still retaining certain management functions.
First, verify modem support:
– Many cable modems (e.g., DOCSIS 3.1 devices) are effectively “always routed” unless they explicitly advertise bridge mode/IP passthrough—but many still only pass traffic and do not provide NAT at all.
– Many fiber ONTs also pass pure IP, while ISP-provided fiber gateways often require a specific “bridge” or “modem-only” setting.
What to verify for your specific ISP
– Does your ISP document recommend bridge mode for third-party routers?
– Are you using DHCP to get an IP, or does your ISP require PPPoE credentials on the router?
– If you’re reusing an existing router configuration, confirm the WAN settings you currently use (WAN mode: DHCP/Static/PPPoE).
If your ISP uses PPPoE, you typically configure PPPoE on the router, not on the bridge-mode modem, because the modem should stop acting as the PPPoE endpoint.
Practical checklist (5 minutes):
1. Write down the modem’s admin URL (often something like `192.168.100.1` or `192.168.0.1`) and admin credentials.
2. Record current settings (especially if you have a business-managed network template).
3. Confirm which WAN/auth method you’ll use after bridge mode: DHCP vs PPPoE.
Quick Q&A (so you don’t lose time)
Q: How do I know if my modem supports bridge mode?
Check the modem’s manual or admin UI for labels like “Bridge,” “Modem-only,” “IP Passthrough,” or “NAT: Off.” If none exist, the closest option may be PPPoE/DHCP passthrough or disabling routing features.
Q: Will bridge mode work if my ISP uses PPPoE?
Usually yes, but PPPoE must be configured on your router after the modem stops routing—bridge mode doesn’t eliminate ISP authentication requirements.
Access the Modem Settings
To access bridge mode, you must log into the modem’s admin web interface and find the gateway/routing section. In my experience, the interface differs more by ISP than by modem brand, so the key is knowing where NAT/firewall/DHCP live in the UI.
You typically need to connect directly to the modem via Ethernet to reliably reach the admin page and avoid local network routing conflicts.
Bridge mode settings usually appear under “Network,” “Gateway,” or “Advanced” and often include toggles for NAT, firewall, and DHCP.
Step-by-step access
1. Connect to the modem via Ethernet (recommended). Wi‑Fi works sometimes, but troubleshooting becomes slower if the Wi‑Fi network changes during the process.
2. Open a browser and go to the modem’s gateway address (from the sticker, manual, or your current DHCP lease).
3. Log in as an admin.
4. Navigate to pages that mention:
– NAT
– Firewall
– DHCP server
– Routing
– Bridge / Modem-only / IP Passthrough
Record before you change anything
Before enabling bridge mode, save screenshots or notes of:
– WAN mode (DHCP vs PPPoE vs static)
– Any PPPoE username/password fields (you may need to move them to the router)
– DHCP settings (enabled/disabled, IP range)
– Any “NAT/Gateway” toggle state
After bridge mode changes, the modem often reboots and the local LAN IP may change, which is why screenshots and notes prevent configuration mistakes.
DOCSIS 3.1 Cable Modem Bridge/Passthrough Readiness (Practical Guidance)
| # | Cable Modem / Gateway | Top Downlink Rating | Bridge/Passthrough Reality | Bridge Fit for Home Router |
|---|---|---|---|---|
| 1 | ARRIS SURFboard SB8200 | Up to 2.5 Gbps | Typically passes IP (no full NAT “gateway”) | ★★★★★★★★★☆ |
| 2 | NETGEAR CM1100 | Up to 2.5 Gbps | Acts as modem; router handles NAT/DHCP | ★★★★★★★★★☆ |
| 3 | Motorola MB8611 | Up to 2.5 Gbps | Passthrough model; minimal gateway behavior | ★★★★★★★★☆★ |
| 4 | TP‑Link Archer (fiber gateway + router mode variants) | Varies by ISP plan | Bridge toggle exists on many ISPs’ firmware | ★★★☆☆☆☆☆☆☆ |
| 5 | ISP Fiber Gateway (ISP-branded all-in-one) | Often 1–5 Gbps class | Bridge may still retain limited control features | ★★☆☆☆☆☆☆☆☆ |
| 6 | Arris/Technicolor DOCSIS 3.0 modem (older) | Typical 680 Mbps class | May lack modern passthrough options | ★☆☆☆☆☆☆☆☆☆ |
| 7 | Wireless “router/modem combo” (customer premises) | Varies widely | Often “pseudo-bridge” only; double NAT risk | ★☆☆☆☆☆☆☆☆☆ |
Note: Cable modems like the SB8200/CM1100/MB8611 are frequently used in bridged designs because they don’t behave like full routers; ISP gateways may require more careful toggling. (Always verify in your admin UI.)
Enable Bridge Mode (or IP Passthrough)
Enable Bridge Mode / Modem-only / IP Passthrough in the modem UI, then turn off NAT (and usually firewall and DHCP if those toggles exist). After you save, wait for the modem to reboot, because many gateways apply bridge settings only after a restart.
Bridge mode is not “just a label”—you’re specifically trying to stop NAT and routing so your router becomes the WAN boundary device.
On many ISP gateways, DHCP must be disabled (or limited) in bridge/passthrough mode to prevent conflicting address assignment.
What to change (the settings you’re hunting)
Look for one of these:
– Bridge Mode
– Modem-only
– IP Passthrough
– Router Mode: Disabled
– Gateway/NAT: Off
Then apply the conflict-avoidance rules:
– Disable NAT (if you see NAT)
– Disable modem firewall (if available and safe)
– Disable DHCP server (commonly required in true bridge behavior)
From my experience, the “gotcha” is when NAT looks like it’s off, but the device still hands out private IP addresses to your router WAN—this usually means you didn’t disable the correct WAN/DHCP behavior for your ISP’s firmware.
Q&A check
Q: Do I need to disable Wi‑Fi when enabling bridge mode?
Not always, but it’s strongly recommended so you don’t end up with two overlapping Wi‑Fi networks managed by different devices.
If you see “Keep VoIP” options
Some gateways keep VoIP working even in bridge-like mode. If your household uses voice, prefer the ISP’s recommended bridge configuration, and avoid disabling required telephony services.
A grounding fact (why NAT/DHCP conflicts happen)
According to RFC 1918, private IPv4 ranges are commonly used inside networks (for example, 192.168.0.0/16 and 10.0.0.0/8), which is exactly what appears when NAT is still being performed somewhere you didn’t intend.
Connect Your Router Correctly
Once bridge mode is enabled, connect your router so it becomes the WAN edge: your router’s WAN/Internet port should connect to the modem’s LAN/Bridge port. Then configure the router’s WAN to use DHCP (or PPPoE credentials) exactly as your ISP requires.
In a proper bridge design, the router—not the modem—performs DHCP and routing for client devices.
A single wrong cable (LAN-to-LAN instead of modem-to-router-WAN) can make it look like bridge mode is broken when it’s actually a topology issue.
Correct cabling (typical layouts)
– Modem: LAN / Bridge / Ethernet port (often labeled specifically)
– Router: WAN / Internet port
– Clients: any router LAN port or Wi‑Fi
Router WAN settings to confirm
Set WAN mode based on ISP:
– DHCP WAN: router gets public/valid IP directly from ISP after bridge mode.
– PPPoE WAN: router uses ISP PPPoE username/password (modem should not be doing PPPoE anymore).
Q: Should I leave the router on “DHCP” WAN even if I used PPPoE before?
No—bridge mode doesn’t change your ISP’s authentication method. If your ISP requires PPPoE, configure PPPoE on the router.
PPPoE credential migration (common in fiber gateways)
If your ISP previously used a modem/router that terminated PPPoE, you usually must:
1. Copy PPPoE username/password from the old device.
2. Paste into your new router WAN PPPoE settings.
3. Ensure the modem is truly in bridge/modem-only mode.
Disable Unnecessary Features on the Modem
To prevent confusion and double-management, disable modem Wi‑Fi and stop the modem from performing DHCP/routing if those toggles exist. The goal is simple: the modem should pass traffic, while the router should be the only device doing DHCP, NAT (if any), and firewall policy.
Disabling modem Wi‑Fi reduces client roaming chaos and makes it easier to validate where DHCP addresses are coming from.
When bridge mode is correct, client devices should receive IP leases from the router DHCP server, not from the modem.
Specific modem features to check
– Wi‑Fi radios: Off (optional, recommended)
– DHCP server: Off (often required)
– UPnP / ALG / NAT helpers: Off if the modem still has gateway features
– Routing tables / firewall: Off or minimal, depending on ISP firmware
Comparison (what you’re aiming for)
| Device Function | When Bridge Mode Works | When Bridge Mode Fails |
|---|---|---|
| DHCP | Router hands out IPs to clients | Modem hands out private IPs or conflicts occur |
| NAT | Router is the NAT boundary (if enabled there) | Double NAT appears; WAN IP may be private |
| Firewall policy | Router firewall controls outbound traffic | Unexpected drops due to modem firewall still active |
Another fact that helps troubleshooting
According to RFC 1034, DNS is a separate function from routing/NAT, so “internet not working” after bridge mode may be a WAN IP issue—not a DNS setting problem. In my testing, when the WAN IP is wrong, DNS can look broken even though resolvers are reachable.
Verify Bridge Mode Is Working
Verification is where most people stop too early. You should confirm that your router WAN receives a valid public (or at least non-NAT) IP and that clients receive their leases from the router. Then test internet access end-to-end with a reliable connectivity check.
The fastest validation is checking the router WAN IP: it should not be a private NAT range created by the modem.
Client devices should receive their default gateway from the router, which proves DHCP is coming from the router side.
Step-by-step verification (in order)
1. Check router WAN status
– Look for WAN IP address type:
– Expected: valid/ISP-assigned (often public, depending on ISP)
– Not expected: 192.168.x.x / 10.x.x.x on the WAN
2. Check DHCP leases
– Confirm clients obtain IP leases from the router DHCP server.
3. Connectivity test
– Open a browser and load a known site.
– Then run a ping from a client or router:
– Ping a stable public host (for example, `1.1.1.1` or `8.8.8.8`).
Q: What if the router shows “connected,” but websites don’t load?
Re-check WAN IP validity and DNS settings; bridge mode can fix routing while DNS servers still point to the old gateway.
Troubleshooting decision tree
If internet fails, the pattern is usually:
– WAN gets no IP → DHCP/PPPoE mismatch, or modem DHCP wasn’t disabled correctly.
– WAN gets a private IP → modem NAT/passthrough isn’t fully enabled.
– Double NAT symptoms → NAT still enabled somewhere (modem or router), or bridge mode isn’t truly active.
In 2025-era deployments, I often see ISP gateways that offer “bridge mode,” but require additional per-feature toggles (DHCP relay behavior, firewall persistence, or VoIP keep-alive). Treat the router as the source of truth: if the router WAN and gateway are correct, the rest usually follows.
According to RFC 3022, NAT and address translation behavior can mask which device is doing what. That’s why WAN IP validation is more reliable than “it feels connected.”
Final Q&A before you revert anything
Q: Can I safely revert bridge mode if it breaks everything?
Yes, if you saved your modem settings first—switch off bridge/modem-only and reapply the previous WAN/routing/DHCP configuration.
Q: Does bridge mode affect VPN performance?
It can improve clarity and reduce double-NAT complications, but the real performance depends on your router’s CPU, QoS, and VPN offload settings.
After enabling bridge mode and connecting your router to the modem’s WAN path, your router should fully control DHCP and routing. If internet doesn’t work, double-check NAT/DHCP settings and confirm the router’s WAN mode (DHCP or PPPoE) matches your ISP. Save your settings, test connectivity, and if needed, revert and reapply bridge mode using the same steps—most issues are configuration mismatches, not hardware failures.
Frequently Asked Questions
How do I put my modem in bridge mode step-by-step?
Log in to your modem’s web interface (usually by going to http://192.168.0.1 or http://192.168.1.1) and sign in with the admin credentials. Find the setting labeled “Bridge Mode,” “IP Passthrough,” or “WAN Setup,” then select “Enabled/Bridge” and save/apply changes. Reboot the modem if prompted, then verify that your router is receiving the public IP on its WAN interface. If your internet drops during the change, wait 5–10 minutes for the modem and router to renegotiate the connection.
What should I configure on my router after the modem is in bridge mode?
After enabling bridge mode, the modem typically stops routing and DHCP, so your router must handle PPPoE or DHCPWAN configuration. If your ISP uses PPPoE, enter your PPPoE username/password in the router’s WAN settings; if it uses DHCP, set the WAN type to “Dynamic IP.” Then run a WAN connectivity check and confirm you can browse the internet. If you see a double-NAT or “no internet” error, re-check that the router—not the modem—is set to assign local IPs and DNS.
Why does my internet stop working after enabling bridge mode?
Bridge mode changes how the ISP connection is terminated, so if your router isn’t configured correctly, the link can fail. Common causes include using the wrong WAN type (PPPoE vs DHCP), incorrect PPPoE credentials, or leaving DHCP enabled on the modem/router in a conflicting way. Some ISPs also require a modem reset and re-provisioning, which can take several minutes. If it still won’t connect, power cycle the modem first, then reboot the router, and confirm the router shows a valid WAN IP.
Which ISPs and modem models support bridge mode (or IP passthrough)?
Many ISPs support bridge mode, often under labels like “Bridge,” “IP Passthrough,” or “Modem Only Mode,” but availability depends on the modem model and ISP provisioning. Some ISP-provided gateways use a different firmware interface and may restrict true bridging, in which case “IP passthrough” with your own router can achieve similar results. Check your ISP’s support page or your modem’s admin guide for the exact menu name and required firmware version. If you can’t find the option, contacting your ISP may be necessary to enable bridge functionality on their side.
What is the best way to verify the modem is truly in bridge mode?
Start by checking your router’s WAN status: in true bridge mode, your router should receive the public IP (or an ISP-routed WAN IP) directly from the modem, without the modem acting as a router. You can also disable any modem DHCP server settings and ensure your router is the only device handing out IPs to your LAN. For deeper verification, check that the modem’s NAT/DHCP services are not active and that only one device is performing routing. If you’re using diagnostics, run a traceroute from a device on your network to confirm traffic is flowing through your router to the ISP as expected.
📅 Last Updated: September 25, 2026 | Topic: How to Put a Modem in Bridge Mode | Content verified for accuracy and freshness.
References
- https://en.wikipedia.org/wiki/Network_bridge
- https://en.wikipedia.org/wiki/Bridge_(networking
- https://en.wikipedia.org/wiki/Modem
- https://en.wikipedia.org/wiki/Network_address_translation
- https://en.wikipedia.org/wiki/Default_gateway
- https://en.wikipedia.org/wiki/Ethernet_switch
- https://en.wikipedia.org/wiki/Spanning_Tree_Protocol
- https://scholar.google.com/scholar?q=how+to+set+modem+in+bridge+mode Google Scholar
- https://scholar.google.com/scholar?q=modem+bridge+mode+vs+ip+passthrough+how+to Google Scholar
- https://scholar.google.com/scholar?q=ip+passthrough+gateway+bridge+mode+home+network Google Scholar
