1
0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-01-25 01:02:24 +00:00

Document effect of settings changes on existing connections/forwardings.

Also mention that service names can be used instead of port numbers.

[originally from svn r5283]
This commit is contained in:
Jacob Nevins 2005-02-10 01:04:06 +00:00
parent 4e7a72310f
commit 339242c9bb

View File

@ -2443,11 +2443,15 @@ address to listen on, by specifying (for instance) \c{127.0.0.5:79}.
See \k{using-port-forwarding} for more information on how this
works and its restrictions.
In place of port numbers, you can enter service names, if they are
known to the local system. For instance, in the \q{Destination} box,
you could enter \c{popserver.example.com:pop3}.
You can modify the currently active set of port forwardings in
mid-session using \q{Change Settings}. If you delete a local or
dynamic port forwarding in mid-session, PuTTY will stop listening
for connections on that port, so it can be re-used by another
program. If you delete a remote port forwarding, note that:
mid-session using \q{Change Settings} (see \k{using-changesettings}).
If you delete a local or dynamic port forwarding in mid-session, PuTTY
will stop listening for connections on that port, so it can be re-used
by another program. If you delete a remote port forwarding, note that:
\b The SSHv1 protocol contains no mechanism for asking the server to
stop listening on a remote port.
@ -2463,6 +2467,11 @@ although the port cannot be reused by another program, you can at
least be reasonably sure that server-side programs can no longer
access the service at your end of the port forwarding.
If you delete a forwarding, any existing connections established using
that forwarding remain open. Similarly, changes to global settings
such as \q{Local ports accept connections from other hosts} only take
effect on new forwardings.
\S{config-ssh-portfwd-localhost} Controlling the visibility of
forwarded ports