Engineering notes
How to get a static IP on Starlink, 4G or 5G: CGNAT explained
Why port forwarding does nothing on Starlink and mobile broadband, how to check whether you are behind CGNAT, and the real ways to get a public or static IP address, with what each one can and cannot do.
You set up port forwarding on your router, checked it twice, and nothing outside your house can connect. On Starlink, 4G and 5G broadband, and a growing number of fibre lines, the reason is usually the same: your router does not have a public address to forward from. This article explains why, how to check, and what your options are.
Why port forwarding does nothing
There are not enough IPv4 addresses for every connection to have its own. Many providers deal with that using carrier-grade NAT, or CGNAT: one public IPv4 address is shared between many customers, and each customer's router is given a private address from a range set aside for the purpose.
Your router can still start connections out to the internet, which is why browsing works. Nothing can start a connection in, because the public address belongs to your provider's equipment, not to your router. A port forward on your own router only covers the last step of a journey that never reaches it.
How to check whether you are behind CGNAT
Compare two addresses:
- The address the internet sees. Any "what is my IP" page shows it, and so does the check button on our static IP page.
- The internet (WAN) address on your router's status page.
If they are different, something between your router and the internet is translating your address, and you are behind CGNAT. A WAN address between 100.64.0.0 and 100.127.255.255 settles it: that range is reserved for carrier-grade NAT by RFC 6598.
If the two addresses match, you have a public address. It may still change from time to time, which is a different and smaller problem: dynamic DNS deals with that.
Starlink, as an example
Starlink's own support pages, as we read them on 15 November 2026, describe two IPv4 policies. The default is CGNAT, which does not allow inbound connections. Some service plans can switch to a public IPv4 address from the account dashboard. Starlink says it does not provide static addresses, so even the public one can change. It also delegates an IPv6 prefix, and notes that its own Wi-Fi router does not do port forwarding, so using either means bringing your own router.
Plans and policies change. Check the provider's current pages before you rely on any of this, for Starlink or anyone else.
The options, and what each one is good for
Ask your provider for a public address
The simplest fix when it exists. Some providers sell a public or static IPv4 address as an add-on, or include one on business plans. Ask what you get: "public" and "static" are not the same thing, and a public address that changes still needs dynamic DNS. Many mobile broadband providers offer neither.
Use IPv6
If your provider gives you IPv6, your devices may already have addresses that are reachable from outside, with the right firewall rule on your router. The limit is the other end: the person or service connecting to you needs IPv6 as well, and plenty of networks still lack it. It is a good answer for reaching your own things from your own phone, and a poor one for a service that anyone should be able to use.
A tunnel service for websites
Several services will publish a web application from behind CGNAT: a small program on your machine connects out to them, and they pass web requests back down that connection. This works well for HTTP and HTTPS. It is not a public address: other protocols are limited or unsupported, and your traffic is handled by their proxy.
A private mesh network
Tools built on WireGuard can join your own devices into a private network that works through CGNAT. This is the right tool when everyone who needs access is you, or people you can ask to install something. It does not make a service reachable by the public.
Rent a small server and forward through it
A virtual server with a public IPv4 address can act as your front door. You run a WireGuard tunnel from home to the server, and the server forwards chosen ports down the tunnel. It works for any protocol and you control all of it. You also maintain all of it: a server to keep patched, forwarding rules to write, and the services at home see the server's address unless you do more work to preserve the real one.
A static public address routed over a tunnel
The last option moves the address itself. A provider with its own network routes a public IPv4 address down a WireGuard tunnel to your router, so the router holds a real public address: every port and every protocol, with nothing to forward and no proxy in between. Because the tunnel is opened from your side, CGNAT does not block it, and because the address belongs to the provider's network and not to your line, it stays the same when you change ISP or move house.
This is the one we are thinking of building at Vozora, and it does not exist yet. We run our own network and already deliver addresses to our own staging servers this way; what we do not know is whether enough people want it. If you would use it, the static IP waiting list is how to tell us. Joining is not an order.
Which one to pick
| You want to | Start with |
|---|---|
| Reach your own devices from your own laptop or phone | A private mesh network, or IPv6 |
| Publish a website or web application | A tunnel service for websites |
| Run something that is not a website, for other people to reach | A public address from your provider, or a rented server and a tunnel |
| Keep one address through changes of provider or house | An address routed over a tunnel |
Whichever you choose, start by checking which address your router really has. It takes two minutes and tells you whether you have a CGNAT problem at all.