[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aPe1_kECjXm3Ydfb@strlen.de>
Date: Tue, 21 Oct 2025 18:34:06 +0200
From: Florian Westphal <fw@...len.de>
To: Andrii Melnychenko <a.melnychenko@...s.io>
Cc: pablo@...filter.org, kadlec@...filter.org, phil@....cc,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, horms@...nel.org,
netfilter-devel@...r.kernel.org, coreteam@...filter.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/1] nft_ct: Added nfct_seqadj_ext_add() for NAT'ed
conntrack.
Andrii Melnychenko <a.melnychenko@...s.io> wrote:
> Hi all,
>
> > I think this needs something like this:
> >
> > if (!nfct_seqadj_ext_add(ct))
> > regs->verdict.code = NF_DROP;
>
> Okay - I'll update it. I'm planning a proper test.
>
> Apparently, I need to provide a simple test FTP server/client, not
> fully functional,
> but sufficient to "trigger" nf_conntrack_ftp.
Argh, I forgot we do have an ftp test case in the nftables repo, even
with NAT.
tests/shell/testcases/packetpath/nat_ftp
in nftables.git repo from git.netfilter.org.
So it would be easier to extend that instead of a new kselftest for the
kernel.
>From a short glance I guess it works because the address rewrite doesn't
need to expand the packet, else this should have failed and found this
bug...
Powered by blists - more mailing lists