Changes between Version 1 and Version 2 of doc/IPv6RelayHowto


Ignore:
Timestamp:
May 25, 2014, 8:03:49 PM (4 years ago)
Author:
adietrich
Comment:

Fixed in-page links and code blocks

Legend:

Unmodified
Added
Removed
Modified
  • doc/IPv6RelayHowto

    v1 v2  
    22In Oct 2012, support for clients connecting to relays as well as relays publishing IPv6 addresses and accepting clients connecting over IPv6 had been implemented. As of Jan 2013, there is also support for exiting to IPv6 destinations. See [https://trac.torproject.org/projects/tor/wiki/org/roadmaps/Tor/IPv6 Tor on IPv6 road map] for more detailed information about which versions of Tor that support different aspects of Tor on IPv6.
    33
    4 
    54== Table of Contents ==
    6 
    7  * [https://people.torproject.org/%7Elinus/ipv6-relay-howto.html#sec-1 1 Relays on IPv6]
    8    * [https://people.torproject.org/%7Elinus/ipv6-relay-howto.html#sec-1-1 1.1 Ordinary relays]
    9    * [https://people.torproject.org/%7Elinus/ipv6-relay-howto.html#sec-1-2 1.2 Bridges]
    10  * [https://people.torproject.org/%7Elinus/ipv6-relay-howto.html#sec-2 2 Authoritative directory specifics]
    11  * [https://people.torproject.org/%7Elinus/ipv6-relay-howto.html#sec-3 3 Client behaviour]
    12 
     5 * [#sec-1 1 Relays on IPv6]
     6   * [#sec-1-1 1.1 Ordinary relays]
     7   * [#sec-1-2 1.2 Bridges]
     8 * [#sec-2 2 Authoritative directory specifics]
     9 * [#sec-3 3 Client behaviour]
    1310
    1411=== 1 Relays on IPv6 === #sec-1
     
    1714The way you make your relay bind to and publish an IPv6 OR port is to add another ORPort config option to your torrc file. You can keep your IPv4 ORPort option as is.
    1815
    19 For the time being you need to configure your numeric IPv6 address explicitly within square brackets^[https://people.torproject.org/%7Elinus/ipv6-relay-howto.html#fn-.1 1]^, like so:
    20 
     16For the time being you need to configure your numeric IPv6 address explicitly within square brackets^[#fn1 1]^, like so:
    2117
    2218{{{
    2319ORPort [2001:DB8::1]:9050
     20}}}
    2421
    25 }}}
    2622There is currently no support for running a DIR port on IPv6. Leave any !DirPort option as is.
    2723
    28 There is currently no way of running an IPv6 only relay^[https://people.torproject.org/%7Elinus/ipv6-relay-howto.html#fn-.2 2]^. Your relay will have to publish both an IPv4 and an IPv6 OR port. This limitation will go away but note that your relay will need to be able to make outgoing IPv4 connections for a foreseeable future.
     24There is currently no way of running an IPv6 only relay^[#fn2 2]^. Your relay will have to publish both an IPv4 and an IPv6 OR port. This limitation will go away but note that your relay will need to be able to make outgoing IPv4 connections for a foreseeable future.
    2925
    3026The !OutboundBindAddress config option can be set to make Tor use a specific source address for outbound connections. This can be useful if your host has more than one IPv6 address. This option can be used twice, once per address family. Enclose an IPv6 address in square brackets.
    3127
    32 After making changes to the torrc file, a restart of Tor is recommended. Some reconfiguration is done properly when Tor is sent a HUP signal while other is not. Specifically, removing an IPv6 OR port from the configuration and sending HUP will not be honoured by Tor at the moment^[https://people.torproject.org/%7Elinus/ipv6-relay-howto.html#fn-.3 3]^. Please note that you won't get a warning about your OR port not being reachable if it isn't^[https://people.torproject.org/%7Elinus/ipv6-relay-howto.html#fn-.4 4]^.
    33 
     28After making changes to the torrc file, a restart of Tor is recommended. Some reconfiguration is done properly when Tor is sent a HUP signal while other is not. Specifically, removing an IPv6 OR port from the configuration and sending HUP will not be honoured by Tor at the moment^[#fn3 3]^. Please note that you won't get a warning about your OR port not being reachable if it isn't^[#fn4 4]^.
    3429
    3530==== 1.1 Ordinary relays ==== #sec-1-1
     
    3833{{{
    3934a [2001:67c:289c::9]:80
     35}}}
    4036
    41 }}}
    4237In order to be able to exit to IPv6 addresses, exit relays __must__ set
    4338
    4439{{{
    4540IPv6Exit 1
     41}}}
    4642
    47 }}}
    4843If you don't want to exit to IPv6, please set the (undocumented) exit policy for IPv6 to reject all exiting to IPv6 addresses:
    4944
    5045{{{
    5146ExitPolicy reject6 *:*
    52 
    5347}}}
    5448
     
    5650A bridge relay with an IPv6 OR port will be distributed by the Bridge DB. The part of IPv6 bridges ending up in the "http pool" are accessed through https://bridges.torproject.org/?ipv6=True.
    5751
    58 
    5952=== 2 Authoritative directory specifics === #sec-2
    6053The AuthDirHasIPv6Connectivity config option is used to make an authoritative directory require successful reachability testing of IPv6 OR ports to consider voting for them (or simply publish them, in the case of a bridge authority).
    6154
    62 Note that authorities, directory as well as bridge, do not yet make full use of IPv6^[https://people.torproject.org/%7Elinus/ipv6-relay-howto.html#fn-.5 5]^. Specifically, there is no way to make an authority export any of its authority-specific functions over IPv6 -- a client can not be configured to bootstrap over IPv6, an authority can not vote over IPv6, and more.
    63 
     55Note that authorities, directory as well as bridge, do not yet make full use of IPv6^[#fn5 5]^. Specifically, there is no way to make an authority export any of its authority-specific functions over IPv6 -- a client can not be configured to bootstrap over IPv6, an authority can not vote over IPv6, and more.
    6456
    6557=== 3 Client behaviour === #sec-3
     
    7264Note that clients running with bridges do not need to set any IPv6 specific configuration options in order to connect to bridges over IPv6. Putting an IPv6 address in a !BridgeRelay option is enough.
    7365
     66== Footnotes: ==
     67[=#fn1 1:] [https://trac.torproject.org/projects/tor/ticket/5940 #5940: Figure out own IPv6 address]
    7468
    75 == Footnotes: ==
    76 ^[https://people.torproject.org/%7Elinus/ipv6-relay-howto.html#fnr-.1 1]^ [https://trac.torproject.org/projects/tor/ticket/5940 #5940: Figure out own IPv6 address]
     69[=#fn2 2:] [https://trac.torproject.org/projects/tor/ticket/5788 #5788: Add support for relays without an IPv4 address]
    7770
    78 ^[https://people.torproject.org/%7Elinus/ipv6-relay-howto.html#fnr-.2 2]^ [https://trac.torproject.org/projects/tor/ticket/5788 #5788: Add support for relays without an IPv4 address]
     71[=#fn3 3:] [https://trac.torproject.org/projects/tor/ticket/6026 #6026: Relays don't realise that their IPv6 OR port has changed]
    7972
    80 ^[https://people.torproject.org/%7Elinus/ipv6-relay-howto.html#fnr-.3 3]^ [https://trac.torproject.org/projects/tor/ticket/6026 #6026: Relays don't realise that their IPv6 OR port has changed]
     73[=#fn4 4:] [https://trac.torproject.org/projects/tor/ticket/6939 #6939: Missing log entry for IPv6 ORPort reachability check]
    8174
    82 ^[https://people.torproject.org/%7Elinus/ipv6-relay-howto.html#fnr-.4 4]^ [https://trac.torproject.org/projects/tor/ticket/6939 #6939: Missing log entry for IPv6 ORPort reachability check]
    83 
    84 ^[https://people.torproject.org/%7Elinus/ipv6-relay-howto.html#fnr-.5 5]^ [https://trac.torproject.org/projects/tor/ticket/6027 #6027: Directory authorities on IPv6]
     75[=#fn5 5:] [https://trac.torproject.org/projects/tor/ticket/6027 #6027: Directory authorities on IPv6]