<div dir="ltr"><p dir="ltr" style="font-size:12.8px;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:arial;background-color:transparent;vertical-align:baseline;white-space:pre-wrap">Hi All,</span></p><br style="font-size:12.8px"><p dir="ltr" style="font-size:12.8px;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:arial;background-color:transparent;vertical-align:baseline;white-space:pre-wrap">We are using Openstack Kilo release 1:2015.1.4-0ubuntu2. We are trying to establish transport mode IPSec with one of the VM from outside.</span></p><p dir="ltr" style="font-size:12.8px;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:arial;background-color:transparent;vertical-align:baseline;white-space:pre-wrap">We have a floating IP from 172.17/16 network assigned to this VM that has private IP from 10.0/16 network.</span></p><p dir="ltr" style="font-size:12.8px;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:arial;background-color:transparent;vertical-align:baseline;white-space:pre-wrap">The IPSec is failing and we are suspecting that the NAT is the culprit. The sender is computing transport header checksum using 172.17.x.y destination but the openstack is changing it to 10.0.x.y network and the checksum is failing.</span></p><p dir="ltr" style="font-size:12.8px;line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:arial;background-color:transparent;vertical-align:baseline;white-space:pre-wrap">In this release of Openstack, is there a way to disable this nating or any workarounds? Sender side, we cannot disable the checksum.</span></p><br style="font-size:12.8px"><span style="background-color:transparent;font-size:11pt;font-family:arial;vertical-align:baseline;white-space:pre-wrap">Thanks</span><br></div>