[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <03d43876-72c7-4b4f-93e1-944f0a04bc1d@email.android.com>
Date: Tue, 10 Jun 2014 07:49:48 +0800
From: orc <orc@...server.ru>
To: musl@...ts.openwall.com
Subject: Re: ipv6 scope id support
10 июня 2014 г. 2:53:37 KRAT, Rich Felker <dalias@...c.org> пишет:
>On Mon, Jun 09, 2014 at 10:35:39PM +0800, orc wrote:
>> Hi list!
>> Great to see major changes towards dns code cleanup and rewrite! Here
>another one:
>> As I understand, this is a feature when you can specify destination
>link-local address and from which interface packets are sent. The
>address and interface are both specified, being separated by '%' (for
>example, ff02::1%eth0)
>> I've grepped into glibc sources and found that this step is performed
>somewhere in dns resolver.
>>
>> Does musl support this? My current attempt to use it failed.
>
>Can you explain what you did that failed? getaddrinfo should always
>accept %nnnn (numeric scope_id) following a numeric address string,
>and accepts %ifname if the address has link-local scope (as determined
>by IN6_IS_ADDR_LINKLOCAL || IN6_IS_ADDR_MC_LINKLOCAL). Likewise,
>getnameinfo will reverse the scope_id to an interface name only fork
>link-local addresses, and the reversal can be inhibited with the
>NI_NUMERICSCOPE flag.
>
>For non-numeric addresses, scope_id is not parsed at all, but entries
>in /etc/hosts can have a scope_id attached to them.
>
>If any of this logic seems incorrect to you, please explain what you
>think should be changed.
Oh, I am sorry, false alert. I was using 1.0.0 at that time. It lacks this.
And the dns bug will motivate me to upgrade :-)
>
>Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
