Glenn Skinner wrote: > Date: Fri, 28 Mar 2008 14:49:56 -0700 > From: Darren Reed <Darren.Reed at sun.com> > Subject: Re: PSARC/2008/219 Committed API for packet interception > > ... > I've updated the spec, to include the above and the other > corrections. > > ... > IPFilter hook naming > -------------------- > For applications that wish to insert hooks before or after IPFilter > in the packet stack, the names used by IPFilter are provided as an > uncommitted interface: > > +------------------+--------------------------+----------------+ > | Packet Hook | IPFilter Hook Name | Classification | > +------------------+--------------------------+----------------+ > | NH_PHYSICAL_IN | "ipfilter_hook_in" | Uncommitted | > | NH_PHYSICAL_OUT | "ipfilter_hook_out" | Uncommitted | > | NH_LOOPBACK_IN | "ipfilter_hook_loop_in" | Uncommitted | > | NH_LOOPBACK_OUT | "ipfilter_hook_loop_out" | Uncommitted | > +------------------+--------------------------+----------------+ > >Does this case specify whether IPFilter supplies ordering hints when >establishing its hooks? If so, what are they? (This would seem to be >useful information for the applications alluded to above to know.) > >
As IPfilter does not make use of the ordering hints, there was nothing to mention...well, I suppose I should have mentioned that it doesn't use them. Darren
