SIO_QUERY_WFP_CONNECTION_REDIRECT_RECORDS control code
The SIO_QUERY_WFP_CONNECTION_REDIRECT_RECORDS control code retrieves the redirect record for the accepted TCP/IP connection for use by a Windows Filtering Platform (WFP) redirect service.
int WSAIoctl( (socket) s, // descriptor identifying a socket SIO_QUERY_WFP_CONNECTION_REDIRECT_RECORDS, // dwIoControlCode NULL, // lpvInBuffer 0, // cbInBuffer (LPVOID) lpvOutBuffer, // output buffer (DWORD) cbOutBuffer, // size of output buffer (LPDWORD) lpcbBytesReturned, // number of bytes returned (LPWSAOVERLAPPED) lpOverlapped, // OVERLAPPED structure (LPWSAOVERLAPPED_COMPLETION_ROUTINE) lpCompletionRoutine, // completion routine );
int WSPIoctl( (socket) s, // descriptor identifying a socket SIO_QUERY_WFP_CONNECTION_REDIRECT_RECORDS, // dwIoControlCode NULL, // lpvInBuffer 0, // cbInBuffer (LPVOID) lpvOutBuffer, // output buffer (DWORD) cbOutBuffer, // size of output buffer (LPDWORD) lpcbBytesReturned, // number of bytes returned (LPWSAOVERLAPPED) lpOverlapped, // OVERLAPPED structure (LPWSAOVERLAPPED_COMPLETION_ROUTINE) lpCompletionRoutine, // completion routine (LPWSATHREADID) lpThreadId, // a WSATHREADID structure (LPINT) lpErrno // a pointer to the error code. );
A descriptor identifying a socket.
The control code for the operation. Use SIO_QUERY_WFP_CONNECTION_REDIRECT_RECORDS for this operation.
A pointer to the input buffer. This parameter is unused for this operation.
The size, in bytes, of the input buffer. This parameter is unused for this operation.
A pointer to the output buffer. This parameter should point to a ULONG data type if the lpOverlapped and lpCompletionRoutine parameters are NULL.
The size, in bytes, of the output buffer. This parameter must be at least the size of a ULONG data type.
A pointer to a variable that receives the size, in bytes, of the data stored in the output buffer.
If lpOverlapped is NULL, the DWORD value pointed to by the lpcbBytesReturned parameter that is returned on a successful call cannot be zero.
If the lpOverlapped parameter is not NULL for overlapped sockets, operations that cannot be completed immediately will be initiated, and completion will be indicated at a later time. The DWORD value pointed to by the lpcbBytesReturned parameter that is returned may be zero since the size of the data stored can't be determined until the overlapped operation has completed. The final completion status can be retrieved when the appropriate completion method is signaled when the operation has completed.
A pointer to a WSAOVERLAPPED structure.
If socket s was created without the overlapped attribute, the lpOverlapped parameter is ignored.
If s was opened with the overlapped attribute and the lpOverlapped parameter is not NULL, the operation is performed as an overlapped (asynchronous) operation. In this case, lpOverlapped parameter must point to a valid WSAOVERLAPPED structure.
For overlapped sockets, operations that cannot be completed immediately will be initiated, and completion will be indicated at a later time. The WSAIoctl or WSPIoctl function returns immediately, and the appropriate completion method is signaled when the operation has been completed.
Otherwise, the function does not return until the operation has been completed or an error occurs.
A pointer to the completion routine called when the operation has been completed (ignored for non-overlapped sockets).
A pointer to a WSATHREADID structure to be used by the provider in a subsequent call to WPUQueueApc. The provider should store the referenced WSATHREADID structure (not the pointer to same) until after the WPUQueueApc function returns.
Note This parameter applies only to the WSPIoctl function.
A pointer to the error code.
Note This parameter applies only to the WSPIoctl function.
The data area passed to a system call is too small. This error is returned if the buffer pointed to by the lpvOutBuffer parameter with a buffer size passed in the cbOutBuffer parameter is too small. The buffer size required will be returned in the lpcbBytesReturned parameter.
An overlapped operation was successfully initiated and completion will be indicated at a later time.
An overlapped operation was canceled due to the closure of the socket or the execution of the SIO_FLUSH IOCTL command.
The lpvOutBuffer, lpcbBytesReturned, lpOverlapped, or lpCompletionRoutine parameter is not totally contained in a valid part of the user address space.
The function is invoked when a callback is in progress.
A blocking operation was interrupted.
The dwIoControlCode parameter is not a valid command, or a specified input parameter is not acceptable, or the command is not applicable to the type of socket specified. This error is returned if the cbOutBuffer parameter is less than the size of a ULONG data type.
The network subsystem has failed.
The socket option is not supported on the specified protocol.
The socket s is not connected.
The descriptor s is not a socket.
The specified IOCTL command is not supported. This error is returned if the SIO_QUERY_WFP_CONNECTION_REDIRECT_RECORDS IOCTL is not supported by the transport provider.
The SIO_QUERY_WFP_CONNECTION_REDIRECT_RECORDS IOCTL is supported on Windows 8, and Windows Server 2012, and later versions of the operating system.
WFP allows access to the TCP/IP packet processing path, wherein outgoing and incoming packets can be examined or changed before allowing them to be processed further. By tapping into the TCP/IP processing path, independent software vendors (ISVs) can more easily create firewalls, antivirus software, diagnostic software, and other types of applications and services. WFP provides user-mode and kernel-mode components so that third-party ISVs can participate in the filtering decisions that take place at several layers in the TCP/IP protocol stack and throughout the operating system. The WFP connection redirect feature allows a WFP callout kernel driver to redirect a connection locally to a user-mode process, perform content inspection in user-mode, and forward the inspected content using a different connection to the original destination.
The SIO_QUERY_WFP_CONNECTION_REDIRECT_RECORDS IOCTL and several other related IOCTLS are user-mode components used to allow multiple WFP-based connection proxy applications to inspect the same traffic flow in a cooperative manner. Each inspection agent can safely re-inspect network traffic that has already been inspected by another inspection agent. With the presence of multiple proxies (developed by different ISVs, for example) the connection used by one proxy to communicate with the final destination could in turn be redirected by a second proxy, and that new connection could again be redirected by the original proxy. Without connection tracking, the original connection might never reach its final destination as it gets stuck in an infinite proxy loop.
The SIO_QUERY_WFP_CONNECTION_REDIRECT_RECORDS IOCTL is used to provide proxied connection tracking on redirected socket connections. This WFP feature facilitates tracking of redirection records from the initial redirect of a connection to the final connection to the destination.
The SIO_QUERY_WFP_CONNECTION_REDIRECT_RECORDS IOCTL is used by a WFP-based redirect service to retrieve the redirect record from the accepted TCP/IP packet connection (the connected socket for a TCP socket or a UDP socket, for example) redirected to it by its companion kernel-mode callout registered at ALE_CONNECT_REDIRECT layers in a kernel-mode driver. The SIO_QUERY_WFP_CONNECTION_REDIRECT_CONTEXT IOCTL is used by a WFP-based redirect service to retrieve the redirect context for a redirect record from the accepted TCP/IP packet connection (the connected socket for a TCP socket or a UDP socket, for example) redirected to it by its companion callout registered at ALE_CONNECT_REDIRECT layers. The redirect context is an optional driver-allocated context used if the current redirection state of a connection is that the connection was redirected by the calling redirect service or the connection was previously redirected by the calling redirect service but later redirected again by a different redirect service. For a TCP proxy connnection, the redirect service transfers the retrieved redirect record to the TCP socket it uses to proxy the original content using the SIO_SET_WFP_CONNECTION_REDIRECT_RECORDS IOCTL.
When the redirect service is redirecting a non-TCP socket (UDP, for example), the redirect records returned by the SIO_QUERY_WFP_CONNECTION_REDIRECT_RECORDS IOCTL indicate this to the redirect service using the WSAMSG structure used with the WSARecvMsg function. The Control member of the WSAMSG structure would have a cmsg_type in the WSACMSGHDR structure set to IP_CONNECTION_REDIRECT_RECORD. The WSARecvMsg parameter must be supplied by the redirect service when accepting non-TCP redirects.
Note that for non-TCP traffic, only the flow-creating packet will carry the IP_CONNECTION_REDIRECT_RECORD. As a result, only the first proxied packet needs to include this information using the WSARecvMsg function.
Since the WFP redirect record is a variable length data blob, the caller can either supply a large output buffer (a 1,024 byte buffer pointed to by the lpvOutBuffer parameter, for example) or can pass an output buffer size in the cbOutBuffer parameter of 0 to query the buffer size required to hold the returned blob. If the output buffer size is not sufficient to the hold the data, the WSAIoctl or WSPIoctl functions will return ERROR_INSUFFICIENT_BUFFER and the required buffer size will be returned in value pointed to by the lpcbBytesReturned parameter.
The application calling the SIO_QUERY_WFP_CONNECTION_REDIRECT_CONTEXT does not need to understand the blob containing the redirect context retrieved. This is an opaque blob of data that the application needs to retrieve and pass back to the new socket.
Minimum supported client
Windows 8 [desktop apps only]
Minimum supported server
Windows Server 2012 [desktop apps only]