From mboxrd@z Thu Jan  1 00:00:00 1970
From: Duncan Roe <duncan_roe@optusnet.com.au>
Subject: Re: [nft 0.9.3 | kernel 5.4.48] cannot get NAT to work
Date: Fri, 26 Jun 2020 13:28:48 +1000
Message-ID: <20200626032848.GD2523@dimstar.local.net>
References: <6e919ed9-50d9-7a23-a581-2c6110af5108@gmx.net>
 <20200623224854.GU26990@breakpoint.cc>
 <f67206b8-aebc-47b5-a3e2-d2d07d2bb53e@gmx.net>
 <20200624081443.GV26990@breakpoint.cc>
 <c4212304-c8f3-ebc7-c9cc-101a5e2ef28a@gmx.net>
 <20200624085315.GW26990@breakpoint.cc>
 <1c9f8c63-c2cb-a730-fb0a-a5b92ec5167b@gmx.net>
 <20200625014506.GC2523@dimstar.local.net>
 <d149de72-fea0-ae74-d55a-80f07b42a17b@gmx.net>
 <43821a84-92d8-3b4f-2c67-58f9132a7b8c@gmx.net>
Mime-Version: 1.0
Return-path: <netfilter-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <43821a84-92d8-3b4f-2c67-58f9132a7b8c@gmx.net>
Sender: netfilter-owner@vger.kernel.org
List-ID: <netfilter.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>

On Thu, Jun 25, 2020 at 08:45:00AM +0000, ????????????? wrote:
> On 25/06/2020 07:13, ????????????? wrote:
[...]
> > 
> > OpenWrt, whilst revolving around routers it is not NFT centric.
> > 
[...]
> > 
> > Does not work with the distro as it does not provide the necessary
> > directories /lib/modules/$(uname -r)/modules.order and
> > /lib/modules/$(uname -r)/modules.builtin

That is odd. The 2 files are approx 130KB and 13KB and are always produced in a
kernel build.
> 
> Alternatively there is - oddly none exhibiting a dependency on
> nft_chain_nat:
> 
nft_chain_nat depends on nf_nat & nf_tables, not vice versa.
The kernel loads it in respone to the netlink message generated by
> nft 'add chain inet nat prerouting...

I can't reproduce what you see even with these revisions:

# nft --version
nftables v0.9.3 (Topsy)
# ls -1 /usr/lib64/libnftnl*
/usr/lib64/libnftnl.so
/usr/lib64/libnftnl.so.11
/usr/lib64/libnftnl.so.11.2.0
# uname -r
5.4.48

If you modprobe nft_chain_nat as part of the boot process, you should of course
be fine.
To explore the problem further, I would build a 5.4.48 kernel from kernel.org
source, using the .config you have. As long as you have a spare 6G disc space,
you gould git clone
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git (6GB allows for a
build).

Cheers ... Duncan.