> > > I have not checked the TCP/IP stack code before, but how does someone > like > > BSD handle storing of SYN packets in their network code? I imagine SYN > > packet is similar to challenge, but I don't know too much about TCP/IP. > > The trick is to not store the cookie on the server but rather create > it in a way so it can be computed from the reply again: > http://en.wikipedia.org/wiki/SYN_cookies > > Interesting. Using the cookie technique might be possible in ioquake3 server if you're willing to bypass the sv_maxPing setting. At least in my ioquake3 server branch, the "ping time" is stored in the challenges array, and is set the first time a connect packet arrives for a challenge. This "ping time" isn't recomputed in my code every time a new connect packet arrives (I know ioquake3 used to have the "Server is for low pings only" problem when server was full and you tried reconnecting). This would be a problem if we used cookies, because the cookie would only have the time of sending the challengeResponse. May be other problems too, but none I can see right away.
_______________________________________________ ioquake3 mailing list [email protected] http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org By sending this message I agree to love ioquake3 and libsdl.
