Skip to content

Commit

Permalink
datapath-windows:Reset PseudoChecksum value only for TX direction off…
Browse files Browse the repository at this point in the history
…load case

While testing OVS-windows flows for the DNAT/SNAT action, the checksum in
TCP header is set incorrectly when TCP offload is enabled by default. As a
result,the packet will be dropped on the Windows VM when processing the packet
 from Linux VM which has included correct checksum at first.  On the Windows VM,
 it has gone through two NAT actions and OVS Windows kernel will reset the
checksum to PseudoChecksum and then it will lose the original correct checksum
value which is set outside.

Back to the Nat TCP/UDP checksum value reset logic,it should reset it TCP checksum
To be PseudoChecksum value only on Tx direction for TCP Offload case.  For the packet
From the outside,  OVS Windows Kernel does not need reset the TCP/UDP checksum as
It should be the job of the received network driver to get out a correct checksum
Value.

>>>sample flow on default configuration on both Windows VM and Linux VM
(src=192.168.252.1,dst=10.110.225.146)-->dnat/snat-> (src=169.254.169.253,
Dst=10.176.26.107) Without the fix the return back packet(src=10.176.26.107,
Dst=169.254.169.253) will have the correct TCP checksum. After the reverse NAT
Actions, it will be changed to be packet (src=10.110.225.146, Dst=192.168.252.1)
But with incorrect TCP checksum 0xa97a which is
The PseudoChecksum. Related packet is put on the reported issue below.

Reported-at:openvswitch/ovs-issues#231
Signed-off-by: Wilson Peng <pweisong@vmware.com>
Signed-off-by: Alin-Gabriel Serdean <aserdean@ovn.org>
  • Loading branch information
pweisong authored and aserdean committed Oct 28, 2021
1 parent 2c1369a commit da5b115
Showing 1 changed file with 7 additions and 4 deletions.
11 changes: 7 additions & 4 deletions datapath-windows/ovsext/Actions.c
Expand Up @@ -1527,6 +1527,7 @@ OvsUpdateAddressAndPort(OvsForwardingContext *ovsFwdCtx,

csumInfo.Value = NET_BUFFER_LIST_INFO(ovsFwdCtx->curNbl,
TcpIpChecksumNetBufferListInfo);

/*
* Adjust the IP header inline as dictated by the action, and also update
* the IP and the TCP checksum for the data modified.
Expand All @@ -1535,6 +1536,7 @@ OvsUpdateAddressAndPort(OvsForwardingContext *ovsFwdCtx,
* ChecksumUpdate32(). Ignoring this for now, since for the most common
* case, we only update the TTL.
*/
/*Only tx direction the checksum value will be reset to be PseudoChecksum*/

if (isSource) {
addrField = &ipHdr->saddr;
Expand All @@ -1551,7 +1553,7 @@ OvsUpdateAddressAndPort(OvsForwardingContext *ovsFwdCtx,
((BOOLEAN)csumInfo.Receive.UdpChecksumSucceeded ||
(BOOLEAN)csumInfo.Receive.UdpChecksumFailed);
}
if (l4Offload) {
if (isTx && l4Offload) {
*checkField = IPPseudoChecksum(&newAddr, &ipHdr->daddr,
tcpHdr ? IPPROTO_TCP : IPPROTO_UDP,
ntohs(ipHdr->tot_len) - ipHdr->ihl * 4);
Expand All @@ -1572,7 +1574,7 @@ OvsUpdateAddressAndPort(OvsForwardingContext *ovsFwdCtx,
(BOOLEAN)csumInfo.Receive.UdpChecksumFailed);
}

if (l4Offload) {
if (isTx && l4Offload) {
*checkField = IPPseudoChecksum(&ipHdr->saddr, &newAddr,
tcpHdr ? IPPROTO_TCP : IPPROTO_UDP,
ntohs(ipHdr->tot_len) - ipHdr->ihl * 4);
Expand All @@ -1581,7 +1583,7 @@ OvsUpdateAddressAndPort(OvsForwardingContext *ovsFwdCtx,

if (*addrField != newAddr) {
UINT32 oldAddr = *addrField;
if (checkField && *checkField != 0 && !l4Offload) {
if ((checkField && *checkField != 0) && (!l4Offload || !isTx)) {
/* Recompute total checksum. */
*checkField = ChecksumUpdate32(*checkField, oldAddr,
newAddr);
Expand All @@ -1590,11 +1592,12 @@ OvsUpdateAddressAndPort(OvsForwardingContext *ovsFwdCtx,
ipHdr->check = ChecksumUpdate32(ipHdr->check, oldAddr,
newAddr);
}

*addrField = newAddr;
}

if (portField && *portField != newPort) {
if (checkField && !l4Offload) {
if ((checkField) && (!l4Offload || !isTx)) {
/* Recompute total checksum. */
*checkField = ChecksumUpdate16(*checkField, *portField,
newPort);
Expand Down

0 comments on commit da5b115

Please sign in to comment.