public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pasky at suse dot cz" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/10083] IPV6 getaddrinfo and AI_ADDRCONFIG Date: Tue, 21 Apr 2009 20:02:00 -0000 [thread overview] Message-ID: <20090421200235.12696.qmail@sourceware.org> (raw) In-Reply-To: <20090419085937.10083.spam@messir.net> ------- Additional Comments From pasky at suse dot cz 2009-04-21 20:02 ------- Then this is precisely the expected behaviour! RFC 3493 states: If the AI_ADDRCONFIG flag is specified, IPv4 addresses shall be returned only if an IPv4 address is configured on the local system, and IPv6 addresses shall be returned only if an IPv6 address is configured on the local system. The loopback address is not considered for this case as valid as a configured address. The idea is that AI_ADDRCONFIG shall be used if you want to use the given address family only when the user has explicit connectivity with that family. glibc was actually buggy before and did what you want, but this got fixed, see bug 4599. -- What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |WONTFIX http://sourceware.org/bugzilla/show_bug.cgi?id=10083 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2009-04-21 20:02 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-19 8:59 [Bug libc/10083] New: " spam at messir dot net 2009-04-19 20:59 ` [Bug libc/10083] " pasky at suse dot cz 2009-04-20 9:09 ` spam at messir dot net 2009-04-20 22:08 ` pasky at suse dot cz 2009-04-21 11:51 ` spam at messir dot net 2009-04-21 20:02 ` pasky at suse dot cz [this message] [not found] <bug-10083-131@http.sourceware.org/bugzilla/> 2014-07-01 7:07 ` fweimer at redhat dot com
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=20090421200235.12696.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.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: linkBe 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).