What double NAT actually breaks
With two NAT layers stacked (one on the ISP device, one on your own router), incoming connections initiated from outside β the exact thing port forwarding is meant to enable β have to correctly traverse both layers, and most ISP gateways are not designed to forward ports to a device that is itself acting as a router. This commonly breaks inbound game connections, certain peer-to-peer applications, some VPN passthrough scenarios, and remote access to devices like a NAS or security camera.
What to do if your ISP device cannot fully bridge
Some ISP equipment, particularly certain fiber ONTs, cannot be fully bridged because it needs to retain some management function. In that situation, two common workarounds exist: placing your own router's WAN IP address in the ISP device's DMZ settings (which forwards essentially all traffic to it, functioning similarly to bridge mode), or disabling the ISP device's Wi-Fi and routing entirely and using it purely as a modem while your own router handles everything else on a separate subnet β though this still leaves double NAT in place for anything the ISP router itself intercepts.
Frequently Asked Questions
Will bridge mode turn off my ISP-provided Wi-Fi?
In most cases, yes β bridge mode typically disables the ISP device's own Wi-Fi radio along with its routing functions, since your own router's Wi-Fi is meant to take over entirely. If you still see the old network name broadcasting after enabling bridge mode, check the ISP device's settings again or contact its support.
What if my ISP's device does not offer a bridge mode option at all?
Look for an "IP Passthrough" feature instead, which achieves a similar result under a different name. If neither is available, placing your own router in the ISP device's DMZ is the next best workaround, though it is slightly less clean than a true bridge.