That will be a problem because that instances will get several IPv6-addresses during the day because of active privacy extensions and the router get a new /56 for IPv6 from the ISP every day. A manual change of the torrc is inefficient for me. Because of that I will deactivate IPv6-support at the affected instances until the discovery of a IPv6-address will be like for IPv4 :-( I am not a programmer but perhaps it will be solved like for dyndns-services.
Marcel > JovianMallard <[email protected]> hat am 13. Mai 2015 um 18:24 geschrieben: > > > Googling finds these: > https://lists.torproject.org/pipermail/tor-commits/2012-May/042676.html > https://trac.torproject.org/projects/tor/ticket/5146 > https://trac.torproject.org/projects/tor/ticket/5940 > > Looks like tor hasn't been taught to turn [::] into a reachable global > IP address yet (for reporting to the network - listening would work > fine), so I think you'll need to use your actual global IPv6 address > there. > > > On 05/13/2015 12:13 PM, [email protected] wrote: > > thanks, now I got a similar information: > > > >> 13:36:02 [WARN] Unable to use configured IPv6 address "[::]" in a > >> descriptor. Skipping it. Try specifying a globally reachable address > >> explicitly. > > > > what do you think? > > > > Marcel _______________________________________________ tor-relays mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
