FWPS_CALLOUT_NOTIFY_FN3 callback function (fwpsu.h)

Version 3 of the function invoked during classification when a callout filter matches. The difference being that this callback returns an FWPS_FILTER3 structure.

Syntax

FWPS_CALLOUT_NOTIFY_FN3 FwpsCalloutNotifyFn3;

NTSTATUS FwpsCalloutNotifyFn3(
  FWPS_CALLOUT_NOTIFY_TYPE notifyType,
  const GUID *filterKey,
  FWPS_FILTER3 *filter
)
{...}

Parameters

notifyType

A value that indicates the type of notification that the filter engine is sending to the callout. Valid values for this parameter are:

FWPS_CALLOUT_NOTIFY_ADD_FILTER. A filter is being added to the filter engine that specifies the callout for the filter's action.

FWPS_CALLOUT_NOTIFY_DELETE_FILTER. A filter is being deleted from the filter engine that specifies the callout for the filter's action.

FWPS_CALLOUT_NOTIFY_TYPE_MAX. A maximum value for testing purposes.

filterKey

A pointer to the management identifier for the filter, as specified by the application or driver that is adding or deleting the filter. Must be NULL if the notifyType parameter is set to FWPS_CALLOUT_NOTIFY_DELETE_FILTER. For more information, see Remarks.

filter

A pointer to an FWPS_FILTER3 structure. This structure describes the filter that is being added to or deleted from the filter engine.

A callout's notifyFn3 callout function can set the context member of this structure to point to a callout driver-supplied context structure when the filter is added to the filter engine. This context structure is opaque to the filter engine, and can be used by the callout driver's classifyFn3 callout function to preserve any driver-specific data or state information between calls by the filter engine to the callout driver's classifyFn3 callout function.

A callout's notifyFn3 callout function can clean up any context associated with the filter when the filter is deleted from the filter engine.

Return value

A callout's notifyFn3 function returns one of the following NTSTATUS codes.

Remarks

A callout driver registers a callout's callout functions with the filter engine by calling the FwpsCalloutRegister2 function.

The filter engine calls a callout's notifyFn3 callout function to notify the callout driver about events that are associated with the callout. If the callout driver's notifyFn3 callout function does not recognize the type of notification that is passed in the notifyType parameter, it ignores the notification and return STATUS_SUCCESS.

If a callout driver registers a callout with the filter engine after filters that specify the callout for the filter's action have already been added to the filter engine, the filter engine does not call the callout driver's notifyFn3 callout function to notify the callout about any of the existing filters. The filter engine calls the callout driver's notifyFn3 callout function to notify the callout when new filters that specify the callout for the filter's action are added to the filter engine. In this situation, a callout's notifyFn3 callout function might not get called for every filter in the filter engine that specifies the callout for the filter's action. If a callout driver registers a callout after the filter engine is started and the callout needs to know about every filter in the filter engine that specifies the callout for the filter's action, the callout driver must call the appropriate management functions to enumerate all the filters in the filter engine and sort through the resulting list of filters to find those that specify the callout for the filter's action. See Calling other Windows Filtering Platform functions for more information about calling these functions.

When a filter that specifies a callout for the filter's action is deleted from the filter engine, the filter engine calls the callout driver's notifyFn3 callout function and passes FWP_CALLOUT_NOTIFY_DELETE_FILTER in the notifyType parameter and NULL in the filterKey parameter. For more information, see Processing notify callouts.

Requirements