TL;DR: If port forwards never work even though your lookup shows a “public” IPv4, you may be behind carrier-grade NAT. Confirm the address from a public IP check, compare it to the WAN IP on the router, and plan tunnels or ISP options instead of endless router reboots.
The symptom that feels like a broken router
You open port 25565 for a game, 51820 for WireGuard, or 443 for a lab server. Firewall rules look perfect. Friends still cannot connect. Hairpin tests from inside the LAN sometimes succeed while the outside world fails. That pattern often means your home router’s WAN address is itself private—nested behind the ISP’s CGNAT.
The two-IP test
Read the WAN/Internet IPv4 on the router status page. Then check what the outside world sees in the browser. Interpret the pair:
- They match and are public: classic public IPv4; port forwarding can work if the ISP allows it.
- Router shows 100.64.0.0/10, 10/8, or 172.16/12: strong CGNAT clue; the lookup’s public IP belongs to the carrier pool.
- They differ, both look public: possible double NAT via an upstream ISP modem in router mode—also blocks naive forwards.
- Only IPv6 matches publicly: inbound IPv4 may be hopeless while IPv6 still works if you publish AAAA records.
What the shared public IP implies
Many customers share one external address. You cannot uniquely forward a port on that address without ISP cooperation. Abuse complaints against the shared IP can also affect neighbors on the same pool—another reason ISPs limit inbound.
Fixes that work with CGNAT—and ones that do not
Rebooting for a new DHCP lease rarely grants a real public IPv4 on CGNAT plans. UPnP cannot punch through the carrier layer. Paying for a static public IPv4, switching plans, or using an IPv6-first design are honest paths. Overlays such as Tailscale, ZeroTier, Cloudflare Tunnel, or a small VPS reverse proxy accept outbound-only links and broker access without inbound ports on your home IP.
Do not publish the shared CGNAT exterior IP in DNS expecting a unique host. You will collide with other customers’ expectations and still not terminate traffic on your LAN.
Gaming, cameras, and remote desktop
Console multiplayer often uses relay servers and survives CGNAT. Self-hosted game servers and self-hosted VPN concentrators do not. Security cameras that “require port 80 open” need a vendor cloud relay or a tunnel when CGNAT is present. Remote Desktop to a home PC likewise needs an outbound-friendly broker or a machine that has real public addressing.
Talking to the ISP with evidence
Support scripts sometimes deny CGNAT until you provide screenshots: router WAN IP in a private range plus browser public IP. Ask explicitly for a public IPv4 add-on. If they only offer IPv6, confirm your devices and apps can use it before you cancel copper fantasies.
- Capture both IPs in one sitting.
- Note whether the modem is bridge or router mode.
- Ask about 100.64.0.0/10 specifically if the agent seems unsure.
Keep expectations aligned with the network you have
IPv6 as a way forward—and its own footguns
If your ISP grants a real IPv6 prefix, inbound services on v6 can succeed while v4 stays behind CGNAT. That only helps clients that speak IPv6. Publish AAAA records carefully, open the correct v6 firewall rules, and remember that some mobile networks still prefer v4 paths to certain CDNs.
Home routers in IPv6 firewall default-deny mode will drop inbound even when addressing is fine. Test with a known-good v6 echo service and with a friend on a dual-stack connection. Do not declare victory after a local loopback test.
Dynamic DNS vendors may update only your CGNAT exterior IPv4, which remains useless for inbound. Point updates at the IPv6 address or at a tunnel endpoint you control instead. Read the updater’s IP detection method—it might query a public lookup page and still pick the unusable v4.
Write the architecture decision down: home inbound via tunnel; raw ports not expected. Future hardware upgrades will not reopen a problem you already solved with overlays.
Neighborhood Wi-Fi and apartment ISP gateways add another NAT layer on top of CGNAT. Even a “public” looking WAN IP on your personal router may sit behind the building’s router. Walk the two-IP test at each layer you control, and ask the building manager whether residents receive public IPv4. Hardware upgrades inside your apartment cannot bypass a shared upstream NAT you do not administer.
Outbound browsing, streaming, and “what is my IP” checks work fine under CGNAT. Inbound services are a different product. Diagnose with the two-IP test on www.whatismyipaddressinquire.com plus your router status page. Once you see the carrier pool, stop buying new routers to solve an ISP addressing design.


