config: Make clients tell dual-stack exits they prefer IPv6

Make Tor clients tell dual-stack exits that they prefer IPv6
connections.

This change is equivalent to setting the PreferIPv6 flag on
SOCKSPorts (and most other listener ports). Tor Browser has
been setting this flag for some time, and we want to remove a
client distinguisher at exits.

Also update the man page, putting all the IP flags in their
non-default forms.

Closes ticket 32637.

1 files changed, 9 insertions, 7 deletions

diff --git a/doc/tor.1.txt b/doc/tor.1.txt
index d1583c3dc7..c84eba56e8 100644
--- a/doc/tor.1.txt
+++ b/doc/tor.1.txt
@@ -1755,14 +1755,16 @@ The following options are useful only for clients (that is, if
     Other recognized __flags__ for a SocksPort are:
     **NoIPv4Traffic**;;
         Tell exits to not connect to IPv4 addresses in response to SOCKS
-        requests on this connection.
-    **IPv6Traffic**;;
-        Tell exits to allow IPv6 addresses in response to SOCKS requests on
-        this connection, so long as SOCKS5 is in use.  (SOCKS4 can't handle
-        IPv6.)
-    **PreferIPv6**;;
+        requests on this connection. (Allowing IPv4 is the default.)
+    **NoIPv6Traffic**;;
+        Tell exits to not connect to IPv6 addresses in response to SOCKS
+        requests on this connection. This option is only relevant when SOCKS5
+        is in use, because SOCKS4 can't handle IPv6.  (Allowing IPv6 is the
+        default.)
+    **NoPreferIPv6**;;
         Tells exits that, if a host has both an IPv4 and an IPv6 address,
-        we would prefer to connect to it via IPv6. (IPv4 is the default.)
+        we would prefer to connect to it via IPv4. (IPv6 is the default in
+        recent versions of Tor.)
     **NoDNSRequest**;;
         Do not ask exits to resolve DNS addresses in SOCKS5 requests. Tor will
         connect to IPv4 addresses, IPv6 addresses (if IPv6Traffic is set) and