NetBSD: implementation of "osiSockDiscoverInterfaceAddresses()"

["David Dudley" <daviddu@cctexas.com>]

OK, looks like to a large degree, this is the source of most of the remaining problems on the NetBSD port (at least... most likely culprit).

Looking at the situation, I can see that there's going to be a problem, from using "ioctl(socket, SIOCGIFCONF &ifconf)" inside the code.  On NetBSD, this function returns information that is "inconsistent" with Linux, I believe.

Could someone please give me a rundown on how this function is expected to work?  If it does what I believe it appears to do, I think I can replace it with an equivalent function using "getifaddrs", and possibly make it a little more general at the same time.  I believe all this function is attempting to do is build up a list of interfaces that exist on the machine, that have access to the outside.  If so, I'll code a replacement, and get it functioning.  The problem is, that in NetBSD, ifreq blocks are not necessarily (and probably not) stored in sequential memory blocks, but can/may/are spread across the kernel address space. 

David Dudley

BEGIN:VCARD
VERSION:2.1
X-GWTYPE:USER
FN:David Dudley
TEL;WORK:880-3740
ORG:;MIS
TEL;PREF;FAX:880-3741
EMAIL;WORK;PREF;NGW:DavidDu@cctexas.com
N:Dudley;David
END:VCARD