TunnelNet Guides

How to check if your server is reachable from the internet (and what CGNAT does to it)

2026-11-19

You set up a server, a camera or a game host at home. It works on your own network, but friends cannot connect, or an online port checker says the port is closed. Before you change settings at random, find out whether the problem is on your computer, on your router, or on your provider's side. This page gives you a short order of checks, from the quickest to the most telling. TCP only: everything here is about TCP connections, because that is what we tested.

Step 1: does it work on your own network?

From another device on the same network, open the server's local address. If that fails, the problem is the server itself or its own firewall, and nothing about your provider matters yet. Fix that first.

Step 2: compare your router's address with the one websites see

Open any "what is my IP" page and note the IPv4 address. Then open your router's admin page and find the line called WAN, Internet or IP address. Compare the two:

  • The router's address starts with 100.64 to 100.127 and differs from what websites see: you are behind CGNAT. That range is reserved for it.
  • It starts with 10., 172.16 to 172.31 or 192.168 and differs: a second router in front of yours (double NAT), or CGNAT.
  • It is a normal public address and the same as websites see: you are not behind CGNAT, and a port forward can work.

The full table, with real output from our lab networks, is in Am I behind CGNAT?

Step 3: try the port from outside

The most direct test is a connection from somewhere else, for example a friend's network or your phone on mobile data. Try to open the port. In our lab, a server behind a router with no port forwarding answered nothing from outside: the test timed out after 8 seconds. After we opened the port through a tunnel, the same test answered.

What CGNAT does to your server

With CGNAT, your provider shares one public IPv4 address between many customers. A port forward on your own router only reaches the router's side, not the internet. That is why forwarding "does nothing", and why no router setting can fix it. See why you still need IPv4 for hosting.

What you can do

  • Ask your provider for a public IPv4 address or a plan that includes one.
  • Use IPv6 if everyone who needs to reach you has it.
  • Use a tunnel that gives you a public address. TunnelNet IP is $10 a month: your machine keeps a tunnel out to us and the address is routed down it, so it works behind NAT and CGNAT with no port forwarding. Every port stays closed until you open it with sudo tnet ports allow tcp 8080, and you can close it again with sudo tnet ports deny 8080. In our lab it could take up to a minute to start answering after opening, and stopped answering 13 seconds after closing.

What we did not test

  • UDP. All our tests used TCP.
  • Real provider-grade CGNAT. Our lab built the same conditions with network namespaces and a router with no port forwarding.