PortForward: Difference between revisions
PerikiyoXD (talk | contribs) No edit summary |
PerikiyoXD (talk | contribs) No edit summary |
||
| Line 14: | Line 14: | ||
This is required when hosting a server from a home network. | This is required when hosting a server from a home network. | ||
== Why Is It Required? == | == Why Is It Required? == | ||
| Line 26: | Line 24: | ||
Without port forwarding, your server will only be accessible from inside your local network. | Without port forwarding, your server will only be accessible from inside your local network. | ||
== Before You Begin == | == Before You Begin == | ||
| Line 39: | Line 35: | ||
Default server ports: | Default server ports: | ||
* | * '''22000 UDP''' | ||
* | * '''22000 TCP''' | ||
* | * '''HTTP port (if applicable)''' | ||
Ports can be changed in your [[ServerConfiguration|server configuration]]. | |||
== How to Open Ports == | == How to Open Ports == | ||
| Line 53: | Line 47: | ||
General steps: | General steps: | ||
# Log into your router’s admin interface (usually 192.168.0.1 or 192.168.1.1). | |||
# Locate the section labeled: | |||
#* Port Forwarding | |||
#* Virtual Server | |||
#* NAT Rules | |||
#* Applications & Gaming | |||
# Create a new rule: | |||
#* External Port: 22000 | |||
#* Internal IP: (your server PC’s local IP) | |||
#* Internal Port: 22000 | |||
#* Protocol: TCP + UDP | |||
# Save changes. | |||
# Restart the router if required. | |||
Because every router interface is different, consult: | Because every router interface is different, consult: | ||
[https://portforward.com/router.htm | [https://portforward.com/router.htm portforward.com router guide] | ||
Select your router model for step-by-step instructions. | Select your router model for step-by-step instructions. | ||
== Verifying Port Forwarding == | == Verifying Port Forwarding == | ||
| Line 84: | Line 74: | ||
* Ask someone outside your network to attempt connection. | * Ask someone outside your network to attempt connection. | ||
You can check whether your port is open using: | |||
[https://www.yougetsignal.com/tools/open-ports/ YouGetSignal Open Port Checker] | |||
Enter your public IP address and the port number (e.g., 22000) to test accessibility. | |||
Important: Port checks will fail if the server is not running. | |||
== Troubleshooting == | == Troubleshooting == | ||
=== No Router Access === | === No Router Access === | ||
If you do not control the router (e.g., apartment, campus, shared housing), you cannot configure port forwarding yourself. | If you do not control the router (e.g., apartment, campus, shared housing), you cannot configure port forwarding yourself. | ||
=== Router Restart Required === | === Router Restart Required === | ||
Some routers require: | Some routers require: | ||
| Line 102: | Line 97: | ||
=== ISP Port Blocking === | === ISP Port Blocking === | ||
Some Internet Service Providers block: | Some Internet Service Providers block: | ||
| Line 113: | Line 109: | ||
* Use a VPS or dedicated hosting provider | * Use a VPS or dedicated hosting provider | ||
=== Carrier-Grade NAT (CGNAT) === | |||
If your ISP uses [https://en.wikipedia.org/wiki/Carrier-grade_NAT carrier-grade NAT (CGNAT)]: | |||
* You do not have a public IPv4 address. | * You do not have a public IPv4 address. | ||
| Line 128: | Line 123: | ||
* Use a VPN that provides port forwarding | * Use a VPN that provides port forwarding | ||
=== Firewall Conflicts === | |||
Ensure: | Ensure: | ||
| Line 136: | Line 130: | ||
* Security software is not blocking the ports. | * Security software is not blocking the ports. | ||
* The internal IP in the router rule matches your server machine. | * The internal IP in the router rule matches your server machine. | ||
== Alternatives to Port Forwarding == | == Alternatives to Port Forwarding == | ||
| Line 149: | Line 141: | ||
These options typically involve cost but avoid router configuration. | These options typically involve cost but avoid router configuration. | ||
== Summary == | == Summary == | ||
Latest revision as of 11:37, 23 February 2026
Port Forwarding
What Is Port Forwarding?
Port forwarding is a router configuration that allows external devices on the internet to connect to a specific device inside your local network.
By default, home routers block unsolicited incoming traffic for security reasons. Port forwarding creates a rule that:
- Listens on a specific external port
- Accepts incoming traffic on that port
- Forwards the traffic to a designated internal IP address and port
This is required when hosting a server from a home network.
Why Is It Required?
If you are running a server from a PC on your home network:
- Your router blocks incoming connections by default.
- External players cannot reach your server.
- Server listing services cannot communicate with your server.
Without port forwarding, your server will only be accessible from inside your local network.
Before You Begin
Ensure the following:
- You have access to your router’s admin panel.
- Your server PC has a static local IP address (or a DHCP reservation).
- You know the ports your server uses.
Default server ports:
- 22000 UDP
- 22000 TCP
- HTTP port (if applicable)
Ports can be changed in your server configuration.
How to Open Ports
Port forwarding is configured in your router settings.
General steps:
- Log into your router’s admin interface (usually 192.168.0.1 or 192.168.1.1).
- Locate the section labeled:
- Port Forwarding
- Virtual Server
- NAT Rules
- Applications & Gaming
- Create a new rule:
- External Port: 22000
- Internal IP: (your server PC’s local IP)
- Internal Port: 22000
- Protocol: TCP + UDP
- Save changes.
- Restart the router if required.
Because every router interface is different, consult: portforward.com router guide
Select your router model for step-by-step instructions.
Verifying Port Forwarding
After configuring:
- Ensure the server is running.
- Use an external port checking tool.
- Ask someone outside your network to attempt connection.
You can check whether your port is open using: YouGetSignal Open Port Checker
Enter your public IP address and the port number (e.g., 22000) to test accessibility.
Important: Port checks will fail if the server is not running.
Troubleshooting
No Router Access
If you do not control the router (e.g., apartment, campus, shared housing), you cannot configure port forwarding yourself.
Router Restart Required
Some routers require:
- A reboot
- A full power cycle
Changes may take seconds to several minutes to apply.
ISP Port Blocking
Some Internet Service Providers block:
- Specific ports
- All inbound ports
Possible solutions:
- Contact your ISP
- Use a VPN with port forwarding support
- Use a VPS or dedicated hosting provider
Carrier-Grade NAT (CGNAT)
If your ISP uses carrier-grade NAT (CGNAT):
- You do not have a public IPv4 address.
- Port forwarding will not work.
Solutions:
- Request a public IP from your ISP
- Use IPv6 (if supported)
- Use a VPS or external hosting
- Use a VPN that provides port forwarding
Firewall Conflicts
Ensure:
- Your operating system firewall allows the server.
- Security software is not blocking the ports.
- The internal IP in the router rule matches your server machine.
Alternatives to Port Forwarding
If port forwarding is not possible:
- Rent a VPS
- Use dedicated game server hosting
- Use a VPN with port forwarding
- Use a reverse proxy or tunneling solution
These options typically involve cost but avoid router configuration.
Summary
Port forwarding allows external players to connect to a server hosted on your home network. It requires:
- Router access
- Correct port configuration
- A public IP address
- Proper firewall rules
Without it, your server will not be reachable from the internet.