[CoLoCo] Remote Access

[Jim Hutchinson]

On Fri, May 9, 2008 at 10:58 AM, Michael Robbert <mrobbert at gmail.com> wrote:

> Jim,
> The problem is NAT, Network Adress Translation. Most home routers have to
> do this because you only get one public IP address. Your router then gives
> all of your local computers a private IP that can not be routed on the
> Internet. NAT does some fancy things with tcp/udp ports and tracks your
> connection. Essentially everything going out your router looks like it is
> coming directly from your router not from your PC. Then the return traffic
> needs to be translated by the router using its tracking tables. This means
> that connections can not be made to your internal PC from the Internet
> without some trickery like port forwarding.
> You'll have to look up any further info. My thumbs are getting tired.
>

Thanks Mike (sorry for your thumbs). I understand how NAT works. What I
don't understand is why using dyndns coupled with ssh and port forwarding on
the router won't won't. I do exactly this to connect my box at home. So I
must not have a clear picture of the problem.

----
Jim (Ubuntu geek extraordinaire)
----
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/ubuntu-us-co/attachments/20080509/cdac23bf/attachment.htm