It is end 2016 we should change from must have IPv4 to must have IPv6
and can have IPv4. All this new fancy ISPs that have FTTH and give you
500 MBit/s symmetric internet access have Carrier grade NAT because they
were late to the Party and don't get IPv4 from the LIRs.
You can't run there a relay because of the stupid you need a public
accessible IPv4 address shit. So i see there a big gain in making that
change, because then the guys with the big home pipes can run relays
too. On the other hand datacenters that have only IPv4 are very
uncommon, so there would be no big loss of relays. Clients that are IPv4
only can use Dual-Stack relays so they won't have a problem.
On 26.11.2016 11:26, teor wrote:
On 26 Nov. 2016, at 21:14, Lluís <2015....@gmail.com> wrote:
If I didn't understand right, a relay can use IPv6 but it will **not**
bootstrap unless it is assigned an IPv4 address.
Does that summarize the discussion ?
Yes.
A relay *must* have an IPv4 address to publish a descriptor.
A relay can also publish an IPv6 address it its descriptor.
Tim
Cheers
Lluís
teor:
On 23 Nov. 2016, at 02:54, Ralph Seichter <tor-relays...@horus-it.de> wrote:
On 22.11.16 03:33, teor wrote:
...
ClientPreferIPv6DirPort 1
This option was introduced and deprecated in the 0.2.8 alpha series,
it has no effect.
That's unexpected. https://www.torproject.org/docs/tor-manual.html.en
still lists this option. I went through this manual page for anything
IPv6-related I could find.
Here is the ticket to deprecate that option:
https://trac.torproject.org/projects/tor/ticket/19704
It's just waiting for someone to write the code and change the manual.
T
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
T
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays