On Sat, 16 Oct 1999 21:57:49 -0700 (PDT), Fred Wright wrote:
> In the particular case of Quake, I've seen some dumps of Quake traffic
> between two machines (this may not involve a "Quake server"), and it
> appears to use a single port. Whether you need to explicitly redirect
> that port probably depends on whether the session is initiated outbound or
> inbound.
In the particular case of "classic" Quake (i.e. Quake 1, not
Quakeworld) the problem lies in the fact that Quake is a dos app
that uses a really weird networking protocol.
I'm not an expert on these matters, but it appears that Quake
includes the source port (and IP?) not only in the headers but in
the data part of the packets which thus gets not changed by
IP-NAT -> the reponse packets end up whereever and the client
sits there with no data.
As I said in a different mail, there is a proxy for classic quake
that allows *one* client to connect through the gateway machine
(that limitation is in fact not an issue of the proxy but one of
the Quake server implementation - it will not allow multiple
clients from the same IP).
Regards,
Eike
--
Eike M. Lang
PGP-Mail welcome - key available at:
http://jayhawk.home.pages.de/
--
To unsubscribe send "unsubscribe miamidx-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
