From: Philip Blundell <Philip.Blundell@pobox.com>
To: libc-hacker@sourceware.cygnus.com
Subject: nscd and IPv6
Date: Tue, 11 Jan 2000 12:02:00 -0000 [thread overview]
Message-ID: <E1286Yg-0006zu-00@kings-cross.london.uk.eu.org> (raw)
I think this code in nscd/hstcache.c is bogus:
/* And the generated IPv6 addresses if necessary. */
if (hst->h_length == INADDRSZ)
{
/* Generate the IPv6 addresses. */
for (cnt = 0; cnt < h_addr_list_cnt; cp += IN6ADDRSZ, ++cnt)
map_v4v6_address (hst->h_addr_list[cnt], cp);
}
IMHO, the NSS code should not be automatically mapping IPv4 addresses to IPv6,
and it should certainly not be happening in nscd. If a program wants both
IPv4 and IPv6 addresses it should pass PF_UNSPEC to getaddrinfo().
The current nscd behaviour is confusing to users (judging by the current
thread on libc-alpha and recent discussion elsewhere) and unhelpful on
IPv6-only hosts where a v4-mapped address is no use.
Does anybody object to deleting this code?
Thanks
p.
next reply other threads:[~2000-01-11 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-11 12:02 Philip Blundell [this message]
2000-01-11 12:44 ` Thorsten Kukuk
2000-01-11 12:59 ` Philip Blundell
[not found] <phil@kings-cross.london.uk.eu.org>
2000-01-11 13:02 ` Philip Blundell
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=E1286Yg-0006zu-00@kings-cross.london.uk.eu.org \
--to=philip.blundell@pobox.com \
--cc=libc-hacker@sourceware.cygnus.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).