nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-07-01 11:32:48 -05:00
Code Issues Projects Releases Wiki Activity

For local and dynamic port forwardings (i.e. the ones which listen

Browse Source 
on a local port), the `Auto' protocol option on the Tunnels panel
should always produce a port you can connect to in _either_ of IPv4
and v6, because the aim is for the user not to have to know or care
which one they're using. This was not the case on Windows, and now
is. Also, updated the docs to give more detail on issues like this.

[originally from svn r5083]
This commit is contained in:
Simon Tatham
2005-01-08 14:45:26 +00:00
parent 79629c729c
commit c57e9f0672
2 changed files with 70 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
doc/config.but
View File

@ -2494,12 +2494,15 @@ incoming connections in both IPv4 and (if available) IPv6
\b for a remote-to-local port forwarding, PuTTY will choose a
sensible protocol for the outgoing connection.
\# FIXME: work out what this paragraph means, reword it for clarity,
\# and reinstate it.
Note that on Windows the address space for IPv4 and IPv6 is
completely disjunct, so listening on IPv6 won't make PuTTY listen on
IPv4. This behaviour may be different on most remote hosts when they
are not operating Windows.
Note that some operating systems may listen for incoming connections
in IPv4 even if you specifically asked for IPv6, because their IPv4
and IPv6 protocol stacks are linked together. Apparently Linux does
this, and Windows does not. So if you're running PuTTY on Windows
and you tick \q{IPv6} for a local or dynamic port forwarding, it
will \e{only} be usable by connecting to it using IPv6; whereas if
you do the same on Linux, you can also use it with IPv4. However,
ticking \q{Auto} should always give you a port which you can connect
to using either protocol.
\H{config-ssh-bugs} The Bugs panel