Game Development Community

Small bug / request regarding Network play...

by Kevin Milburn · in General Game Discussion · 06/27/2003 (10:12 am) · 4 replies

I have experienced a problem with the network play.. It isn't really a bug in Orbz, but I believe it's only Orbz that can get round it. So here goes..

I have a DSL connection with a NAT router. Ocassionally when playing there seems to be a problem with the connection, and the 'no connection' symbol appears.. Every now and again the problem is serious enough that the router appears to drop some information regarding the incoming connection from the Orbz server.. As a result, Orbz appears to freeze (although it does seem to update every 30 seconds or so), and I can see lots of activity on the router with incoming data, but the router drops it!

When this happens, orbz will still run, and will attempt to return to the lobby when the game is over, but fails to do so, resulting in Orbz having to be killed.. The server also still thinks that the system is connected.

Depending on how the network connectivity is working, is it possible to get Orbz to poke the incoming connection periodically, hopefully preventing the entry being removed from the NAT table (or even restoring it). Or Orbz needs to detect when it's not receiving the data correctly, and recover the connction somehow..

#1
06/27/2003 (11:21 am)
Can you set your NAT to keep alive the forwarded ports?
#2
06/30/2003 (2:18 pm)
No, there is no keep alive option.... And as Asus no longer support this model, there isn't going to be!!!

However, It's happened again, and I noticed that the data is actually making it into my internal network (helps if I pay attention to the correct LED). So NAT is not the problem. But I still get left seemingly with the majority of the incoming data being ignored completely by Orbz..

BTW, This is the Linux version, running on SuSE 8.2...
#3
07/05/2003 (4:50 am)
Just in case you are readig this Justin....

Once again, the comms between my machine and the servers failed, I have extraced some information from the conversation going on between my box and the server when attempting to return to the lobby (using tcpdump)...

The resulting file can be found at www.kmilburn.force9.co.uk/returntolobby.txt..

Hopefully, this may give some indication as to what is happening. If there is any other information you need, let me know.
#4
07/09/2003 (9:43 pm)
Definately has us stumped. Would it help to know the ports that Torque is using for the network traffic? Maybe there are settings on the NAT to allow traffic on a certain port without blocking it or interfering with it?