Expand Minimize

MIB_UDPROW_OWNER_PID structure

The MIB_UDPROW_OWNER_PID structure contains an entry from the User Datagram Protocol (UDP) listener table for IPv4 on the local computer. The entry also includes the process ID (PID) that issued the call to the bind function for the UDP endpoint.

Syntax


typedef struct _MIB_UDPROW_OWNER_PID {
  DWORD dwLocalAddr;
  DWORD dwLocalPort;
  DWORD dwOwningPid;
} MIB_UDPROW_OWNER_PID, *PMIB_UDPROW_OWNER_PID;

Members

dwLocalAddr

The IPv4 address of the UDP endpoint on the local computer.

A value of zero indicates a UDP listener willing to accept datagrams for any IP interface associated with the local computer.

dwLocalPort

The port number of the UDP endpoint on the local computer. This member is stored in network byte order.

dwOwningPid

The PID of the process that issued the call to the bind function for the UDP endpoint. This member is set to 0 when the PID is unavailable.

Remarks

The MIB_UDPTABLE_OWNER_PID structure is returned by a call to GetExtendedUdpTable with the TableClass parameter set to UDP_TABLE_OWNER_PID and the ulAf parameter set to AF_INET. The MIB_UDPTABLE_OWNER_PID structure contains an array of MIB_UDPROW_OWNER_PID structures.

The dwLocalAddr member is stored as a DWORD in the same format as the in_addr structure. In order to use the dwLocalAddr member, the ntohl or inet_ntoa functions in Windows Sockets or similar functions may be needed. On Windows Vista and later, the RtlIpv4AddressToString or RtlIpv4AddressToStringEx functions may be used to convert the IPv4 address in the dwLocalAddr member to a string without loading the Windows Sockets DLL.

The dwLocalPort member is in network byte order. In order to use the dwLocalPort member, the ntohs or inet_ntoa functions in Windows Sockets or similar functions may be needed.

The MIB_UDPTABLE_OWNER_PID structure contains the UDP listener table for IPv4 on the local computer. The name is based on the definition of this table in RFC 1213 published by the IETF. For more information, see http://www.ietf.org/rfc/rfc1213.txt. This table contains UDP endpoints for IPv4 that have been bound to an address. It should be noted that an application can create a UDP socket and bind it to an address for the sole purpose of sending a UDP datagram, with no intention of receiving packets using this socket (functioning as a listener).

On the Microsoft Windows Software Development Kit (SDK) released for Windows Vista and later, the organization of header files has changed. This structure is defined in the Udpmib.h header file, not in the Iprtrmib.h header file. Note that the Udpmib.h header file is automatically included in Iprtrmib.h, which is automatically included in the Iphlpapi.h header file. The Udpmib.h and Iprtrmib.h header files should never be used directly.

Requirements

Minimum supported client

Windows Vista, Windows XP with SP2 [desktop apps only]

Minimum supported server

Windows Server 2008, Windows Server 2003 with SP1 [desktop apps only]

Header

Udpmib.h on Windows Server 2008 and Windows Vista (include Iphlpapi.h);
Iprtrmib.h on Windows Server 2003 with SP1 and Windows XP with SP2 (include Iphlpapi.h)

See also

bind
GetExtendedUdpTable
GetUdp6Table
GetUdpTable
in_addr
inet_ntoa
MIB_UDP6ROW_OWNER_PID
MIB_UDP6TABLE_OWNER_PID
MIB_UDPTABLE_OWNER_PID
ntohl
ntohs
RtlIpv4AddressToString
RtlIpv4AddressToStringEx

 

 

Community Additions

ADD
Show:
© 2014 Microsoft