大网数据广告活动
启动与系统组件

Failed to redirect connected UDP traffic

· 52CE 我爱测

This article provides workarounds for the redirection failure problem that occurs when the connected UDP traffic is redirected to a local proxy using a WFP callout driver.

Applies to:   Windows Driver Kit 10

Symptoms

Consider the following scenario:

  • A local process sends User Datagram Protocol (UDP) packets by using the Windows Sockets (Winsock) API.
  • An application Layer Enforcement (ALE) callout driver was developed using Windows Filtering Platform (WFP), which redirects traffic from the local process.
  • A local proxy service receives the UDP packets that are redirected by the callout driver.

In this scenario, if the local process uses the connect and send functions to send UDP packets through a connected UDP protocol, the packets are dropped and the redirection to the local proxy service fails.

Cause

The issue occurs because the WFP redirect records are referenced incorrectly.

Workaround

To redirect traffic successfully to the local proxy service, use the sendto function to send UDP packets through a connectionless UDP protocol.

More information

To learn how to enable application layer enforcement (ALE) callout drivers to inspect and redirect connections, see Using Bind or Connect Redirection.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors (upstream author metadata: aartig13). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
See source applicability · Source date 04/20/2021
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。