Am I behind CGNAT? Three ways to check (tested)
If you can't reach a server, camera or game host at home from outside, and port forwarding "does nothing", your provider may be sharing one public IPv4 address between many customers. That's carrier-grade NAT (CGNAT). This guide shows three ways to check, how to tell CGNAT apart from a second router in your own home (double NAT), and what you can do about either.
Tested on
Lab run 2026-11-16 on Linux 6.8.12 (Proxmox VE host), iproute2 6.1.0, nftables 1.0.6, traceroute 2.1.2, curl 7.88.1, Python 3.11.2. We built five small networks with Linux network namespaces: a router with a public address, a router behind CGNAT, a double NAT home, IPv6 on the CGNAT line, and a client using a VPN-style tunnel. Each case had a "what is my IP" service and an outside machine trying to connect in. All addresses in this guide are documentation examples (203.0.113.x, 198.51.100.x, 2001:db8::), not real ones.
Check 1: compare your router's address with the one websites see
This is the most reliable check, and you can do it in two minutes with no tools.
- The address websites see. Open any "what is my IP" page. Write down the IPv4 address.
- The address your router has. Open your router's admin page (often
192.168.1.1or192.168.0.1; it's printed on the router) and find the line called WAN, Internet or IP address. - Compare them:
| Your router's WAN address | Compared with what websites see | What it means |
|---|---|---|
| Starts with 100.64 to 100.127 | different | You're behind CGNAT. This range (100.64.0.0/10) is reserved for exactly that. |
| 10.x, 172.16 to 172.31, or 192.168.x | different | A second router in front of yours (double NAT), or CGNAT. See double NAT or CGNAT? |
| A normal public address | the same | Not behind CGNAT. Port forwarding can work. |
| A normal public address | different | A VPN is on, or you're on an office network. Turn the VPN off and check again. |
What we saw in the lab:
| Case | Router WAN address | Address the site saw | Verdict |
|---|---|---|---|
| Public address | 198.51.100.20 |
198.51.100.20 |
No, not behind CGNAT |
| CGNAT | 100.64.12.34 |
198.51.100.2 |
Yes, behind CGNAT |
| Double NAT (ISP modem-router in front) | 192.168.0.2 |
198.51.100.30 |
Most likely yes: CGNAT or a second router |
| Public address, but VPN on | 198.51.100.20 |
203.0.113.99 (the VPN's address) |
The two addresses differ |
We also added a second customer behind the same CGNAT box: its router had 100.64.77.88, a different address from the
first customer's 100.64.12.34, yet both showed up on the internet as 198.51.100.2. That's the "shared" in shared
address: a website can't tell you and your neighbour apart, and nobody outside can start a connection to either of you.
Check 2: traceroute
A traceroute lists every router between you and a destination. Run it from a computer at home:
- Windows:
tracert -d 1.1.1.1 - macOS / Linux:
traceroute -n 1.1.1.1
Look at the hops right after your own router (hop 1):
Public address
1 192.168.10.1 <- your router
2 203.0.113.10 <- straight onto the internet
CGNAT
1 192.168.20.1 <- your router
2 100.64.0.1 <- the provider's CGNAT box: a 100.64 hop
3 203.0.113.10
Double NAT
1 192.168.30.1 <- your router
2 192.168.0.1 <- a second router in YOUR home (the ISP's modem-router)
3 203.0.113.10
A 100.64 to 100.127 hop after your router means CGNAT. A 192.168.x or 10.x hop right after your router is usually a box in your own home, which you can often open in a browser. (On a real line you'll see more hops than in our lab; it's the first two or three that matter. Some providers hide their hops, so a traceroute with no 100.64 hop doesn't prove you're not behind CGNAT. Check 1 is the stronger test.)
Check 3: try a port forward from outside
- On a computer at home, start something that listens on a port, e.g.
python3 -m http.server 8080. - On your router, forward TCP port 8080 to that computer.
- From outside your network (a phone on mobile data with Wi-Fi off), open
http://<the address websites see>:8080.
| Case | Result in the lab |
|---|---|
| Public address | Worked: "hello from the home server" |
| CGNAT | Failed: the connection never reached the home router. Forwarding on the router changes nothing. |
| Double NAT | Failed until we also forwarded 8080 on the ISP modem-router, then worked |
CGNAT, trying the router's own 100.64.12.34 from outside |
Failed: that address can't be reached from the internet at all ("network is unreachable") |
In the lab, a failed attempt came back as "connection refused". On a real line it's more often a timeout. Either way, nothing reaches your server.
Double NAT or CGNAT?
Both show a private address on your router, and both break port forwarding. Telling them apart matters because double NAT is something you can fix yourself:
- Look for a second box: an ISP modem-router, a "gateway", or an old router in front of yours. Open its admin page and look
at its WAN address.
- Its WAN address equals the one websites see: it's double NAT. Put that box in bridge mode (or "modem only"), or forward the port on it too (that's what fixed it in our lab).
- Its WAN address is 100.64 to 100.127 or private too: that's CGNAT on top.
- In the traceroute, a 192.168.x hop right after your router is the giveaway for a second box at home.
The good news: IPv6 may already work
Many CGNAT providers also give you IPv6, and IPv6 has no CGNAT. In the lab, the same CGNAT line got an IPv6 range. With an "allow" rule on the router for port 8080, the outside machine reached the home server over IPv6 straight away, while a port we didn't allow (22) timed out.
The catch: the people connecting to you need IPv6 too. Most mobile networks have it, many home and office networks don't.
What you can do about it
Honest options, cheapest first:
| Option | Cost | Good for | Catch |
|---|---|---|---|
| Ask your provider for a public IPv4 | free to a few $/month, if they offer it | everything | many fixed-wireless, 5G home and satellite plans don't offer it |
| Use IPv6 | free | services you reach from IPv6 networks | visitors on IPv4-only networks can't reach you |
| Fix double NAT (bridge mode) | free | double NAT only | doesn't help with real CGNAT |
| Tailscale / ZeroTier | free tiers | reaching your own devices from your own devices | not for the public (strangers, game players, customers) |
| Cloudflare Tunnel | free tier | websites and web apps | web traffic mainly; games, cameras and other ports need workarounds |
| A small VPS + WireGuard | a few $/month | any port, full control | you run and secure the VPS yourself |
| A static IP delivered over a tunnel (e.g. TunnelNet) | paid | any port, a public address that stays the same, no VPS to run | a paid service |
How TunnelNet helps
TunnelNet gives a home or office server its own public IPv4 address over a tunnel, so it can be reached from anywhere even behind CGNAT, with no port forwarding on your router. See pricing. If one of the free options above covers what you need, use that.
What went wrong in our lab (so you don't repeat it)
- Two nftables mistakes in our own lab script. One-line rule sets with a closing brace straight after another were
refused (
syntax error, unexpected end of file), and so was a chain we namedfwd. Writing one statement per line and renaming the chain fixed both. This only matters if you rebuild the lab. - No WireGuard tool on the lab host. The kernel had WireGuard, but we didn't install extra packages on a hypervisor, so the "VPN" case used a plain GRE tunnel. For this test that doesn't matter: any VPN that carries your traffic shows its own exit address to websites, which is the point being tested.
- We couldn't show the CGNAT box's connection table. That kernel had no
/proc/net/nf_conntrackand theconntracktool wasn't installed, so we left that part out. - Lab vs. real life. Our "internet" was one Linux namespace, so failed connections were refused quickly. Real providers usually drop them, which shows as a timeout. Real traceroutes have more hops, and some providers hide theirs.
- Not tested here: IPv6-only mobile setups that show a
192.0.0.xaddress on the device (464XLAT), and providers that run CGNAT on ordinary-looking addresses. Check 1 still catches the second one: the router's address won't match what websites see.
How we tested
Five namespaces stood in for the routers and the internet. A tiny web service returned the caller's address ("what is my IP"),
and an outside machine at 203.0.113.50 tried to connect in. For each case we recorded the router's WAN address, what the
service saw, a traceroute, and a port-forward attempt, then ran the router's address through the same comparison rules as the table in check 1.
The lab was deleted afterwards. Every command and result above comes from that run.