[tor-bugs] #33056 [Core Tor/Tor]: Tor relays fail to understand /etc/resolv.conf ipv6 lines with % in them

[Tor Bug Tracker & Wiki]

#33056: Tor relays fail to understand /etc/resolv.conf ipv6 lines with % in them
--------------------------+------------------------
 Reporter:  arma          |          Owner:  (none)
     Type:  defect        |         Status:  new
 Priority:  Medium        |      Milestone:
Component:  Core Tor/Tor  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:  ipv6          |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------
Description changed by arma:

Old description:

> We had a relay operator on irc just now who has this line in their
> /etc/resolv.conf:
> {{{
> nameserver fe80::7e2ebdff:fe99:4cb9%enp2s0
> }}}
>
> Apparently this is a totally normal thing: the % indicates a link local
> name server.
>
> Two more hints that % is a standard thing:
> * https://bugs.launchpad.net/ubuntu/+source/wide-dhcpv6/+bug/1620221 "The
> link local name servers should be suffixed with the scope, e.g. "%eth0"."
> * https://tools.ietf.org/html/rfc4007#section-11 "to specify an IPv6 non-
> global address without ambiguity, an intended scope zone should be
> specified as well."
>
> Tor is unable to handle this % syntax in a resolv.conf line:
> {{{
> Jan 25 17:03:00.171 [warn] eventdns: Unable to parse nameserver address
> fe80::7e2ebdff:fe99:4cb9%enp2s0
> }}}
>
> It's not as bad as it could be, because Tor skips that line and uses
> whatever other lines there are. But (a) maybe we're not doing as well as
> we can do, and (b) maybe there are situations where that's the only
> configured nameserver and everything works on the host except Tor
> doesn't.
>
> I think technically this might be a libevent bug (aka missing feature),
> since it's libevent's evdns_base_nameserver_ip_add() which calls
> evutil_parse_sockaddr_port() which helpfully explains that
> {{{
>         /* recognized formats are:
>          * [ipv6]:port
>          * ipv6
>          * [ipv6]
>          * ipv4:port
>          * ipv4
>          */
> }}}
> none of which are the % syntax. But I will file it here a Tor ticket,
> since it's a Tor bug too, and then we can figure out where best to fix
> it.

New description:

 We had a relay operator on irc just now who has this line in their
 /etc/resolv.conf:
 {{{
 nameserver fe80::7e2ebdff:fe99:4cb9%enp2s0
 }}}

 Apparently this is a totally normal thing: the % indicates a link local
 name server.

 Two more hints that % is a standard thing:
 * https://bugs.launchpad.net/ubuntu/+source/wide-dhcpv6/+bug/1620221 "The
 link local name servers should be suffixed with the scope, e.g. "%eth0"."
 * https://tools.ietf.org/html/rfc4007#section-11 "to specify an IPv6 non-
 global address without ambiguity, an intended scope zone should be
 specified as well."

 Tor is unable to handle this % syntax in a resolv.conf line:
 {{{
 Jan 25 17:03:00.171 [warn] eventdns: Unable to parse nameserver address
 fe80::7e2ebdff:fe99:4cb9%enp2s0
 }}}

 It's not as bad as it could be, because Tor skips that line and uses
 whatever other lines there are. But (a) maybe we're not doing as well as
 we can do, and (b) maybe there are situations where that's the only
 configured nameserver and everything works on the host except Tor doesn't.

 I think technically this might be a libevent bug (aka missing feature),
 since it's libevent's evdns_base_nameserver_ip_add() which calls
 evutil_parse_sockaddr_port() which helpfully explains that
 {{{
         /* recognized formats are:
          * [ipv6]:port
          * ipv6
          * [ipv6]
          * ipv4:port
          * ipv4
          */
 }}}
 none of which are the % syntax. But I will file it here as a Tor ticket,
 since it's a Tor bug too, and then we can figure out where best to fix it.

--

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33056#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online