This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug libc/160] if_nameindex has inconsistent behavior because of __opensock
- From: "joshk at triplehelix dot org" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 14 May 2004 01:19:29 -0000
- Subject: [Bug libc/160] if_nameindex has inconsistent behavior because of __opensock
- References: <20040513235527.160.joshk@triplehelix.org>
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
------- Additional Comments From joshk at triplehelix dot org 2004-05-14 01:19 -------
I think I leaped to that conclusion. My hasty logic was that a PF_INET socket fd
would only pick up interfaces set up with PF_INET, that is, IPv4, and PF_UNIX
would grab all interfaces.
I'll try to come up with a test program soon and see if I can force PF_UNIX to
be used on my 2.4 box, and see if it works. I'll basically need to copy the
nameindex/__opensock code out of glibc and customize it..
FWIW, the reason I reported this as a glibc bug was that
1) I was under the impression that the function was guaranteed to return _all_
network interfaces (cf.
http://www.opengroup.org/onlinepubs/009695399/functions/if_nameindex.html)
2) as such, glibc should take steps to ensure it works the same way on a variety
of system configurations.
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=160
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.