Skip to content

RPC OpNum conditions not displayed properly #13

@MichaelGrafnetter

Description

@MichaelGrafnetter

Opnum condition IDs are currently not translated to their names:
Image

This is how the filter looks like in netsh:

filterKey: f62d016e-f5db-48df-b94f-472fe10f6553
displayData.name: RPCFilter
displayData.description: RPC Filter
filterId: 0x1a747
layerKey: um
weight: Type: FWP_EMPTY Value: Empty
action.type: block
numFilterConditions: 2

filterCondition[0]
        fieldKey: if_uuid
        matchType: FWP_MATCH_EQUAL
        conditionValue: Type: FWP_BYTE_ARRAY16_TYPE Value: df1941c5 4e79fe89 364610bf 4df4ac57

filterCondition[1]
        fieldKey: opnum
        matchType: FWP_MATCH_EQUAL
        conditionValue: Type: FWP_UINT16 Value: 4

The interface UUID could also be displayed as df1941c5-fe89-4e79-bf10-463657acf44d.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions