On Tue, Feb 17, 2026 at 4:28 PM Dumitru Ceara <[email protected]> wrote:
> On 2/17/26 4:25 PM, Erlon Rodrigues Cruz wrote: > >>> /* Use common zone for SNAT and DNAT if this option is set to "true". > */ > >>> -static bool use_common_zone = false; > >>> +static bool use_common_zone; > >> While I like this change, it's unrelated. It shouldn't be part of this > >> patch. > >> > >>> /* If this option is 'true' northd will make use of ct.inv match > fields. > >>> * Otherwise, it will avoid using it. The default is true. */ > >>> static bool use_ct_inv_match = true; > >>> > >>> +/* If this option is 'true' northd will flag the related ACL flows to > >> use > >>> + * connection tracking fields to properly handle IP fragments. By > >> default this > >>> + * option is set to 'false'. > >>> + */ > >>> +static bool acl_ct_translation = false; > >>> + > > This and use_common_zone slipped through the cracks. Please let me know > if > > there's something else other than those and I add to a v6. > > Hi Erlon, > > There's no need for a v6 just for these. I think we (the maintainers) > can address that when merging v5 if the rest is OK. > > Thanks, > Dumitru > > Hi Erlon, thank you for the v5, I will review it ASAP. I know we have discussed possibility of backporting this. Could you confirm how far this would be, 24.03? Also if that's the case could you please write a formal email to dev mailing list? Something similar to https://mail.openvswitch.org/pipermail/ovs-dev/2026-February/430373.html. Regards, Ales _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
