Opened 9 years ago

Closed 9 years ago

Last modified 8 years ago

#2574 closed defect (fixed)

eventdns complains about IPv6 nameserver in resolv.conf

Reported by: swsnyder Owned by:
Priority: High Milestone: Tor: 0.2.2.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: tor-relay
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


On my IPv6-enabled network I have these lines in /etc/resolv.conf:

nameserver ::1

These entries to my own running name server. At start-up tor logs this line:

[warn] eventdns: Unable to add nameserver ::1: error 2

I understand that IPv6 routing is not in place yet, but shouldn't Tor be OK with using a local IPv6 interface for name resolution?

This is with Tor v2.1.29, a version that is shown in the Version drop-down list below.

Child Tickets

Change History (8)

comment:1 Changed 9 years ago by swsnyder

a version that is shown in the Version

Should be "that is NOT shown in the Version". Sigh. The most recent v2.1.x version listed is 2.1.26.

comment:2 Changed 9 years ago by nickm

Milestone: Tor: 0.2.2.x-final

comment:3 Changed 9 years ago by nickm

Actually, have you tried any of the 0.2.2.x releases? Those are supposed to add support for IPv6 nameservers.

comment:4 Changed 9 years ago by nickm

Priority: normalmajor
Status: newneeds_review

Okay, tried it out: it turns out we had a "socket(PF_INET,...)" that should have been "socket(sa->sa_family,...)". See branch bug2574 in my public repository.

This is a bugfix on 0.2.1; maybe we _should_ apply it there.

comment:5 Changed 9 years ago by Sebastian

looks fine. I think we can get away with calling this a new feature.

comment:6 Changed 9 years ago by nickm

Resolution: fixed
Status: needs_reviewclosed

Well, it's a feature we have claimed to have before. So IMO it's a bugfix. :)

merging to 0.2.1 and later . Thanks!

comment:7 Changed 8 years ago by nickm

Keywords: tor-relay added

comment:8 Changed 8 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.