Experimental Physics and
Industrial Control System

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:[email protected]
N:Dudley;David
END:VCARD

Replies:

RE: NetBSD: implementation of"osiSockDiscoverInterfaceAddresses()" Jeff Hill

Navigate by Date:

Prev: Re: VCCT and CA sniffer Chris Payne

Next: New Technology Alert: X-Ray-based Ultra-high Density Optical Memory (X-ROM) X-ROM, Inc.

Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <2006>  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 

Navigate by Thread:

Prev: Re: Any EPICS support for ICS 145? Ernest L. Williams Jr.

Next: RE: NetBSD: implementation of"osiSockDiscoverInterfaceAddresses()" Jeff Hill

Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <2006>  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024