You set up port forwarding on your router. The internal IP is correct, the port number matches, and the rule is enabled.

But when you try connecting from outside your network, nothing happens.

Before changing the rule again, check your router's WAN IP address. The problem might have nothing to do with your configuration.

Your Router Might Not Have a Public IP

Port forwarding works by directing incoming traffic from your router to a device inside your network.

For example, you might forward TCP port 25565 to a Minecraft server running on your computer.

That works when incoming connections can actually reach your router.

But some internet providers use Carrier-Grade NAT (CGNAT). Instead of assigning every customer a public IPv4 address, the provider shares public addresses among multiple connections.

Your router sits behind another NAT gateway controlled by the ISP.

The forwarding rule exists on your router, but incoming traffic stops upstream.

You can't fix that by changing the local rule.

Check Your WAN IP Before Doing Anything Else

This is worth checking before spending another hour on firewall settings.

First, open your router's administration page. Look under Internet, WAN, or Connection Status.

Find the WAN IPv4 address.

Now open a public IP checking website from a device connected to the same router. Make sure any VPN is disabled.

Compare the two addresses.

If your router shows something between 100.64.0.0 and 100.127.255.255, that's a strong indication of ISP-level shared addressing.

That range is reserved under RFC 6598.

You can also compare both addresses using a CGNAT checker. It helps distinguish shared address space, private upstream addressing, and a directly assigned public IPv4 address.

One important detail: different addresses don't always mean CGNAT.

If your WAN address is 192.168.x.x or 10.x.x.x, you might have a second router performing NAT. Your ISP could also be using private addressing upstream.

You'll need to identify which device owns that address.

What If the WAN IP Is Public?

If your router has a public IPv4 address matching the address seen online, the issue is probably somewhere else.

Check these things before contacting your ISP:

  1. Internal IP: Make sure the forwarding rule points to the correct device.
  2. Protocol: TCP and UDP aren't interchangeable. Check what your application requires.
  3. Local firewall: The operating system might be blocking incoming connections.
  4. Running service: An open forwarding rule doesn't help when nothing is listening on that port.

Also, test from outside your home network.

Using your phone's mobile data is a simple option. Testing your public address while connected to the same Wi-Fi can produce misleading results if your router doesn't support NAT loopback.

What Actually Works Behind CGNAT?

If you've confirmed CGNAT, changing ports usually won't solve it.

You have a few practical options.

Ask your ISP for a public IPv4 address.

Some providers offer one for free. Others charge a monthly fee. A dynamic public IPv4 address can be sufficient for many home-hosting setups.

Use a VPN or tunnel that supports inbound access.

Depending on the application, a mesh VPN or a tunnel service may provide remote connectivity without traditional port forwarding.

Consider IPv6.

If your ISP provides globally routable IPv6 connectivity, your service may be reachable without IPv4 forwarding. You'll still need suitable firewall rules and IPv6 support on both ends.

For remote cameras, NAS devices, and administration interfaces, prefer secure authenticated remote access rather than exposing management ports directly.

Don't Keep Rebuilding the Same Rule

Port forwarding problems aren't always caused by incorrect router settings.

Sometimes the configuration is fine, but the network upstream isn't allowing the connection through.

Check the WAN address first. Find out whether you're dealing with CGNAT, another router, or a local firewall problem.

Once you know where the connection stops, troubleshooting becomes much easier.