From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Request for reports on ipv6 issues
Date: Sun, 30 Sep 2012 12:57:18 -0400 [thread overview]
Message-ID: <20120930165718.GA3043@brightrain.aerifal.cx> (raw)
One area I've been meaning to address for a while is the quality and
completeness of ipv6 support in musl. I've never used ipv6 seriously
so while I can read the specification for how the interfaces are
supposed to behave, I don't have any good intuition beyond that.
I know AI_ADDRCONF is not supported, and should be. I also know glibc
has experienced a lot of bugs with it not behaving as expected, so
this one probably requires some attention to the details.
Apparently ipv6 has some sort of "scope" which I don't understand, and
which I don't think we handle now.
The AI_V4MAPPED and AI_ALL flags are not supported at all yet, but
they seem pretty straightforward.
Anything else?
Rich
next reply other threads:[~2012-09-30 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-30 16:57 Rich Felker [this message]
2012-09-30 19:05 ` Rich Felker
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=20120930165718.GA3043@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--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).