Console local IP vs public IP for port mapping

Quick answer

Setting up port forwarding for a PlayStation, Xbox, or any console means juggling two different IP addresses — and mixing them up is the most common reason forwarding fails. Here’s the distinction, made simple.

The two addresses

Your console has a local IP — a private address like 192.168.1.30 that your router assigns it inside your home network. Your whole network shares one public IP — the internet-facing address other players reach, shown on our homepage. Port forwarding connects the two: it tells the router to send traffic arriving at the public IP’s game ports to the console’s local IP.

Which one goes where

This is the key: in the router’s port-forwarding rule, the destination is the console’s local IP — never the public IP. The public IP is what the rule implicitly applies to (it’s your router’s internet side); the local IP is where you’re directing the traffic. People often wrongly enter the public IP as the target, and the forward does nothing.

Find the console’s local IP

On the console, open network settings and view the connection status — it shows the local IP (the 192.168.x.x or 10.x.x.x address). That’s the value you put in the forwarding rule’s target field.

Lock it down first

Local IPs are handed out by DHCP and can change, which would silently break your forward when the console gets a new one. Before forwarding, give the console a fixed local IP — either a DHCP reservation in the router (preferred) or a manual static IP on the console — so the address the rule targets never moves.

Then forward and test

With a fixed local IP set, create the forwarding rule pointing the game’s ports at it, then check your NAT type to confirm it improved. If you’re also sharing your public IP for others to connect to, that’s the address from our homepage — plus the port. Just remember: share the public IP, forward to the local IP.