I read the code and find this
datapath/conntrack.c : 982
if (info->nat && !(key->ct_state & OVS_CS_F_NAT_MASK) &&
(nf_ct_is_confirmed(ct) || info->commit) &&
ovs_ct_nat(net, key, info, skb, ct, ctinfo) != NF_ACCEPT) {
return -EINVAL;
}
I
On Thu, Jun 1, 2017 at 4:28 AM, 钢锁0918 wrote:
> that is for this problem[ovs-dev] [ovs-discuss] ovn: unsnat handling error
> for Distributed Gatewayhttps://mail.openvswitch.org/pipermail/ovs-
> dev/2017-April/330536.html
I don't understand why this workaround is a good
IMO, following that discuss mail chain, it ends up here:
https://mail.openvswitch.org/pipermail/ovs-dev/2017-April/331200.html
I did not see any update to the test case to reproduce the problem.
On 1 June 2017 at 04:28, 钢锁0918 wrote:
> that is for this problem[ovs-dev]
that is for this problem[ovs-dev] [ovs-discuss] ovn: unsnat handling error for
Distributed
Gatewayhttps://mail.openvswitch.org/pipermail/ovs-dev/2017-April/330536.html
*RTFSC*
--发件人:Ben Pfaff