public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "psimerda at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug network/12398] AI_ADDRCONFIG breaks getaddrinfo() calls for loopback names and addresses Date: Tue, 20 Nov 2012 23:33:00 -0000 [thread overview] Message-ID: <bug-12398-131-aWW6dk7BLc@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-12398-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=12398 --- Comment #5 from Pavel Šimerda <psimerda at redhat dot com> 2012-11-20 23:32:57 UTC --- Changed the comment. Currently, I'm using the following patch to fix my node-local IPv4/IPv6 networking (link-local networking is currently not broken in Fedora since they removed the patch to also disregard link-local addresses). I'm proposing this patch as a temporary solution until this s fixed properly with the following notes: * It breaks POSIX1-2008 (which requires checking for any IPv4/IPv6 address) * It breaks informational RFC 3493 (which requires the same but disregards the loopback interface) * It ignores the older informational RFC 2553 (which requires the same as RFC 3494 but only for DNS lookups) The POSIX1-2008, RFC 3493 and obsolete RFC 2553 are all effectively useless but the obsolete one is closest to the truth. Whether a global IPv4 address, a global IPv4 route, or a global IPv4 default gateway is the right sign of global connectivity, is up to discussion. I also changed the description of the bug to reflect the actual problem, not one possible (maybe wrong, but at least POSIX-compliant) solution of that problem. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-11-20 23:33 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-13 20:03 [Bug libc/12398] New: loopback addresses shouldn't be disregarded by getaddrinfo()+AI_ADDRCONFIG when looking up "localhost" tore at fud dot no 2011-07-16 5:36 ` [Bug libc/12398] " nick.jones@network-box.com 2012-02-21 2:07 ` [Bug network/12398] " jsm28 at gcc dot gnu.org 2012-07-27 14:11 ` psimerda at redhat dot com 2012-07-28 10:13 ` psimerda at redhat dot com 2012-08-01 23:16 ` orion at cora dot nwra.com 2012-09-22 15:43 ` psimerda at redhat dot com 2012-11-20 23:13 ` [Bug network/12398] AI_ADDRCONFIG breaks getaddrinfo() calls for loopback names and addresses psimerda at redhat dot com 2012-11-20 23:33 ` psimerda at redhat dot com [this message] 2012-11-20 23:37 ` psimerda at redhat dot com 2012-11-20 23:39 ` psimerda at redhat dot com 2012-12-06 7:04 ` gaofeng at cn dot fujitsu.com 2012-12-16 13:47 ` tore at fud dot no 2012-12-16 15:53 ` [Bug network/12398] getaddrinfo("127.0.0.1") and/or getaddrinfo("::1) may fail with AI_ADDRCONFIG psimerda at redhat dot com 2012-12-17 17:30 ` psimerda at redhat dot com 2012-12-18 14:34 ` psimerda at redhat dot com 2013-02-09 17:54 ` phattanon at nettree dot co.th 2013-02-09 21:11 ` psimerda at redhat dot com 2013-02-24 22:12 ` psimerda at redhat dot com 2013-10-20 20:49 ` neleai at seznam dot cz 2013-10-22 10:04 ` psimerda at redhat dot com 2014-02-16 17:47 ` jackie.rosen at hushmail dot com 2014-05-28 19:45 ` schwab at sourceware dot org 2014-06-27 12:29 ` 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=bug-12398-131-aWW6dk7BLc@http.sourceware.org/bugzilla/ \ --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).