| UID | title | description | helpviewer_keywords | old-location | tech.root | ms.assetid | ms.date | ms.keywords | req.header | req.include-header | req.target-type | req.target-min-winverclnt | req.target-min-winversvr | req.kmdf-ver | req.umdf-ver | req.ddi-compliance | req.unicode-ansi | req.idl | req.max-support | req.namespace | req.assembly | req.type-library | req.lib | req.dll | req.irql | targetos | req.typenames | req.redist | ms.custom | f1_keywords | dev_langs | topic_type | api_type | api_location | api_name | |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NS:udpmib._MIB_UDPROW |
MIB_UDPROW (udpmib.h) |
Contains an entry from the User Datagram Protocol (UDP) listener table for IPv4 on the local computer. |
|
mib\mib_udprow.htm |
MIB |
db366802-962f-4e83-838e-1e2f51beab92 |
12/05/2018 |
*PMIB_UDPROW, MIB_UDPROW, MIB_UDPROW structure [MIB], PMIB_UDPROW, PMIB_UDPROW structure pointer [MIB], _mpr_mib_udprow, iprtrmib/MIB_UDPROW, iprtrmib/PMIB_UDPROW, mib.mib_udprow, rras.mib_udprow, udpmib/MIB_UDPROW, udpmib/PMIB_UDPROW |
udpmib.h |
Iphlpapi.h |
Windows |
Windows 2000 Professional [desktop apps only] |
Windows 2000 Server [desktop apps only] |
Windows |
MIB_UDPROW, *PMIB_UDPROW |
19H1 |
|
|
|
|
|
|
The MIB_UDPROW structure contains an entry from the User Datagram Protocol (UDP) listener table for IPv4 on the local computer.
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.
The port number of the UDP endpoint on the local computer. This member is stored in network byte order.
The GetUdpTable function retrieves the IPv4 UDP listener table on the local computer and returns this information in a MIB_UDPTABLE structure.
An array of MIB_UDPROW structures are contained in the MIB_UDPTABLE structure.
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 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.