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 196D6C61DA4 for ; Thu, 9 Mar 2023 15:24:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231700AbjCIPYV (ORCPT ); Thu, 9 Mar 2023 10:24:21 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45392 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230386AbjCIPYC (ORCPT ); Thu, 9 Mar 2023 10:24:02 -0500 Received: from mail.netfilter.org (mail.netfilter.org [217.70.188.207]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id C58B95A1A0 for ; Thu, 9 Mar 2023 07:23:28 -0800 (PST) Date: Thu, 9 Mar 2023 16:23:25 +0100 From: Pablo Neira Ayuso To: Phil Sutter Cc: netfilter-devel@vger.kernel.org Subject: Re: [nft PATCH] doc: nft.8: Document lower priority limit for nat type chains Message-ID: References: <20230309135246.18143-1-phil@nwl.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20230309135246.18143-1-phil@nwl.cc> Precedence: bulk List-ID: X-Mailing-List: netfilter-devel@vger.kernel.org On Thu, Mar 09, 2023 at 02:52:46PM +0100, Phil Sutter wrote: > Users can't know the magic limit. > > Signed-off-by: Phil Sutter > --- > doc/nft.txt | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/doc/nft.txt b/doc/nft.txt > index 7de4935b4b375..0d60c7520d31e 100644 > --- a/doc/nft.txt > +++ b/doc/nft.txt > @@ -439,6 +439,9 @@ name which specifies the order in which chains with the same *hook* value are > traversed. The ordering is ascending, i.e. lower priority values have precedence > over higher ones. > > +With *nat* type chains, there's a lower excluding limit of -200 for *priority* > +values, because conntrack hooks at this priority and NAT requires it. prerouting, output -200 NF_IP_PRI_CONNTRACK this should only apply in these two hooks, it should be possible to relax this in input and postrouting in the kernel. > + > Standard priority values can be replaced with easily memorizable names. Not all > names make sense in every family with every hook (see the compatibility matrices > below) but their numerical value can still be used for prioritizing chains. > -- > 2.38.0 >