From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 045F5C38A2D for ; Tue, 25 Oct 2022 11:05:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232329AbiJYLF2 (ORCPT ); Tue, 25 Oct 2022 07:05:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42966 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231751AbiJYLFY (ORCPT ); Tue, 25 Oct 2022 07:05:24 -0400 Received: from mail.netfilter.org (mail.netfilter.org [217.70.188.207]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 7C2DE7AB3D; Tue, 25 Oct 2022 04:05:12 -0700 (PDT) Date: Tue, 25 Oct 2022 13:05:08 +0200 From: Pablo Neira Ayuso To: Michael Lilja Cc: "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Jonathan Corbet , Jozsef Kadlecsik , Florian Westphal , netdev@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, netfilter-devel@vger.kernel.org, coreteam@netfilter.org Subject: Re: [PATCH] Periodically flow expire from flow offload tables Message-ID: References: <20221023171658.69761-1-michael.lilja@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20221023171658.69761-1-michael.lilja@gmail.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Sun, Oct 23, 2022 at 07:16:58PM +0200, Michael Lilja wrote: > When a flow is added to a flow table for offload SW/HW-offload > the user has no means of controlling the flow once it has > been offloaded. If a number of firewall rules has been made using > time schedules then these rules doesn't apply for the already > offloaded flows. Adding new firewall rules also doesn't affect > already offloaded flows. > > This patch handle flow table retirement giving the user the option > to at least periodically get the flow back into control of the > firewall rules so already offloaded flows can be dropped or be > pushed back to flow offload tables. > > The flow retirement is disabled by default and can be set in seconds > using sysctl -w net.netfilter.nf_flowtable_retire How does your ruleset look like? Could you detail your usecase? Thanks.