| Previous | Next |
| STATUS_FWP_NOTIFICATION_DROPPED | STATUS_FWP_INCOMPATIBLE_SA_STATE |
STATUS_FWP_TRAFFIC_MISMATCH
The IPsec SA context was addressed with different traffic identity
STATUS_FWP_TRAFFIC_MISMATCH belongs to WFP IPsec security-association context handling. It is not a generic packet mismatch: repeated calls to IPsecSaContextGetSpi0 must use the same IPSEC_TRAFFIC0 parameters for the context. Supplying different traffic data creates an inconsistent request for that SA context.
Compare the entire traffic structure as supplied by the caller, not only a visible address or port. Record the context ID, serialized traffic fields, IP version, and direction assumptions at each call site. Creating another context to suppress the error can duplicate security policy rather than repair the incorrect lookup.
What to compare
- The SA context ID and every
IPSEC_TRAFFIC0field used in the first and later calls. - The call order and ownership of the context.
- Whether address normalization or IPv4/IPv6 representation changed between calls.
- The intended association rather than an unrelated IPsec tunnel or firewall filter.
References
- Microsoft: FWP_E_TRAFFIC_MISMATCH
- Microsoft: WFP provider contexts and IPsec policy
- Microsoft: WFP management functions
Looking for a different code? Search another status or error code.