nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-01-25 01:02:24 +00:00
Code Issues Projects Releases Wiki Activity

... of course, it would help if I remembered to _document_ dynamic

Browse Source 
port forwarding. Ahem.

[originally from svn r3056]
This commit is contained in:
Simon Tatham 2003-04-05 11:52:42 +00:00
parent 8a3ff2bf3e
commit 3f83c3b140
2 changed files with 33 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/config.but
View File

@ -1,4 +1,4 @@
\versionid $Id: config.but,v 1.59 2003/03/07 09:03:11 simon Exp $
\versionid $Id: config.but,v 1.60 2003/04/05 11:52:42 simon Exp $
\C{config} Configuring PuTTY
@ -1978,7 +1978,8 @@ To add a port forwarding:
\b Set one of the \q{Local} or \q{Remote} radio buttons, depending
on whether you want to forward a local port to a remote destination
(\q{Local}) or forward a remote port to a local destination
(\q{Remote}).
(\q{Remote}). Alternatively, select \q{Dynamic} if you want PuTTY to
provide a local SOCKS proxy on a local port.
\b Enter a source port number into the \q{Source port} box. For
local forwardings, PuTTY will listen on this port of your PC. For
@ -1986,10 +1987,12 @@ remote forwardings, your SSH server will listen on this port of the
remote machine. Note that most servers will not allow you to listen
on port numbers less than 1024.
\b Enter a hostname and port number separated by a colon, in the
\q{Destination} box. Connections received on the source port will be
directed to this destination. For example, to connect to a POP-3
server, you might enter \c{popserver.example.com:110}.
\b If you have selected \q{Local} or \q{Remote} (this step is not
needed with \q{Dynamic}), enter a hostname and port number separated
by a colon, in the \q{Destination} box. Connections received on the
source port will be directed to this destination. For example, to
connect to a POP-3 server, you might enter
\c{popserver.example.com:110}.
\b Click the \q{Add} button. Your forwarding details should appear
in the list box.
@ -2023,7 +2026,7 @@ controls in the Tunnels panel to change this:
\b The \q{Local ports accept connections from other hosts} option
allows you to set up local-to-remote port forwardings in such a way
that machines other than your client PC can connect to the forwarded
port.
port. (This also applies to dynamic SOCKS forwarding.)
\b The \q{Remote ports do the same} option does the same thing for
remote-to-local port forwardings (so that machines other than the

30
doc/using.but
View File

@ -1,4 +1,4 @@
\versionid $Id: using.but,v 1.13 2003/03/20 22:12:12 ben Exp $
\versionid $Id: using.but,v 1.14 2003/04/05 11:52:42 simon Exp $
\C{using} Using PuTTY
@ -300,15 +300,25 @@ To do this, just select the \q{Remote} radio button instead of the
number on the \e{server} (note that most servers will not allow you
to use port numbers under 1024 for this purpose).
An alternative way to forward local connections to remote hosts is
to use dynamic SOCKS proxying. For this, you will need to select the
\q{Dynamic} radio button instead of \q{Local}, and then you should
not enter anything into the \q{Destination} box (it will be
ignored). This will cause PuTTY to listen on the port you have
specified, and provide a SOCKS proxy service to any programs which
connect to that port. So, in particular, you can forward other PuTTY
connections through it by setting up the Proxy control panel (see
\k{config-proxy} for details).
The source port for a forwarded connection usually does not accept
connections from any machine except the SSH client or server machine
itself (for local and remote forwardings respectively). There are
controls in the Tunnels panel to change this:
\b The \q{Local ports accept connections from other hosts} option
allows you to set up local-to-remote port forwardings in such a way
that machines other than your client PC can connect to the forwarded
port.
allows you to set up local-to-remote port forwardings (including
dynamic port forwardings) in such a way that machines other than
your client PC can connect to the forwarded port.
\b The \q{Remote ports do the same} option does the same thing for
remote-to-local port forwardings (so that machines other than the
@ -451,7 +461,7 @@ These options are equivalent to the username selection box in the
Connection panel of the PuTTY configuration box (see
\k{config-username}).
\S2{using-cmdline-portfwd} \c{-L} and \c{-R}: set up port forwardings
\S2{using-cmdline-portfwd} \c{-L}, \c{-R} and \c{-D}: set up port forwardings
As well as setting up port forwardings in the PuTTY configuration
(see \k{config-ssh-portfwd}), you can also set up forwardings on the
@ -465,12 +475,18 @@ one of these:
\c putty -L 5110:popserver.example.com:110 -load mysession
\c plink mysession -L 5110:popserver.example.com:110
And to forward a remote port to a local destination, just use the
\c{-R} option instead of \c{-L}:
To forward a remote port to a local destination, just use the \c{-R}
option instead of \c{-L}:
\c putty -R 5023:mytelnetserver.myhouse.org:23 -load mysession
\c plink mysession -R 5023:mytelnetserver.myhouse.org:23
To set up SOCKS-based dynamic port forwarding on a local port, use
the \c{-D} option. For this one you only have to pass the port
number:
\c putty -D 4096 -load mysession
For general information on port forwarding, see
\k{using-port-forwarding}.