rudedog
02-25-2005, 09:48 PM
A list of ports required open to setup a server behind a router or firewall
DogMeat's Port List Guide
QuickList:
1) Collect IP Information
2) Configure Port Blocking/Forwarding on your Firewall
Overview:
Firewalls and Routers are restrictive by design, and have to be setup to allow the MoHAA/GameSpy traffic to reach your server. In some cases this is done by allowing traffic thru a Port Blocking filter and/or directing it to a specific IP Address using Port Forwarding.
Instructions:
Unfortunately I cannot give specific instructions that would cover every program out there, but I can give some general info to get you going. The most common situations seem to be broadband internet routers and personal firewalls such as Black Ice Defender or Norton. Both of these use port blocking, and personal firewalls can often be changed on the fly to a "low" setting. You'll most likely be using a web based interface for a router, and will have to enter in the actual port numbers to unblock. Less commonly seen is Port Forwarding, which is usually found in the more intelligent routers and dedicated firewall machines, like a Linux box. Oftentimes the game server will be on a network segement that has special security to protect the rest of your network while making it easy for Internet users to access the server. This is known as the DMZ or De-Militarized Zone, since it represents a border or buffer zone between your protected machines and the wilds of the 'net.
I have collected the information on the following table from various websites and documents on MoHAA and GameSpy. A server must use at minimum the ports in bold, the rest are for GameSpy/ASE; and I have used 192.168.0.2 as an example of the Game Server's IP Address. Port Forwarding Table
MoHAA - Default Server Game Port UDP 12203 192.168.0.2 12203
MoHAA - GameSpy Monitoring Port UDP 12300 192.168.0.2 12300
GameSpy - Query Port UDP 6500 192.168.0.2 6500
GameSpy - Dplay UDP UDP 6515 192.168.0.2 6515
GameSpy - Custom UDP Pings UDP 13139 192.168.0.2 13139
GameSpy - Master Server UDP Heartbeat UDP 27900 192.168.0.2 27900
GameSpy - Master Server List Request TCP 28900 192.168.0.2 28900
GameSpy - GP Connection Manager TCP 29900 192.168.0.2 29900
GameSpy - GP Search Manager TCP 29901 192.168.0.2 29901
MoHAA - Demo Monitoring Port (Legacy) UDP 12201 192.168.0.2 12201
MoHAA - Alt Game Port (Optional w/ net_port) UDP 12202 192.168.0.2 12202
MoHAA - Alt Game Port (Optional w/ net_port) UDP 12210 192.168.0.2 12210
GameSpy - Voice Chat Port (Optional) UDP 3783 192.168.0.2 3783
GameSpy - IRC Chat (Optional) UDP 6667 192.168.0.2 6667
This guide may be used on any website as long as my name and website remain on it.
DogMeat
tfo.servebeer.com (http://tfo.servebeer.com/)
DogMeat's Port List Guide
QuickList:
1) Collect IP Information
2) Configure Port Blocking/Forwarding on your Firewall
Overview:
Firewalls and Routers are restrictive by design, and have to be setup to allow the MoHAA/GameSpy traffic to reach your server. In some cases this is done by allowing traffic thru a Port Blocking filter and/or directing it to a specific IP Address using Port Forwarding.
Instructions:
Unfortunately I cannot give specific instructions that would cover every program out there, but I can give some general info to get you going. The most common situations seem to be broadband internet routers and personal firewalls such as Black Ice Defender or Norton. Both of these use port blocking, and personal firewalls can often be changed on the fly to a "low" setting. You'll most likely be using a web based interface for a router, and will have to enter in the actual port numbers to unblock. Less commonly seen is Port Forwarding, which is usually found in the more intelligent routers and dedicated firewall machines, like a Linux box. Oftentimes the game server will be on a network segement that has special security to protect the rest of your network while making it easy for Internet users to access the server. This is known as the DMZ or De-Militarized Zone, since it represents a border or buffer zone between your protected machines and the wilds of the 'net.
I have collected the information on the following table from various websites and documents on MoHAA and GameSpy. A server must use at minimum the ports in bold, the rest are for GameSpy/ASE; and I have used 192.168.0.2 as an example of the Game Server's IP Address. Port Forwarding Table
MoHAA - Default Server Game Port UDP 12203 192.168.0.2 12203
MoHAA - GameSpy Monitoring Port UDP 12300 192.168.0.2 12300
GameSpy - Query Port UDP 6500 192.168.0.2 6500
GameSpy - Dplay UDP UDP 6515 192.168.0.2 6515
GameSpy - Custom UDP Pings UDP 13139 192.168.0.2 13139
GameSpy - Master Server UDP Heartbeat UDP 27900 192.168.0.2 27900
GameSpy - Master Server List Request TCP 28900 192.168.0.2 28900
GameSpy - GP Connection Manager TCP 29900 192.168.0.2 29900
GameSpy - GP Search Manager TCP 29901 192.168.0.2 29901
MoHAA - Demo Monitoring Port (Legacy) UDP 12201 192.168.0.2 12201
MoHAA - Alt Game Port (Optional w/ net_port) UDP 12202 192.168.0.2 12202
MoHAA - Alt Game Port (Optional w/ net_port) UDP 12210 192.168.0.2 12210
GameSpy - Voice Chat Port (Optional) UDP 3783 192.168.0.2 3783
GameSpy - IRC Chat (Optional) UDP 6667 192.168.0.2 6667
This guide may be used on any website as long as my name and website remain on it.
DogMeat
tfo.servebeer.com (http://tfo.servebeer.com/)