tor and resolv.conf / ipv6

[Nick Mathewson]

On Thu, Sep 2, 2010 at 12:10 PM, Udo van den Heuvel <udovdh at xs4all.nl> wrote:
> On 2010-09-02 17:34, Udo van den Heuvel wrote:
>> Tor chokes and stops when it finds ipv6 numbers in resolv.conf.
>> Is this a known issue?

Sadly, yeah.

As a workaround, if you build Tor with Libevent 2.0.x, Tor will use
Libevent's evdns code, rather than its own internal (and
lagged-behind) implementation.  Libevent 2.0's dns code knows how to
handle IPv6 addresses for DNS servers.  (You can't do this with older
versions of Libevent, since until about Libevent 2.0, Tor required
evdns features that Libevent didn't have.)

As another workaround, you can specify an alternative resolv.conf file
using the ServerDNSResolvConfFile command.

As a real fix, there are a few possibilities.
   * Port the ipv6-resolver code over from Libevent 2.  [Not going to
happen in Tor 0.2.2.]
   * Re-port the entirety of evdns.c over from Libevent 2. [Definitely
not going to happen in Tor 0.2.2]
   * Just wait until Libevent 2.0.x is ubiquitous.

yrs,
-- 
Nick
***********************************************************************
To unsubscribe, send an e-mail to majordomo at torproject.org with
unsubscribe or-talk    in the body. http://archives.seul.org/or/talk/