On 28/05/2020 08:15, [email protected] wrote: > From: wenxu <[email protected]> > > Currently all the conntrack entry offfload rules will be add > in both ct and ct_nat flow table in the mlx5e driver. It is > not makesense. > > This serise provide nat attribute in the ct_metadata action which > tell driver the rule should add to ct or ct_nat flow table I don't understand why changes to the core are needed. A conntrack entry should be a NAT if and only if it has FLOW_ACTION_MANGLE actions. AIUI this is sufficient information to distinguish NAT from non-NAT conntrack, and there's no need for an additional bool in ct_metadata. But it's possible my understanding is wrong.
-ed
