X-Git-Url: https://git.distorted.org.uk/u/mdw/putty/blobdiff_plain/d6430b975d14ddbd53c40126fa9d00bea3c2d08b..6ee9b735013c0e636b027b77e9f6ba57a96e142f:/doc/config.but

diff --git a/doc/config.but b/doc/config.but
index 8992638d..bbe8495f 100644
--- a/doc/config.but
+++ b/doc/config.but
@@ -1,4 +1,4 @@
-\versionid $Id: config.but,v 1.44 2002/10/22 09:40:38 simon Exp $
+\versionid $Id: config.but,v 1.45 2002/12/18 11:39:25 simon Exp $
 
 \C{config} Configuring PuTTY
 
@@ -1881,6 +1881,19 @@ in the list box.
 To remove a port forwarding, simply select its details in the list
 box, and click the \q{Remove} button.
 
+In the \q{Source port} box, you can also optionally enter an IP
+address to listen on. Typically a Windows machine can be asked to
+listen on any single IP address in the \cw{127.*.*.*} range, and all
+of these are loopback addresses available only to the local machine.
+So if you forward (for example) \c{127.0.0.5:79} to a remote
+machine's \cw{finger} port, then you should be able to run commands
+such as \c{finger fred@127.0.0.5}. This can be useful if the program
+connecting to the forwarded port doesn't allow you to change the
+port number it uses. This feature is available for local-to-remote
+forwarded ports; SSH1 is unable to support it for remote-to-local
+ports, while SSH2 can support it in theory but servers will not
+necessarily cooperate.
+
 \S{config-ssh-portfwd-localhost} Controlling the visibility of
 forwarded ports