Hi Yin, I'm back sorry it took a while 😊.
When applying `OvsUpdateAddressAndPort` for some reason there still is a problem with the checksums. There are two aspects which apparently are hit for some reason: 1. normal packet. 2. tcp segment. If I disable tcp/udp checksums(on the NIC) normal packets have the right checksums. However, the tcp segments checksums are still wrong. If I apply a full blown checksum using ` OvsApplySWChecksumOnNB` and ` OvsTcpSegmentNBL`(just for checksum computations) things are fine with tcp/udp checksum enabled/disabled and lso enabled/disabled. From what I can think of the pseudochecksums are wrong when being sent down to a NIC. I'll try to dig further into this issue since what you apply here is the same thing we apply on the set ip/tcp port actions and that works fine. Thanks, Alin. > -----Original Message----- > From: ovs-dev-boun...@openvswitch.org [mailto:ovs-dev- > boun...@openvswitch.org] On Behalf Of Yin Lin > Sent: Thursday, March 23, 2017 12:12 AM > To: d...@openvswitch.org > Subject: [ovs-dev] [PATCH 3/3 v2] datapath-windows: NAT integration with > conntrack > > Signed-off-by: Yin Lin <li...@vmware.com> _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
