Bridge Mode Killed My Wi-Fi: How to Fix Access Points

When you put your router in bridge mode, those Wi-Fi access points often stop working. Here's how to get them back online—fast.

The 30-Second Fix: Reboot Everything in Order

I've seen this a dozen times. You flip your router to bridge mode, and suddenly your access points go dark. Nine times out of ten, it's just a power cycle issue. Here's the trick—do it in the right order.

  1. Unplug your main router (the one in bridge mode) and all access points.
  2. Wait 30 seconds. Yes, actually count.
  3. Plug in the main router and let it fully boot—watch for the lights to stabilize, usually 2-3 minutes.
  4. Then plug in each access point one at a time, starting with the one closest to the router.

Had a client last month whose entire office went dark after switching to bridge mode. This got everything back. The access points were just confused about which IP to grab. They need the bridge-mode router to hand out addresses, and a full restart clears the stale DHCP cache.

The 5-Minute Fix: Check DHCP and Static IPs

Still not working? Your access points probably have static IPs that don't match the new network. When you switch to bridge mode, the router's IP range often changes. Here's what to do.

Find the New Network Range

Log into your bridge-mode router. Look at the IP it got from the main ISP modem. Usually it's something like 192.168.1.1 or 10.0.0.1. Write down the subnet mask too—it's almost always 255.255.255.0.

Update Access Point IPs

Each access point needs an IP in that same range. For example, if the router is 192.168.1.1, set an access point to 192.168.1.50, another to 192.168.1.51, and so on. Use a static IP outside the DHCP pool to avoid conflicts.

Access Point 1: IP 192.168.1.50, Subnet 255.255.255.0, Gateway 192.168.1.1
Access Point 2: IP 192.168.1.51, Subnet 255.255.255.0, Gateway 192.168.1.1

Set the DNS to the gateway IP too—it'll forward requests to the ISP. I've seen people leave DNS blank and wonder why internet doesn't work.

The 15+ Minute Fix: Advanced Bridge Mode Setup

If the quick fixes didn't work, something is deeper wrong. This usually happens with mesh systems or older access points that don't like bridge mode.

Step 1: Disable DHCP on the Router

In bridge mode, the router's DHCP should be off. The main ISP router handles IPs. But sometimes bridge mode doesn't disable it automatically. Double-check.

  • Go to the router's DHCP settings.
  • Set it to disabled. Save.

If you can't find the setting, the router might be in "access point mode" instead of true bridge mode. That's fine—access point mode also works, just make sure DHCP is off.

Step 2: Put Each Access Point in Access Point Mode

Most consumer access points (like TP-Link EAPs or Ubiquiti UAPs) have a switch or setting to run as an access point vs. a router. If it's set to "router" mode, it'll try to do its own NAT and DHCP, causing conflicts.

For Ubiquiti: Go to Settings > Wireless > Select the AP > Set Mode to 'Access Point'
For TP-Link EAP: Use the controller software, set operating mode to 'Access Point'

Step 3: Check for Double NAT

Bridge mode should solve double NAT, but if your access points still act as mini-routers, you'll get double NAT. Symptoms: devices on the same network can't see each other, slow internet, weird port forwarding issues.

To check: go to 192.168.1.1 and look at the WAN IP. If it's not a public IP (like 100.64.x.x or a private RFC 1918 address), you've got double NAT. The fix: hard reset the access points to factory defaults and set them up fresh in access point mode.

Pro tip: Write down all access point MAC addresses before resetting. You'll need them to assign static IPs later.

Step 4: Test with a Wired Connection

Plug a laptop directly into an access point's LAN port. Can you get an IP? Can you ping the router at 192.168.1.1? If no, the issue is physical—bad cable, wrong port, or the access point is fried. Had a client once where a cheap Cat5e cable was the culprit. Swapped it to Cat6 and everything worked.

When to Give Up and Reset Everything

If you've tried all this and still have problems, do a factory reset on the main router (30-30-30 rule) and the access points. Then start from scratch. I know it's painful, but it's faster than chasing ghost issues.

Remember: Bridge mode isn't magic. It just tells the router to stop routing and let the ISP device handle everything. Your access points must be set to access point mode and get a valid IP. Do that, and you're golden.

Related Errors in Network & Connectivity
0XC00000CC Fix STATUS_BAD_NETWORK_NAME (0XC00000CC) Fast 0X400D005C NS_I_STOP_CUB 0X400D005C: NetShow Content Server Stopped by Admin DNS_PROBE_FINISHED_NXDOMAIN DNS_PROBE_FINISHED_NXDOMAIN fix that actually works 0X00002649 DNS STATUS CONTINUE NEEDED (0x00002649) Fix Guide

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.