UID | title | ms.date | targetos | description | tech.root | req.construct-type | req.ddi-compliance | req.dll | req.header | req.include-header | req.kmdf-ver | req.lib | req.max-support | req.redist | req.target-min-winverclnt | req.target-min-winversvr | req.target-type | req.typenames | req.umdf-ver | req.unicode-ansi | topic_type | api_type | api_location | api_name | f1_keywords | dev_langs | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NS:nblchecksum._NDIS_TCP_IP_CHECKSUM_NET_BUFFER_LIST_INFO |
NDIS_TCP_IP_CHECKSUM_NET_BUFFER_LIST_INFO |
11/30/2020 |
Windows |
The NDIS_TCP_IP_CHECKSUM_NET_BUFFER_LIST_INFO structure specifies information used in offloading checksum tasks from the TCP/IP transport to a NIC. |
netvista |
structure |
ndis/nblchecksum.h |
ndis.h |
Supported in NDIS 6.0 and later. |
Windows |
NDIS_TCP_IP_CHECKSUM_NET_BUFFER_LIST_INFO, *PNDIS_TCP_IP_CHECKSUM_NET_BUFFER_LIST_INFO |
|
|
|
|
|
|
The NDIS_TCP_IP_CHECKSUM_NET_BUFFER_LIST_INFO structure specifies information used in offloading checksum tasks from the TCP/IP transport to a NIC. The NDIS_TCP_IP_CHECKSUM_NET_BUFFER_LIST_INFO structure is part of the NET_BUFFER_LIST information (out-of-band data) that is associated with a NET_BUFFER_LIST structure.
A structure that contains the following members:
Set by the TCP/IP transport to indicate that the send packet contains IPv4 addresses.
Set by the TCP/IP transport to indicate that the send packet contains IPv6 addresses.
Set by the TCP/IP transport to indicate that the NIC should calculate the packet's TCP checksum.
Set by the TCP/IP transport to indicate that the NIC should calculate the packet's UDP checksum.
Set by the TCP/IP transport to indicate that the NIC should calculate the IP checksum for the first IP header in the packet. If the packet contains both a tunnel IP header and a transport IP header, the NIC should calculate the checksum for both IP headers.
Reserved for NDIS.
The offset, in bytes, of the TCP header from the beginning of the packet for TCP packets. Miniport drivers can use TcpHeaderOffset to determine the location of the TCP header so that they do not need to parse the MAC and IP header.
A structure that contains the following members:
Set by the miniport driver to indicate that the TCP checksum calculated by the NIC did not match the checksum in the receive packet's TCP header.
Set by the miniport driver to indicate that the UDP checksum calculated by the NIC did not match the checksum in the receive packet's UDP header.
Set by the miniport driver to indicate that the IP checksum calculated by the NIC did not match the checksum in the receive packet's first IP header. If the receive packet contains both a tunnel IP header and a transport IP header, the NIC validates the checksum for both IP headers.
Set by the miniport driver to indicate that the TCP checksum calculated by the NIC matched the checksum in the receive packet's TCP header.
Set by the miniport driver to indicate that the UDP checksum calculated by the NIC matched the checksum in the receive packet's UDP header.
Set by the miniport driver to indicate that the IP checksum calculated by the NIC matched the checksum in the receive packet's first IP header. If the receive packet contains both a tunnel IP header and a transport IP header, the NIC validates the checksum for the both IP headers.
NDIS uses this bit. The miniport driver must not examine or set this bit; the miniport driver should just ignore this bit.
A miniport driver that supports Receive Segment Coalescing (RSC) sets this flag to indicate that the TCP header checksum was validated by the NIC but the TCP header checksum value in the packet is not valid. For more information, see Indicating Coalesced Segments.
Miniport drivers that do not support RSC should set this flag to zero.
A miniport driver that supports RSC sets this flag to indicate that for an IPv4 packet, the IP header checksum was validated by the NIC but the IP header checksum value in the packet is not valid. For a packet consisting of both a tunnel and a transport IP header, this bit is applicable only to the tunnel IP header. For more information, see Indicating Coalesced Segments.
Miniport drivers that do not support RSC should set this flag to zero.
A PVOID version of the checksum information. Miniport drivers can use this member to access the raw information instead of the specific fields.
The NDIS_TCP_IP_CHECKSUM_NET_BUFFER_LIST_INFO structure specifies information that is used in offloading checksum tasks from the TCP/IP transport to a NIC. The NDIS_TCP_IP_CHECKSUM_NET_BUFFER_LIST_INFO structure is part of the NET_BUFFER_LIST information (out-of-band data) that is associated with a NET_BUFFER_LIST structure.
Before the TCP/IP transport passes to the miniport driver a TCP/IP packet on which the miniport driver will perform checksum tasks, the TCP/IP transport updates the NDIS_TCP_IP_CHECKSUM_NET_BUFFER_LIST_INFO structure that is associated with the NET_BUFFER_LIST structure. Specifically, the TCP/IP transport sets the IsIPv4 or IsIPv6 flag to indicate that the send packet is an IPv4 or IPv6 packet.
yyIf the TCP/IP transport does not set either the IsIPv4 or IsIPv6 flag, the miniport driver should not perform checksum tasks on the packet. If the TCP/IP transport sets the IsIPv4 or IsIPv6 flag, it also sets the appropriate flags that are required to indicate which checksums the miniport driver should calculate for the packet. For IPv4, this includes the IpHeaderChecksum, TcpChecksum, or UdpChecksum flags. For IPv6, this includes the TcpChecksum or UdpChecksum flags. In addition, for TCP packets, the TCP/IP transport sets the TcpHeaderOffset field when either the IsIPv4 or IPv6 flag is set. The transport does not set this field for UDP packets.
Before indicating up a receive TCP/IP packet on which it performs checksum tasks, a miniport driver sets the appropriate XxxChecksumFailed or XxxChecksumSucceeded flags in the NDIS_TCP_IP_CHECKSUM_NET_BUFFER_LIST_INFO structure.