[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: expose internal network to the outside world





Matt Price wrote:

ssh -p 2000 -l me mydomain.dyndns.org
which gets to the router; the router sees that it's supposed to forward
requests on port 2000 to 192.168.2.199; 192.168.2.199 picks up the
request and an ssh tunnel is formed
You won't need tunneling for this, just the NAT that your "router" does. Your router should just forward all data to specified machine.

on the other hand, if I type
ssh -p 3000 -l metoo mydomain.dyndns.org
the router sends the request to 192.168.2.254 instead.
On my router confiugration screen, there seem to be 3 places where this
sort of thing can be done:
1. "DDNS" -- here I'm allowed to have 1 static IP address designated as
a "server" ; requests on ports 80,21,and 25 (http, ftp, smtp) are
forwarded on to the "server".  I've tried this and it works fine for
http at least (I get the standard debian default index page from my
local machine).  But there seems to be no further flexibility.
2. "NAT".  This section comes with the following instructions:

*Special Applications*

Some applications require multiple connections, such as Internet gaming,
video conferencing, Internet telephony and others. These applications
cannot work when Network Address Translation (NAT) is enabled. If you
need to run applications that require multiple connections, specify the
port normally associated with an application in the "Trigger Port"
field, select the protocol type as TCP or UDP, then enter the public
ports associated with the trigger port to open them for inbound traffic.

Note: The range of the Trigger Ports is from 1 to 65535.

THen there's a tablei nwhich I can associate "trigger ports" with
"public ports".  But I odn't think I really understand what this is
about, as thre seems to be no way to associate a particular local
machine with a forwarded port.

3. DMZ.  THis screen lets me associate a local IP address (192.168.2.x)
with a public IP address.  But this isn't what I want, is it?  Because
after all I only have one constantly-changing IP address available to
me...
Maybe. This is what I use, but I don't require direct ssh ability to both of my machines. I login to my machine in the DMZ and then ssh to my other machine from there--it feels more secure that way. If you can set a permanent IP address for your local machine then this should be fine.

Your other option is to see if your router has some firewall rules, such as map this to that.



Reply to: