From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pablo Neira Ayuso Subject: Re: Trying to provision flowtable returns error Date: Thu, 5 Nov 2020 22:01:46 +0100 Message-ID: <20201105210146.GA10732@salvia> References: <20201105005345.GA4263@dimstar.local.net> <20201105153822.GE15770@breakpoint.cc> <20201105170754.GB25824@breakpoint.cc> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Martin Gignac Cc: Florian Westphal , netfilter@vger.kernel.org On Thu, Nov 05, 2020 at 01:41:53PM -0500, Martin Gignac wrote: > > However, this would only insert the flow table statements on server > > bootup. Since '/etc/nftables/firewall.nft' ttself *wouldn't* contain > > the flow tables statements, any 'systemctl reload nftables' or 'nft -f > > /etc/nftables/firewall.nft' action (to apply a rule change, for > > example) would essentially get rid of the flow tables mechanism from > > the running system, wouldn't it? > > I guess there's no "equivalent" of iifname/oifname for flow table > devices where you could refer to a device that does not (yet) exist? You can dynamically add/delete devices to/from flowtables since Linux kernel 5.8