Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re[2]: (ASCEND) Quake/QW and Pipeline 75 and NAT

     I had good luck using static mappings in order to get X-Windows 
     working for some of users running NAT on their P75s.  The thing I was 
     never able to find out was - precisely WHAT ports need to be mapped in 
     order for Quake to work?  If someone could that that info from id - we 
     could likely develop a workaround for our Quake addicts.
     
     -Michael


______________________________ Reply Separator _________________________________
Subject: Re: (ASCEND) Quake/QW and Pipeline 75 and NAT
Author:  James Johnson <plexus@plexus.seanet.com> at Internet
Date:    10/31/97 8:26 PM


     
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...
     
No the problem you face is not the IP, but the port # with Quake. The 
Pipeline uses the port # for translation purposes (as do all NAT 
implementations). This # gets mangled in the process. I observered, using 
NetXray, the port # which I sent out to the Quake server and the port # which 
came back. I'd be sending out 27k (or something close) and be getting back 
ports in the 4k range. Since Quake wasn't listening there the packet went 
un-heard, and into the bitbucket. 
     
You might be able to set static maps. I never tried this.
     
With Multi-IP NAT the port #'s do not get translated and thus Quake works.
     
I don't think any IP information is contained in the Quake datagram. This 
makes sense, because it is in the application layer. I assume Quake uses 
the same protocol for both IPX and IP. (Why would they change it?) In order 
to (re)use this code it would have to be independant of the various network 
protocols (ie above the transport layer).
     
If you find any errors in my comments let me know. After all most of what 
I've stated was from observations (packet sniffing), and reading various 
RFCs on NAT. I'd like to know what other have found too.
     
At 02:31 PM 10/31/97 -0800, 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>
>
>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com 
To get FAQ'd:   <http://www.nealis.net/ascend/faq>
Received: from Mailer.symantec.com (198.6.49.5) by smtp-ima.symantec.com with
SMTP
  (IMA Internet Exchange 2.11 Enterprise) id 0000D4AE; Fri, 31 Oct 97 21:40:26
-0800
Received: from max.bungi.com (max.bungi.com [207.126.97.7]) by
Mailer.symantec.com (8.8.4/8.7.6) with ESMTP id VAA26554 for
<MMedwid@symantec.com>; Fri, 31 Oct 1997 21:42:09 -0800 (PST)
Received: (from majordom@localhost)
	by max.bungi.com (8.8.7/8.8.7) id UAA15278
	for ascend-users-outgoing; Fri, 31 Oct 1997 20:26:44 -0800 (PST)
X-Authentication-Warning: max.bungi.com: majordom set sender to
owner-ascend-users using -f
Received: from mx.seanet.com (dns2.seanet.com [199.181.164.2])
	by max.bungi.com (8.8.7/8.8.7) with ESMTP id UAA15273
	for <ascend-users@max.bungi.com>; Fri, 31 Oct 1997 20:26:39 -0800 (PST)
Received: from plexus (plexus.seanet.com [204.182.64.122]) by mx.seanet.com
(8.8.5/Seanet-8.7.3) with SMTP id UAA17954; Fri, 31 Oct 1997 20:26:33 -0800
(PST)
Message-Id: <3.0.32.19971031202625.006d2900@pop.seanet.com>
X-Sender: plexus@pop.seanet.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Fri, 31 Oct 1997 20:26:32 -0800
To: rjm@cet.com, ascend-users@max.bungi.com
From: James Johnson <plexus@plexus.seanet.com>
Subject: Re: (ASCEND) Quake/QW and Pipeline 75 and NAT
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ascend-users@max.bungi.com
Precedence: bulk