Home network

Double NAT: How to Tell If You Have It and How to Fix It

What double NAT is, three quick checks to tell if you have it (WAN IP vs public IP, traceroute, NAT type test), what it breaks, and which fix fits your setup.

In this guide

Double NAT means two devices translate addresses between your equipment and the internet, usually an ISP gateway plus your own router. It breaks port forwarding, UPnP, open NAT and inbound remote access, not ordinary browsing. Check by comparing the router’s WAN IP with your public IP; fix it by bridging the gateway or running your router as an access point.

Test it now

Cloudflare edge
IP websites see216.73.216.115
LocationColumbus, United States
Internet providerAnthropic, PBC

Read at the Cloudflare edge from this request. The homepage adds your provider, network type and the VPN, DNS and WebRTC checks.

Show details

What double NAT is

Network address translation lets one public IPv4 address serve a whole network: the router hands out private addresses from the RFC 1918 ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) and rewrites outgoing packets to its own public address. Double NAT is that process happening twice in series. NETGEAR’s definition is the short version: it “occurs when you connect your router to an ISP gateway or another router.”

The common cause is equipment, not configuration. Providers supply a gateway (modem and router in one box) and people add their own router or mesh system behind it for better Wi-Fi. The gateway keeps translating for the outer network, now the WAN side of your router, and your router translates again for the inner network. A leftover router used as a Wi-Fi extender but still running as a router creates a second private network the same way.

Carrier-grade NAT counts as a layer too. When a provider shares one public address among many customers, it performs NAT on its own equipment, and RFC 6598 reserves 100.64.0.0/10, the Shared Address Space, for the link between that carrier NAT and your gateway, so your router has a private-looking WAN address even with a single router at home. The guide to what CGNAT is covers that case; it matters here because the checks below tell the two apart and the fixes differ.

How do I tell if I’m double NATted? Three checks

Each check takes about a minute, and together they tell you whether there are two NAT layers and who owns the outer one.

  1. Compare the router’s WAN IP with your public IP. Log in to your router (the guide to finding your router’s IP address covers each system) and read the WAN, Internet or Broadband IP on its status page. Then open the IP lookup, which pre-fills the public address the internet sees for you and shows its network and ISP. If the two match, the router holds the public address and there is one NAT. If the WAN address is in a RFC 1918 range, another router of yours or the provider’s gateway sits in front; if it is in 100.64.0.0–100.127.255.255, the layer in front belongs to your provider. The local IP page explains each of those ranges. Microsoft uses the same comparison in its Xbox NAT troubleshooting: record the router’s WAN address, check your public address on a website, and if they differ the ISP is supplying a private address.
  2. Count the private hops in a traceroute from your device. On Windows run tracert 1.1.1.1; on macOS or Linux run traceroute 1.1.1.1. The first hop is your router. If the second hop is also a private address, two routers are translating; if it is in 100.64.x, that is the carrier NAT. The online traceroute shows the reverse path, from CheckMyIP’s probe server to your public address, and explains how to read hops; it ends at whichever device holds your public address, so it confirms what the internet can reach but cannot look inside your network.
  3. Run the NAT type test. The NAT type test asks CheckMyIP’s own STUN server how your connection maps addresses and ports and reports whether a NAT is present, whether carrier-grade NAT was detected, and the mapping behavior consoles translate into open, moderate or strict. Two home routers in series do not show up as a distinct line, which is why check 1 comes first; the CGNAT line separates the provider’s layer from yours.

An Xbox gives you a fourth check: “Double NAT detected” under Current Network Status in Profile & system > Settings > General > Network settings, which Microsoft treats as the trigger for the fixes below.

What you seeOne router, public WAN IPTwo routers of yours (double NAT)Provider CGNAT
Router WAN IP vs public IPSame addressWAN IP in 10/8, 172.16/12 or 192.168/16WAN IP in 100.64/10, or another address that differs
tracert from a PCOne private hop, then public addressesTwo private hopsA 100.64.x hop after your router
NAT type testNAT present, CGNAT not detectedNAT present, CGNAT not detectedCGNAT detected
Xbox network settingsNo message“Double NAT detected”Strict NAT until the ISP supplies a public IP

What double NAT breaks (and what it does not)

The inner router can only open ports on the outer router’s private network, so anything that depends on an unsolicited inbound connection reaching your device fails unless both layers are configured. NETGEAR lists online games, VPN connections, and port forwarding and triggering; Google adds UPnP and notes that devices on the two private networks can struggle to reach each other. In practice:

  • Port forwarding rules on your router that “do not work” from the internet, because the gateway never passes the traffic on; the guide to what port forwarding is has a section on this failure.
  • UPnP mappings that consoles request from the inner router, which open nothing on the outer one: the usual reason for a Strict or Moderate NAT type behind two routers; the guide to changing your NAT type to open covers the other causes.
  • Remote access to a camera, NAS, VPN server or remote desktop by your public address.
  • Devices split across the two networks, such as a printer on the gateway’s Wi-Fi and a laptop on yours.

What it does not break: outbound connections. Browsing, streaming, downloads, cloud backup and most video calls initiate from your side and work through two NAT layers as they do through one; Google notes that the second translation usually adds only a very small delay. If none of the inbound cases applies to you, double NAT is a fact rather than a fault.

Fix 1: put the ISP gateway in bridge mode

Bridge mode (some providers call it modem mode or IP passthrough) turns off the gateway’s routing so that your own router receives the public address. NETGEAR and Google recommend it over the alternatives, and Microsoft lists it as the first step for an Xbox showing “Double NAT detected.” Every provider does it differently, so take the procedure from the provider’s own page; three documented examples:

  • Xfinity (US). On a device on your home network, open the Admin Tool at 10.0.0.1, log in as admin with the password printed on the gateway’s sticker (or your changed one), select Gateway > At a Glance, click Enable next to Bridge Mode, click OK on the warning, log out, then connect your router to any Ethernet port on the gateway. Xfinity says bridge mode turns off the gateway’s private Wi-Fi, network management, extenders and CyberSecure, and that only one device can connect to the gateway in that mode.
  • AT&T (US). AT&T gateways offer IP Passthrough rather than a true bridge: the gateway shares its WAN IP with a single LAN device. AT&T’s page (last updated December 7, 2022) documents it for Motorola NVG510/589 gateways at 192.168.1.254 under Firewall > IP Passthrough, with Allocation Mode set to Passthrough and Passthrough Mode set to DHCPS-fixed with your router’s MAC address, then save and restart; on 2Wire/Pace gateways the equivalent is DMZplus under Settings > Firewall > Applications, Pinholes and DMZ. AT&T warns that only one device can be in passthrough mode and that it loses the gateway’s firewall protection.
  • Virgin Media (UK). Hub 3, 4 and 5 (not the 5x) and Super Hub 1, 2 and 2AC have Modem Mode: browse to 192.168.0.1, select Next, enter the Hub settings password from the base of the Hub, select Super Hub, then Modem Mode, then Enable Modem Mode and Apply Changes. The Hub then answers at 192.168.100.1, and Intelligent WiFi, Pod compatibility and some Connect app functions stop working.

Other providers publish equivalent pages; search the provider’s support site for “bridge mode” plus the gateway model, and expect to lose the gateway’s Wi-Fi and app features, which your own router now provides. Then reboot your router so that it picks up the public address on its WAN port.

Fix 2: run your own router as an access point instead

If the gateway cannot be bridged (some provider devices do not allow it, or you need the gateway’s phone or TV services), reverse the roles: leave the gateway as the only router and make your device a pure access point. Microsoft’s wording is that changing the router to function only as an access point “will remove it as a NAT on your network.” NETGEAR’s guidance for Orbi and Nighthawk behind an unbridgeable gateway is to turn off the gateway’s Wi-Fi and put the NETGEAR router in AP mode, noting that some router features are disabled there. Google documents the same for a single Nest Wifi device in the Google Home app under Home > Wifi > Settings > Advanced Networking > Network mode > Bridge mode, with the caveats that it works only on a single device (not the primary router of a mesh), that Family Wi-Fi, priority device and guest Wi-Fi become unavailable, and that it cannot be used when the WAN IP is already public.

In access-point mode your devices receive addresses from the gateway, so port forwarding, UPnP and DMZ are configured on the gateway from then on, and you give up the routing features of your own router (parental controls, guest networks, VPN clients, router-level DNS, depending on the model). Choose this when the gateway’s features matter more than your router’s; choose Fix 1 when the opposite is true.

Fix 3: forward ports through both routers or chain the DMZ when bridging is impossible

When neither device can change roles, you can make a specific inbound path work by configuring both layers. On the gateway, forward the port to the inner router’s WAN address (the private address the gateway gave it); on the inner router, forward the same port to the device. Give the inner router a DHCP reservation on the gateway first so that the outer rule keeps pointing at it.

The broader version is to put the inner router’s WAN address in the gateway’s DMZ, which sends all unsolicited inbound traffic to the inner router, and then handle forwarding and UPnP there alone. AT&T’s Default Server mode, which forwards externally initiated TCP and UDP traffic to one LAN device that keeps its LAN address, is a vendor-built form of this; its IP Passthrough and DMZplus go further and hand that device the WAN address itself. Microsoft’s caution for consoles applies: do not combine port forwarding, UPnP and DMZ for the same device, and fix the device’s address before relying on a DMZ rule. This is a workaround for one or two services rather than a cure; a console will usually still report double NAT.

Fix 4: when the second NAT belongs to your ISP (CGNAT)

If check 1 showed a WAN address in 100.64.0.0/10, or any address that differs from your public IP while you have only one router, the outer layer is the provider’s and none of the fixes above applies. RFC 6598 describes this Shared Address Space as not globally routable and intended for the link between a carrier NAT and customer equipment, so forwarding and DMZ on your router open ports the internet cannot reach. Microsoft’s advice for Xbox here is to contact the ISP for a public IP address, without which open NAT is not possible. The other routes are IPv6, which gives each device a globally unique address with no translation if the service you need supports it, or a tunnel service that provides an inbound address. The CGNAT guide compares those workarounds.

Is it okay to have double NAT? When to leave it alone

For a household that browses, streams, works on video calls and games on services that do not require open NAT, double NAT is harmless. It is sometimes kept on purpose: a provider gateway that must stay in router mode for TV or phone service, a second router that isolates a lab or office network from the family one, or a travel router behind hotel Wi-Fi. Ask whether anything on your network needs an inbound connection from the internet and whether a console reports Strict NAT or “Double NAT detected.” If the answer to both is no, the correct action is none.

Where it is worth fixing, pick the fix by what you control: bridge the gateway if the provider allows it, otherwise run your router as an access point, and keep two-layer forwarding for the rare case where neither is possible.

Verify the fix with the same three checks

After bridging the gateway or switching your router to access-point mode, reboot everything and run the checks again from a device on your network.

  1. The router’s WAN IP (or, in access-point mode, the gateway’s WAN IP) now matches the public address shown by the IP lookup. If it still differs and is in 100.64.0.0/10, you were behind CGNAT as well, and Fix 4 applies.
  2. tracert 1.1.1.1 shows one private hop before the first public address.
  3. The NAT type test reports NAT present with CGNAT not detected, and a console that showed “Double NAT detected” no longer does; Microsoft’s instruction is to restart the Xbox and the network devices, then re-check the network settings.

If a port forward was the reason for all this, finish with the open port checker, which connects from CheckMyIP’s server to the TCP port on your public address and shows whether the rule now reaches the device.

Sources

Questions

What is meant by double NAT?

Two routers in series, each translating private addresses to the address on its WAN side. Your devices sit on the inner router’s private network, the inner router sits on the outer router’s private network, and only the outer router holds the public IP. Inbound connections have to be forwarded through both layers, which most setups never do.

What is the downside of double NAT?

Anything that needs an inbound connection fails or needs double configuration: port forwarding, UPnP, open NAT on consoles, and VPN servers, cameras and remote desktop reached from outside. NETGEAR and Google both list online gaming and port forwarding first. Outbound browsing, streaming and video calls generally work unchanged.

How do I fix double NAT on Xbox?

Microsoft’s steps are to put the ISP gateway into bridge mode (the provider or manufacturer documents how), or, if that is not possible, to run your own router as an access point only, then restart the Xbox and network hardware and confirm under Profile & system > Settings > General > Network settings that “Double NAT detected” is gone.