Routers and Firewalls

This is likely to be the most common problem you will run into when trying to use GRiP, getting through your system's firewall and/or router. Users are free (and encouraged) to add your own solutions for various operating systems and routers in use, but it is difficult for us to provide any official or concrete details due to the sheer number of possible combinations of software involved. But there are a few bits of information we know you will definitely need and a few suggestion we can give you on getting GRiP configured to work with your hardware and software.

Firewalls

Most firewalls simply require you to let it know what program needs to be able to pass data through and what ports it will be using. See the bottom of this page for links to tips on dealing with Windows Firewall. If you are running a firewall other than Window Firewall, consult your user's manual for more information.

Routers

Probably the trickiest part of the equation for those not familiar with it, is getting your router to allow GRiP to communicate with the Internet and other players. In general, what needs to happen is that you set up a tunnel directing GRiP traffic that hits the router across the given GRiP ports to and from your specific computer on the local network. Again, specifics are difficult to give when there are so many different routers available. See your router's user manual for more information.

Ports Used

Unless you have changed the default settings GRiP is set up to run across port 4010 as its primary port. GRiP also uses two additonal ports for file transfer and private chat. These values will always be equal to the main port +1 and the main port +2 respectively. So by default GRiP uses ports 4010, 4011, and 4012. If you had changed the main port default to say 22005, then GRiP would use ports 22005, 22006, and 22007.

The private chat port (4012 by default) must be set to allow UDP traffic, while the other two ports should be set for TCP.