[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: tor and resolv.conf / ipv6
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: tor and resolv.conf / ipv6
- From: Nick Mathewson <nickm@xxxxxxxxxxxxx>
- Date: Thu, 2 Sep 2010 12:56:36 -0400
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Thu, 02 Sep 2010 12:56:43 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=BFLjPYdPzg6a2pZ3cWRC/otOA/xVnPNg+ZmYxH+giYI=; b=u0cJhhBT9C+MS3zzt/fEhIeKav15sj6cOJ52UQo3W8vTEaYkRbrdvJMIzVTiAZxdgd JXoWB03oua+LNyzJw9Xt+gZS6NWiYkQWmzMbPPWYQ4u8vUUFSNSrdeNLKHNZpD+VSHog URzKjiNraOIwst5dUp1xpxCPH8q2Ej1DLjvj0=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=ap3lnZX8MWyDAo7tvT3oB4h9kZbaDiWiTOc9sHvuaZdc4QgtvqI33z43DKigytob7j 6oECLz2cvRnDnoJho1D7qD+mxR8CbWvfLHYzkv4wbpdg5YZYN0CfqT3OkP29DSkd0uaK WsFv1uxzngb/VXNrdeyrBHE7AdEE5emK0Iju0=
- In-reply-to: <4C7FCC82.6040805@xxxxxxxxx>
- References: <4C7FC41D.2090808@xxxxxxxxx> <4C7FCC82.6040805@xxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
On Thu, Sep 2, 2010 at 12:10 PM, Udo van den Heuvel <udovdh@xxxxxxxxx> 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@xxxxxxxxxxxxxx with
unsubscribe or-talk in the body. http://archives.seul.org/or/talk/