Looking for some advice/a hint

[Brian J. Murrell]

Hi Ted (et. al).

I am pretty close with my OMAPI interface object implementation for the
client.  I have run into a snag and and not sure what it is.  I believe
I have fully implemented both "creating" and "removing" interfaces.  The
proper DHCP messages are sent when the interface is created and when it
is removed.  The "interface_info" object transitions from interfaces to
dummy_interfaces successfully, depending on whether the interface is up
(created) or not (removed).

The problem I seem to be having is that when I up and then down an
interface, all is OK, however if I try to up it again, even before any
DHCP messages are even sent out (DHCPREQUEST is what I am expecting) I
get the following error:

omapi_one_dispatch failed: unexpected error (Bad file descriptor) --
exiting.

(Note that I added the printing of errno string: "Bad file descriptor"
in the brackets to help me debug).

Any idea why a bad file descriptor might be getting included in one (or
more) of the fd_sets?  I noticed the sets are construced using "io"
objects.  I can imagine what they are, but have not delved into what
they actually do.  I was hoping not to have to.  :-)

Any ideas at all would help
Thanx,
b.

P.S.  In having gotten this far, I am suspecting that complimentary
routines for if_register_{send, receive} to remove the sending and
listening mechanisms is needed.  Would I be right about that or am I
missing something?


--
Brian J. Murrell                              InterLinx Support Services, Inc.
North Vancouver, B.C.                                             604 983 UNIX
        Platform and Brand Independent UNIX Support - R3.2 - R4 - BSD