Port Forwarding Guide

What Is Port Forwarding and When Do You Need It?

Your router uses NAT to share one public IP address across all your devices. By default, incoming connections are blocked because the router doesn't know which device they're meant for. Port forwarding creates a permanent rule: "any incoming traffic on port X goes to device Y."

You need port forwarding when:

• Hosting a game server (Minecraft, Valheim, CS2)
• Running a home web or file server
• Accessing home cameras or NAS remotely
• Fixing Strict NAT on gaming consoles (as a fallback when UPnP doesn't work)
• Self-hosted VPN or remote desktop

Before You Start: Check for CGNAT

Port forwarding doesn't work if your ISP uses CGNAT. Compare your router's WAN IP to your public IP (whatismyip.com). If they differ, you're behind CGNAT — read the CGNAT guide first.

Step 1: Assign a Static Local IP to Your Device

Port forwarding rules target a local IP address. If your device's IP changes (dynamic DHCP), the rule breaks. Set a DHCP reservation in your router admin panel: find the device in the DHCP client list and assign it a fixed IP like 192.168.1.100. This is different from a static IP configured on the device itself — DHCP reservation is easier and less error-prone.

Step 2: Log Into Your Router Admin Panel

Type your router's gateway address into a browser — usually 192.168.1.1 or 192.168.0.1. Find it via: Windows Command Prompt → ipconfig → Default Gateway. Log in with your admin credentials (often on a sticker on the router).

Step 3: Find the Port Forwarding Section

Location varies by router brand:

• Asus: WAN → Virtual Server / Port Forwarding
• Netgear: Dynamic DNS → Port Forwarding / Port Triggering
• TP-Link: Advanced → NAT Forwarding → Virtual Servers
• Linksys: Security → Apps and Gaming → Single Port Forwarding
• Eero: eero app → your network → Advanced → Port Forwarding

Step 4: Create the Rule

A port forwarding rule has four fields:

• External port: the port incoming traffic arrives on
• Internal IP: the local IP of your device (e.g., 192.168.1.100)
• Internal port: usually the same as external port
• Protocol: TCP, UDP, or Both (check the application's documentation)

Common Port Numbers

Step 5: Test the Rule

Use canyouseeme.org to test if a port is open — enter the port number and it will tell you if it's reachable from outside your network. If the port shows closed despite your rule, check: firewall on the target device, CGNAT blocking, or the rule targeting the wrong local IP.

Frequently Asked Questions

What is port forwarding and do I need it for gaming?

Port forwarding creates a rule sending incoming traffic on specific ports to a specific device. Most gaming doesn't require it — UPnP handles it automatically. You need manual port forwarding if UPnP doesn't resolve your NAT type, or if you're hosting a game server.

Is port forwarding safe?

Port forwarding exposes a specific device to the internet on a specific port. The security risk depends on what's running on that port. A properly secured game server or Plex instance carries minimal risk. Forwarding port 3389 (Remote Desktop) to a Windows PC without strong authentication is higher risk.

Why is my port forwarding not working?

The most common causes: CGNAT (your ISP's NAT blocking the rule before it reaches your router), the device's local IP changed, firewall on the device blocking the port, or the router rule targeting the wrong IP or protocol.

Does port forwarding affect internet speed?

No — port forwarding only affects routing of incoming connections. It has no impact on download or upload speed.

What is UPnP and should I use it instead of port forwarding?

UPnP (Universal Plug and Play) lets devices automatically request port forwarding rules from your router. Most gaming consoles and applications use UPnP to achieve Open NAT without manual configuration. Enable UPnP in your router settings before trying manual port forwarding.