|
jljr222 - Some of the ports are assigned dynamically I think. Find the PID of the game server process then on the shell as root via SSH, run lsof against it to see what all it has open, like if the TF2 server was running with pid 4173, run `lsof -Pnp 4173 |grep IP` on the shell and it should show you all the ports, both TCP and UDP that the server process is listening on. Other connections may be made client-style, where it's not acting as a server but connecting out to the remote stats/auth servers and failure there could be triggering the problem. To find those you'd need to use tcpdump/ngrep or strace the process while it made the connections.
|