
Bridge mode turns a Netgear router into a pass-through device. It stops routing, DHCP, NAT, and usually Wi-Fi so another router or mesh system can manage the home network.
Does this affect you?
Use this for standalone Netgear routers such as Nighthawk models when adding them behind another router, gateway, or mesh system and avoiding double NAT.
Turn on bridge mode
Configure it while directly connected to the Netgear router.
- Connect to the Netgear Wi-Fi or plug into it by Ethernet.
- Open routerlogin.net or 192.168.1.1.
- Log in with the admin username and password. Defaults are often admin/password if unchanged.
- Go to Advanced > Advanced Setup > Router/AP/Bridge Mode or the closest matching menu.
- Choose Bridge Mode, not Wireless Bridge or WDS, which is a different wireless repeating feature.
- Click Apply and wait for restart.
- Connect the downstream router or mesh system to a Netgear LAN port, not the WAN/Internet port, unless your model instructions say otherwise.
Get back into a bridged router
The old default address often changes in bridge mode.
- Open the main router or mesh app connected-device list.
- Look for the Netgear model name or Nighthawk device.
- Use its assigned local IP address in a browser.
- If you cannot find it, factory reset returns the router to defaults but erases all custom settings.
More control
Use access point mode if you still want Wi-Fi
Bridge mode usually disables the Netgear Wi-Fi. If you want the router to extend coverage with its radios, Access Point Mode is usually the better choice.
Something else must handle routing
Do not bridge a router unless another router, modem/gateway, or mesh system will provide DHCP, NAT, Wi-Fi, and firewall duties.
You can switch back
Log in through the new assigned IP, return to the same setting, and choose Router Mode. The router restarts and resumes normal routing.
Sources
- Netgear Support – Set up your router in bridge mode (2025)
- Netgear Support – Default login and IP address for Netgear routers (2025)
- FCC Consumer Guide – Wireless Network Troubleshooting (2024)
