Plenty of home networks run perfectly until someone adds a second router. Suddenly a game console warns about its connection type, a video call drops for no clear reason, or a security camera refuses to answer from outside the house. The equipment is fine and the internet plan has not changed, yet something in the middle is interfering. The usual culprit is double NAT, a situation where traffic passes through two routers that both try to do the same job. This guide explains how that happens, what it quietly breaks, and the straightforward ways to clear it.
What NAT is doing
Network address translation, NAT, is the trick that lets many devices in a home share one public internet address. Your phone, laptop and television each get a private address on the inside, and the router rewrites their traffic so the outside world sees a single address. Replies come back to the router, which sorts them to the right device.
This exists largely because the older IPv4 addressing system ran short of numbers, forcing homes to hide many devices behind one, a scarcity the guide on the newer IPv6 system explains. A single layer of this translation is normal and causes no trouble at all. Problems begin only when two routers perform it one after the other, each unaware of the other’s work.
How the second layer forms
Double NAT appears when a device that is already a router plugs into another router. The most common version involves the box the internet provider supplies. Many of these are combined units, a modem and a router in one case, even though people think of them only as a modem. When you add your own router behind that combo for better range or extra features, two routers now translate addresses in series.
The same thing happens when a mesh system or a travel router is connected the wrong way, or when a spare router is added to extend Wi-Fi rather than being set up as an access point. People often make the change to gain the speed the guide on a newer Wi-Fi standard offers, without realising the second router brings its own translation layer along with it.
Why games and calls suffer
Most everyday browsing survives double NAT without complaint, because the request goes out and the reply comes straight back. The trouble is with services that need the outside world to start a connection inward. Online games use this to link players directly, and console makers report it as a strict or moderate NAT type. Voice and video calls, especially peer-to-peer ones, rely on similar inbound paths.
With two routers in the way, port forwarding set on one is undone by the other, so the inbound connection never reaches the device. The result is party chat that fails, matches that will not host, cameras unreachable from a phone, and calls that connect slowly or drop. The symptoms look random, which is why double NAT is so often misdiagnosed as a faulty app or a bad line.
The mistakes that create it
A handful of familiar setups account for most double NAT, and recognising them is half the fix:
- Adding a personal router behind an ISP combo unit without changing either device’s mode.
- Plugging a second router into a LAN port and leaving it in its default router mode instead of access-point mode.
- Using a mesh node as a router when the main gateway is already routing.
- Connecting a travel or hotel router in front of your own for convenience.
- Adding a second router purely for its filtering tools, the kind the guide on network content controls describes, without disabling its routing.
In each case the cure is to make sure only one device hands out addresses and performs the translation.
Fixing it with bridge mode
The cleanest fix is to stop one of the two devices from routing. When the provider’s box is the problem, ask the provider, or use its settings, to switch it into bridge mode. Bridge mode turns the combo into a plain modem that passes the public address straight through to your own router, leaving a single translation layer behind it.
If bridge mode is not available, the alternative is to demote your own router to an access point, which turns off its address handling and lets the ISP box do the routing. A third option, useful when you cannot change the ISP box, is to place one device in the other’s DMZ, though that is a workaround rather than a tidy solution. Bridge mode stays the preferred route because it removes the extra layer completely.
Checking whether you have it
Confirming double NAT takes only a minute. Open your router’s status page and look at its internet, or WAN, address. If that address falls in a private range, starting with 10., 172.16 through 172.31, or 192.168, your router received a private address from another router rather than a public one from the internet. That private handoff is the signature of double NAT, and telling public from private addresses is a distinction the guide on assigned and reserved addresses makes clear.
A second check is to compare that WAN address with the public address a search for my IP returns. If the two differ, another device sits between your router and the internet. Some consoles and routers also report double NAT directly in a network test, which saves the manual comparison and points straight at the cause.
What this means in practice
Double NAT is not a fault so much as a side effect of stacking equipment that was each designed to be the only router in the house. Ordinary browsing hides it, which is why it tends to surface later, when someone installs a game, sets up a camera, or tries to reach home from elsewhere. Knowing the cause turns a baffling intermittent problem into a setting you can change in a few minutes.
The lasting fix is to decide which single device will route and translate, and to make every other box downstream behave as a bridge or an access point. Once one layer is doing the job, port forwarding works as intended, consoles report an open connection type, and calls stop dropping without explanation. The equipment does not change; only the arrangement does.
Frequently asked questions
What is double NAT?
Double NAT is when your traffic passes through two routers that each translate private addresses to a public one. Usually it happens because the internet provider’s box is secretly a router as well as a modem, and a second personal router sits behind it. One translation layer is normal and invisible; two layers stacked in series are what cause the trouble.
Why do my games have connection issues?
Games often need other players or servers to open a connection inward to your console, and double NAT blocks that inbound path. The console then reports a strict or moderate NAT type, and you see failed party chat, hosting problems, or slow matchmaking. Removing the second routing layer, usually with bridge mode, changes the reported type and clears most of these faults.
How do I fix double NAT?
Make only one device route. The tidiest method is to put the provider’s combo unit into bridge mode, so it acts as a plain modem and your own router does the translating. If that is not possible, set your own router to access-point mode instead. Either way you finish with a single translation layer, which restores port forwarding and inbound connections.
