From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: ipv6 scope id support
Date: Mon, 9 Jun 2014 14:53:37 -0400 [thread overview]
Message-ID: <20140609185337.GJ179@brightrain.aerifal.cx> (raw)
In-Reply-To: <accbace9-9f7e-4bb5-bbcd-f7b6444b724e@email.android.com>
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.
Rich
next prev parent reply other threads:[~2014-06-09 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 14:35 orc
2014-06-09 18:53 ` Rich Felker [this message]
2014-06-09 23:49 ` orc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140609185337.GJ179@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).