Changes between Version 2 and Version 3 of doc/IPv6RelayHowto


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

Use PageOutline macro, fix heading levels

Legend:

Unmodified
Added
Removed
Modified
  • doc/IPv6RelayHowto

    v2 v3  
     1[[PageOutline(2-3)]]
     2
    13= A Tor relay operators IPv6 HOWTO =
     4
    25In 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.
    36
    4 == Table of Contents ==
    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]
    10 
    11 === 1 Relays on IPv6 === #sec-1
     7== 1 Relays on IPv6 ==
    128Assuming that you already have an ordinary IPv4 relay up and running, this is how to make it an IPv6 relay.
    139
     
    2824After 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]^.
    2925
    30 ==== 1.1 Ordinary relays ==== #sec-1-1
     26=== 1.1 Ordinary relays ===
    3127The IPv6 OR port of an ordinary relay should show in the consensus as an "a" line. For example:
    3228
     
    4743}}}
    4844
    49 ==== 1.2 Bridges ==== #sec-1-2
     45=== 1.2 Bridges ===
    5046A 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.
    5147
    52 === 2 Authoritative directory specifics === #sec-2
     48== 2 Authoritative directory specifics ==
    5349The 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).
    5450
    5551Note 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.
    5652
    57 === 3 Client behaviour === #sec-3
     53== 3 Client behaviour ==
    5854A few notes on how clients behave. Might be useful for testing your relays.
    5955
     
    6460Note 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.
    6561
    66 == Footnotes: ==
     62== Footnotes ==
    6763[=#fn1 1:] [https://trac.torproject.org/projects/tor/ticket/5940 #5940: Figure out own IPv6 address]
    6864