[gameprogrammer] Re: TCP/IP Problem: NAT

On Fri, 19 Nov 2004 14:02:05 -0600, Bob Pendleton <bob@xxxxxxxxxxxxx> wrote:
> On Fri, 2004-11-19 at 12:47, Chris Nystrom wrote:
> 
> Hi Chris, how's it going?

Good. Thank you for asking. How are you doing?
 
> This problem has no solution. NAT is designed to hide all the boxes on
> one side of the box behind a single IP address. The result is that they
> cannot be addressed from the other side of the box.

I suppose that is good news. Knowing for sure that my problem has no
solution saves me the time in trying to get it to work.

> NATs can be
> configured to send requests for specific ports to specific machines
> behind the NAT. That is handy for hiding servers behind a NAT and for
> redirecting traffic to different servers. But, it is not a solution to
> your problem.

You are right.
 
> OTOH, all the machines behind the NAT can address the rest of the world.
> The solution to your problem is to have the client contact the server,
> not the other way around.

Hmmm... I suppose  I could do that.

> And no, X can't get around NAT either.

Hmmm... I am on the NAT machine and I SSH to a server, and then I type
"xclock" and
the xclock pops right up on the display of the origianal NAT machine.
How does the xclock app running on the server know how to communicate
back to the X server running on the NAT machine to display itself?

I assume this must be some ssh mojo? xclock knows nothing of ssh right
? So how does X know how to use the ssh mojo ? More importantly how
can one set up ones own application to work the same way ?

Interstingly, the DISPLAY variable that ssh sets up is set to
localhost...hmmm...a mystery.

Thank,
Chris

-- 
Chris Nystrom <cnystrom@xxxxxxxxx>
http://www.newio.org/~ccn
AIM: nystromchris


---------------------
To unsubscribe go to http://gameprogrammer.com/mailinglist.html

Other related posts: