Hi! We’ll sort out this router not getting public IP issue and get your internet and port forwarding working again. A couple of quick checks first so we aim in the right place.
When you log in to the router, what does the Internet/WAN IP address show exactly — 0.0.0.0, “disconnected”, or something like 10.x.x.x or 192.168.x.x? And if you go to a “What is my IP” website from a device that is online (or when you plug a computer directly into the modem), do you ever see a different public IP address there?
Last thing: do you have a separate modem + Wi-Fi router, or a single gateway from your ISP, and did your ISP mention anything about PPPoE, static IP, or bridge mode when the service was set up?
Customer
We switched to a new router because I want to use remote access and port forwarding. Since then the router’s WAN IP just shows 0.0.0.0 or sometimes a 10.something address. When it shows 0.0.0.0 there’s no internet at all, and when it shows 10.x.x.x the internet works but my server can’t be reached from outside. Plugging a PC straight into the modem gives internet and a proper looking public IP on “What is my IP”.
Thanks, that’s very clear and it matches two common problems:
• If the WAN IP is 0.0.0.0, the router is not getting any IP address from the ISP — DHCP or PPPoE is failing, so you get no internet.
• If the WAN IP is 10.x.x.x, 172.16-31.x, or 192.168.x.x, the router is getting only a private address. That means you’re behind another router or carrier-grade NAT (CGNAT), so you don’t really have a usable public IP for port forwarding.
We’ll tackle it in two stages: first we’ll fix the “router not getting IP address from ISP” situation so the WAN port gets a valid IP every time. Then we’ll see whether that WAN IP is truly public or private and deal with double NAT or CGNAT if needed.
Customer
Got it. When I connect my desktop directly to the modem, the connection works fine and that “What is my IP” site shows some random public IP. As soon as I put the modem into the WAN port of the router, the router WAN IP goes to 0.0.0.0 again and devices lose internet. The ISP did mention something about PPPoE on the original router but I just left this one on automatic / DHCP.
Perfect test — that proves the modem and ISP can give out a valid public IP, so the problem is how this router is talking to them.
Step A — Clean power cycle and check WAN IP
1) Turn off the router and modem (unplug power on both).
2) Make sure the Ethernet cable from the modem is plugged into the router’s WAN/Internet port, not a LAN port.
3) Plug in the modem first and let it fully sync (all “online” lights solid). Give it 2–3 minutes so the old DHCP lease is fully released.
4) Then power on the router and wait until the Power and Wi-Fi LEDs go solid.
5) From a device connected to the router, open a browser and go to the router admin page (often 192.168.0.1 or 192.168.1.1). Open the Internet/WAN status page and look at:
• Connection type (DHCP, PPPoE, Static IP, etc.)
• WAN/Internet IP address
Tell me what you see there now: still 0.0.0.0, or an IP that starts with 10/172/192, or something completely different?
Customer
After doing the modem-first reboot, the router shows “Internet: Disconnected” and the WAN IP is still 0.0.0.0. Connection type is “Automatic / DHCP”. That old router that came from the ISP definitely had PPPoE username and password set in its settings.
That explains the router not getting IP address from ISP part. On a PPPoE connection, the modem is basically just a bridge and the router must log in with those credentials; DHCP/Automatic will never receive a public IP there.
Step B — Configure PPPoE and verify you get a public IP
• In the router’s Internet/WAN settings, change the connection type from Automatic/DHCP to PPPoE (or whatever your ISP specifies).
• Enter the exact PPPoE username and password provided by your ISP. These are different from your Wi-Fi password.
• If your ISP tied the old service to a specific device, use the router’s MAC address clone feature to copy the MAC from either the old router (if you still have it) or from the PC that works directly when connected to the modem.
• Save/apply and wait 30–60 seconds, then refresh the WAN status page.
You want to see a WAN IP that is not 0.0.0.0 and not in the private ranges (10.x, 172.16-31.x, 192.168.x). That would indicate the router finally has a real public IP address. If you get a private address instead, that’s a double NAT / CGNAT situation and we’ll handle that in the next step.
Customer
After switching to PPPoE and entering the credentials, the router now shows “Connected” and the WAN IP is something like 10.120.x.x. Internet works on all devices now, but port forwarding and the remote access app still don’t work. The external IP shown by “What is my IP” is completely different from the router WAN IP.
Great — we’ve fixed the “router not getting IP at all” part. Now we’re in the second scenario:
• Your router is online but its WAN IP (10.x.x.x) is a private address.
• The website shows a different public IP that belongs to your ISP’s upstream router.
That means you’re behind double NAT or carrier-grade NAT (CGNAT). In this setup, your router never sees a real public IP, so classic port forwarding, game hosting, VPN server, or camera access from outside will not work reliably.
You have three realistic options:
1) Ask your ISP to switch your line to a public IPv4 address (sometimes called “public IP”, “static IP”, or “turn off CGNAT”).
2) If you have an ISP router in front of yours, put theirs into bridge/bridge-only mode so your own router receives the public IP directly on its WAN port.
3) If option 1 or 2 is impossible, use alternatives like reverse tunnels, cloud relay, or IPv6 where supported instead of classic port forwarding.
While we’re waiting on your ISP response, we can still tighten your current setup so that once you get a public IP, everything is ready to go.
Customer
I checked and there’s definitely an ISP router in front of mine. I just plugged my router into one of its LAN ports. The ISP box Wi-Fi is still on. I can call them about bridge mode, but is there anything I should change on my own router now so that, once they switch it, I actually get the public WAN IP and don’t end up back at 0.0.0.0?
Good catch — that explains the private WAN IP. Your router is currently sitting behind the ISP router, so it can only receive a private address from their DHCP server.
Here’s how to prepare your router so it cleanly picks up the public IP once the ISP device is bridged:
• Confirm with support whether the bridged connection will be DHCP, PPPoE, or static IP. You’re already set to PPPoE, which is good if that’s what they will keep using once bridge mode is enabled.
• Ask them to clear or release any old DHCP/PPPoE sessions bound to your previous hardware, and mention that your new router is not getting a public IP on WAN.
• When they turn on bridge mode, do a clean restart in this order: power off both devices, power on the modem/ISP box, wait until it’s fully online, then power on your router and refresh the WAN status.
• If they assign you a static public IP, enter the IP, subnet mask, gateway, and DNS exactly as they provide in the WAN/Internet section instead of automatic DHCP.
After that, your router should finally show a WAN IP that is outside private ranges. At that point, we can verify that port forwarding, DDNS, and remote access are working correctly.
Customer
I called them and had the ISP router switched to full bridge mode. After another round of reboots, my own router now shows a WAN IP that’s not in 10 or 192.168 and it matches what “What is my IP” shows. Port forwarding and my remote access app both work now. Anything else I should tweak so the router doesn’t lose the public IP again?
Nice — that means your router is now getting a real public IP and the double-NAT problem is gone.
To keep it stable and avoid going back to 0.0.0.0 on WAN or random loss of the public IP:
• Turn on automatic firmware updates on the router if available, or check manually every month or two. Some older firmware versions had bugs where the router dropped the WAN lease and fell back to 0.0.0.0.
• Note down your PPPoE or static IP details, the router admin address, and your ISP account info. Keep them in a safe place so you can quickly reconfigure after a reset.
• Avoid plugging other routers in front of this one unless you know how to configure bridge mode — that’s how people accidentally end up back with private WAN IPs and broken port forwarding.
• In the router’s logs, glance at any repeated “DHCP failed” or “PPPoE authentication failed” messages. If you see those often, it’s worth reporting to your ISP so they can check things on their side.
With that in place, your router should keep its public IP without you needing to constantly reboot hardware.
Customer
Makes sense. Everything is stable so far and the remote access is working from my phone over mobile data. I’ve written down the PPPoE details and router login info like you suggested. Anything else I should know about public vs private IPs before I forget all this?
Sure, here’s the short version you can screenshot:
• A
public IP is routable from the internet and is what you need for classic
port forwarding, VPN server, remote desktop, cameras, etc.
• A
private IP (10.x, 172.16-31.x, 192.168.x) is used only inside networks. If your
router WAN IP is private, you’re behind another router or CGNAT and inbound connections won’t work unless the device in front also forwards or your ISP gives you a public IP.
•
Router WAN IP 0.0.0.0 means it didn’t get any IP from the ISP — usually fixed by the right WAN type (DHCP vs PPPoE vs static), a proper power cycle, or clearing an old DHCP/PPPoE session at the ISP side.
If you ever see your
router not getting public IP again — WAN shows 0.0.0.0, a private address, or your ports suddenly stop working — you can
open a chat with an expert and we’ll walk through the modem, router, and ISP settings with you step by step.
Customer
That explanation really helps. I finally understand why the router wasn’t getting a public IP and why port forwarding was failing. Everything’s good now — thanks a lot for the detailed walkthrough!
You’re very welcome! If friends or coworkers say their
router isn’t getting a public IP or their
WAN IP is 0.0.0.0 / private, you can share this checklist. And if you’d rather have someone in the router interface with you, just
start a chat with an expert and we’ll take it from there in real time.
Why routers stop getting a public IP (modem, WAN IP, DHCP, CGNAT)
Most home router not getting public IP problems are caused by configuration between the modem and router, not by your laptop or phone. If the ISP uses PPPoE or a static IP and the router is left on automatic DHCP, the WAN interface will stay at 0.0.0.0 or “disconnected”. In other cases, the router gets only a private WAN IP because it’s plugged into another router or your provider uses carrier-grade NAT (CGNAT), which breaks regular port forwarding and remote access.
Breaking the path into device → router → modem → ISP makes it easier to see what’s wrong. If a computer works when wired directly to the modem with a public IP, but the router WAN IP is 0.0.0.0 or private, the problem is how the router is obtaining the address from the ISP — its WAN type, PPPoE login, MAC address binding, or the upstream device not being in bridge mode.
How to tell if the problem is router, modem, or ISP address assignment
To quickly narrow down a router not getting public IP issue, start with these tests:
First, connect a computer directly to the modem with an Ethernet cable. If you can browse the web and a “What is my IP” site shows a normal public IP, your ISP line and modem are working. Next, reconnect the router, log into its admin page, and look at the Internet/WAN status. If it shows 0.0.0.0 with DHCP or PPPoE, the router is failing to obtain any IP from the ISP. If it shows a private WAN IP like 10.x or 192.168.x.x, your router is behind another router and you’re dealing with double NAT or CGNAT rather than a total outage.
Router not getting public IP — quick troubleshooting tips
Confirm the modem and ISP first, then fix the router’s WAN type and public vs private IP.
Fast path: test the modem directly → connect modem to the router’s Internet/WAN port → reboot modem first, then router → set the correct WAN type (DHCP, PPPoE, static IP) as required by your ISP → verify the router gets a real public IP address and not 0.0.0.0 or a private 10/172/192 address → avoid double NAT by putting any ISP router into bridge mode. Once that’s done, classic port forwarding and remote access will work the way they should.
Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your router model and ISP, please consult a verified expert on Whizz-Tech before making decisions.
Why is my router not getting a public IP from my ISP?
Usually either the WAN type is wrong (for example set to DHCP when your ISP requires PPPoE or static IP) or the router is plugged into another router or gateway instead of a bridged modem. In the first case, the WAN IP might stay at 0.0.0.0 or “disconnected”. In the second case, your router receives only a private WAN address such as 10.x or 192.168.x.x, which means it is behind double NAT or CGNAT and does not see a true public IP.
How do I fix “router WAN IP 0.0.0.0” or “no IP address from ISP”?
Power cycle the modem and router in order, make sure the modem is connected to the router’s Internet/WAN port, and set the correct Internet/WAN connection type in your router (DHCP, PPPoE, or static IP) as specified by your ISP. If it still shows 0.0.0.0, ask your ISP to clear any old DHCP/PPPoE sessions bound to old hardware and confirm whether you need to clone a MAC address or enter static IP details.
What’s the difference between public IP and private IP on my router WAN?
A public IP address is reachable from the internet and is required for classic port forwarding and hosting services. A private IP (10.x, 172.16-31.x, 192.168.x.x) is used only inside networks. If your router WAN IP is private, then your ISP router or CGNAT is in front of you, and inbound connections from the internet will not reach your router unless the upstream device also forwards ports or your ISP gives you a public IP.
When should I reset my router to factory settings?
If you’ve confirmed the modem works, used the correct WAN type, and tried normal reboots but the router still won’t get a public IP, a factory reset can clear bad configuration or leftover settings from another ISP. Just make sure you have your PPPoE or static IP details, Wi-Fi name and password, and admin login ready before resetting so you can re-enter them afterward.