Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Quake/QW and Pipeline 75 and NAT
At 02:41 PM 11/1/97 -0800, Jason Eggleston wrote:
>James Johnson wrote:
>>
>> Strange my IP is 192.168.100.101, and I can play Quake/QW perfectly fine
>> (Ascend Pipeline 75 w/ multi-IP NAT). I get one valid IP address from my
>> ISP, and I wanted to play Quake so Multi-IP NAT was my only choice.
>> Fortunately I don't need more than one machine connected. I know NAT single
>> IP does not work. Read on for the reason...
>
>This still boils down to a problem with Quake. Every other UDP/TCP
>program I've used manages to make it through the address translation...
>why? Because the server doesn't depend on any data within the TCP/UDP
>packet to determine the source port/source IP address combination.
>Apparently, there is some inline information encoded for the client port
>number. This is bad.
>
>Thanks,
Um did you read all of my posting? There is no information in the datagram
pertaining to a port # other than the udp port. If I send a packet from any
machine with a specific port destionation to a Pipeline (doing Single IP
NAT) the port # gets mangled.
This is perfectly fine. Everyone knows that unless you tell the Pipeline to
do a specific mapping for that port this will happen. This is what NAT
does. Perfectly normal.
Its not a problem with Quake, its not a problem with the Pipeline. It just
the way NAT works.
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
Follow-Ups: