expose internal network to the outside world

[Lennart Sorensen]

On Wed, Sep 14, 2005 at 10:40:29PM -0400, Alex Beamish wrote:
> Hi Matt,
> 
> I believe what you want is port forwarding, or what you referred to as 
> 'trigger ports'.
> 
> As you described, a call on port 1000 will go to one machine, and a call to 
> port 2000 will go to another machine.
> 
> I believe if you had a real firewall instead of a little router (I have a 
> Netgear, same kind of box as yours), you could have subdomains, because 
> dyndns.org <http://dyndns.org> would pass
> 1.mydomain.dyndns.org<http://1.mydomain.dyndns.org>to your machine,
> identified as
> mydomain.dyndns.org <http://mydomain.dyndns.org> for further subdomain 
> resolution. But I'll be happy to hear an explanation from someone who knows 
> what they're talking about.

One IP = One service/port.

DNS is only used to lookup what the IP is.  It doesn't get passed to the
server at all (except in http 1.1 and the like).  All it sees is
connection from x.x.x.x port xxx to y.y.y.y port yyy.

> I use dyndns.org <http://dyndns.org> and port forwarding myself -- works 
> beautifully.

Lennart Sorensen
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml