[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191204.163232.1306369201437008300.davem@davemloft.net>
Date: Wed, 04 Dec 2019 16:32:32 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: aconole@...hat.com
Cc: netdev@...r.kernel.org, pshelar@....org, jhs@...atatu.com,
xiyou.wangcong@...il.com, jiri@...nulli.us, dev@...nvswitch.org,
linux-kernel@...r.kernel.org, mleitner@...hat.com,
paulb@...lanox.com, roid@...lanox.com, nicolas.dichtel@...nd.com
Subject: Re: [PATCH 1/2] openvswitch: support asymmetric conntrack
From: Aaron Conole <aconole@...hat.com>
Date: Tue, 3 Dec 2019 16:34:13 -0500
> The openvswitch module shares a common conntrack and NAT infrastructure
> exposed via netfilter. It's possible that a packet needs both SNAT and
> DNAT manipulation, due to e.g. tuple collision. Netfilter can support
> this because it runs through the NAT table twice - once on ingress and
> again after egress. The openvswitch module doesn't have such capability.
>
> Like netfilter hook infrastructure, we should run through NAT twice to
> keep the symmetry.
>
> Fixes: 05752523e565 ("openvswitch: Interface with NAT.")
> Signed-off-by: Aaron Conole <aconole@...hat.com>
> ---
> NOTE: this is a repost to see if the email client issues go away.
Applied and queued up for -stable.
Powered by blists - more mailing lists