Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Quake/QW and Pipeline 75 and NAT
This is not Ascend's fault. id Software violated a rule of thumb, if
not an RFC. If a server needs to know the address of a client, the
server should check the source address of the incoming datagrams.
Granted, this won't help you play Quake, but it will point to the tree
you should be barking at... However, this is old news, and id is not
likely to fix it until hopefully Quake 2.
Thanks,
rj wrote:
>
> Quake and QW grab the local machine's ip (192.168.100.102 in my case)
> and encode this into the datagram. The router correctly fixes the ip
> address in the header but not the datagram. That is why you can connect
> to a server but never play. The server is sending updates to the fake
> (192.168.100.102) address.
>
> Is there ANYTHING Ascend can do to get this fixed? Ascend, are you out
> there?
> ++ Ascend Users Mailing List ++
> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd: <http://www.nealis.net/ascend/faq>
--
Jason Eggleston
SysAdmin, Jet.Net Inc.
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
References: