PFN_WSK_GET_LOCAL_ADDRESS - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// wsk.h
PFN_WSK_GET_LOCAL_ADDRESS PfnWskGetLocalAddress;
NTSTATUS PfnWskGetLocalAddress(
[in] PWSK_SOCKET Socket,
[out] PSOCKADDR LocalAddress,
[in, out] PIRP Irp
)
{...}
View the official Windows Driver Kit DDI referenceNo description available.
The WskGetLocalAddress function retrieves the local transport address of a socket.
Socket [in]A pointer to a WSK_SOCKET structure that specifies the socket object for the socket that is being queried.
LocalAddress [out]A pointer to a caller-allocated buffer that receives the local transport address for the socket. The buffer must be located in non-paged memory. The buffer must also be large enough to contain the specific SOCKADDR structure type that corresponds to the address family that the WSK application specified when it created the socket.
For a connection-oriented socket that the WSK application accepted on a listening socket, the address family is the same as the address family that the WSK application specified when it created the listening socket.
Irp [in, out]A pointer to a caller-allocated IRP that the WSK subsystem uses to complete the retrieve operation asynchronously. For more information about using IRPs with WSK functions, see Using IRPs with Winsock Kernel Functions.
WskGetLocalAddress returns one of the following NTSTATUS codes:
| Return code | Description |
|---|---|
| STATUS_SUCCESS | The local transport address for the socket was successfully retrieved. The IRP will be completed with success status. |
| STATUS_PENDING | The WSK subsystem could not retrieve the local transport address for the socket immediately. The WSK subsystem will complete the IRP after it has retrieved the local transport address for the socket. The status of the retrieve operation will be returned in the IoStatus.Status field of the IRP. |
| STATUS_INVALID_DEVICE_STATE | The socket is not bound to a local transport address. The IRP will be completed with failure status. |
| STATUS_FILE_FORCED_CLOSED | The socket is no longer functional. The IRP will be completed with failure status. The WSK application must call the WskCloseSocket function to close the socket as soon as possible. |
| Other status codes | An error occurred. The IRP will be completed with failure status. |
A WSK application can call the WskGetLocalAddress function only on a socket that has been bound to a local transport address.
A listening, datagram, or stream socket is bound to a local transport address when the WSK application calls the WskBind function.
A connection-oriented socket is bound to a local transport address in one of the following ways:
The WskGetLocalAddress function is particularly useful for determining the specific local transport address that was assigned to a socket by the transport protocol when the socket was bound to the local wildcard address. For a connection-oriented socket that was bound to the local wildcard address, the local transport address might not be assigned to the socket by the transport protocol until the socket is connected to a remote transport address. The step where the local transport address is assigned to the socket is transport protocol-dependent. For TCP, the port number is assigned when a connection-oriented socket is bound, but the IP address is not assigned until the socket is connected.
If the WskGetLocalAddress function returns STATUS_PENDING, the buffer that is pointed to by the LocalAddress parameter must remain valid until the IRP is completed. If the WSK application allocated the buffer with one of the ExAllocate*Xxx* functions, it cannot free the memory with the corresponding ExFree*Xxx* function until after the IRP is completed. If the WSK application allocated the buffer on the stack, it cannot return from the function that calls the WskGetLocalAddress function until after the IRP is completed.
WSK_PROVIDER_CONNECTION_DISPATCH
WSK_PROVIDER_DATAGRAM_DISPATCH