Here is a full listing of the ports you will need to forward on your router and allow through the Windows Firewall.
NOTE: You may only need to forward the incoming ports as your NAT router will usually allow all outgoing traffic by default. Windows Firewall currently does not block outgoing data, only incoming data, so unless you are running a third party firewall you shouldn't need to unblock outgoing ports.
General Listings of the ports
Port 113 (TCP/incoming) - not essential
Port 6970 (UDP/outgoing)
Port 6971 (UDP/incoming)
Port 6667 (TCP/outgoing)
Port 30196 (TCP/incoming)
Port 30196 (TCP/outgoing)
Port 30197 (TCP/outgoing)
Port 30198 (TCP/incoming)
Port 30198 (TCP/outgoing)
Port 30199 (UDP/outgoing)
Ports 32766-32786 (UDP/incoming)
iGOR uses several ports for internet communications. Some of these can be changed, others cannot.
IRC Chat
Port 6667 (TCP/outgoing) - cannot be changed.
IRC Ident Server
Port 113 (TCP/incoming) - cannot be changed. (It is not essential that this port is opened, but chat connections will be much quicker if you can open this port for incoming connections / add it to your port forwarding list.
Race List
Port 30197 (TCP/outgoing)- cannot be changed.
Remote Hosting Client
Port 30196 (TCP/outgoing)
By default, GPL uses the following ports:
Broadcasting
Port 6970 (UDP/outgoing) - used by GPL to broadcast the status of the races to the RaceList server.
HOWEVER, iGOR changes this port to 30199 (UDP/outgoing) to keep the range of ports required by iGOR to a single block (30196-30199).
Pings
Port 6971 (UDP/incoming) - used by GPL for ping responses. Not used by iGOR
Racing Connections
Ports 32766-32786 -- 21 in total (UDP/incoming)
Details: 32766 is used for incoming connections, 32767-32786 are used for existing connections to each individual client.
WINDOWS FIREWALL
Another consideration that you have to bear in mind is the Windows Firewall, turned off originally but ever since Service Pack 2 it has been enabled by default. Every port that a GPL server needs to allow incoming data for not only has to be allowed via port forwarding or a DMZ, but it also needs to be allowed through the Windows Firewall once it hits the server. This extra workload may tempt you into either running a DMZ or even turning off the Windows Firewall, but please don't consider either of these options, take the axtra time and effort to configure them properly, and never run with both a DMZ and Windows Firewall off. You may as we'll go out and leave your doors and windows open while you're at it.
NOTE: I found that once I had configured the necessary port forwards and firewall exceptions, the first time I ran the server online Windows Firewall asked me twice to unblock something that required access, and that was the gplc67.exe and gplc65.exe.
Once everything is forwarded and unblocked you are ready to get your server listed on iGOR.
NOTE: You may only need to forward the incoming ports as your NAT router will usually allow all outgoing traffic by default. Windows Firewall currently does not block outgoing data, only incoming data, so unless you are running a third party firewall you shouldn't need to unblock outgoing ports.
General Listings of the ports
Port 113 (TCP/incoming) - not essential
Port 6970 (UDP/outgoing)
Port 6971 (UDP/incoming)
Port 6667 (TCP/outgoing)
Port 30196 (TCP/incoming)
Port 30196 (TCP/outgoing)
Port 30197 (TCP/outgoing)
Port 30198 (TCP/incoming)
Port 30198 (TCP/outgoing)
Port 30199 (UDP/outgoing)
Ports 32766-32786 (UDP/incoming)
iGOR uses several ports for internet communications. Some of these can be changed, others cannot.
IRC Chat
Port 6667 (TCP/outgoing) - cannot be changed.
IRC Ident Server
Port 113 (TCP/incoming) - cannot be changed. (It is not essential that this port is opened, but chat connections will be much quicker if you can open this port for incoming connections / add it to your port forwarding list.
Race List
Port 30197 (TCP/outgoing)- cannot be changed.
Remote Hosting Client
Port 30196 (TCP/outgoing)
By default, GPL uses the following ports:
Broadcasting
Port 6970 (UDP/outgoing) - used by GPL to broadcast the status of the races to the RaceList server.
HOWEVER, iGOR changes this port to 30199 (UDP/outgoing) to keep the range of ports required by iGOR to a single block (30196-30199).
Pings
Port 6971 (UDP/incoming) - used by GPL for ping responses. Not used by iGOR
Racing Connections
Ports 32766-32786 -- 21 in total (UDP/incoming)
Details: 32766 is used for incoming connections, 32767-32786 are used for existing connections to each individual client.
WINDOWS FIREWALL
Another consideration that you have to bear in mind is the Windows Firewall, turned off originally but ever since Service Pack 2 it has been enabled by default. Every port that a GPL server needs to allow incoming data for not only has to be allowed via port forwarding or a DMZ, but it also needs to be allowed through the Windows Firewall once it hits the server. This extra workload may tempt you into either running a DMZ or even turning off the Windows Firewall, but please don't consider either of these options, take the axtra time and effort to configure them properly, and never run with both a DMZ and Windows Firewall off. You may as we'll go out and leave your doors and windows open while you're at it.
NOTE: I found that once I had configured the necessary port forwards and firewall exceptions, the first time I ran the server online Windows Firewall asked me twice to unblock something that required access, and that was the gplc67.exe and gplc65.exe.
Once everything is forwarded and unblocked you are ready to get your server listed on iGOR.
Copyright © JamesOnline.net. All rights reserved.