Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: toml <toml@thlu.de>
Cc: netfilter@vger.kernel.org
Subject: Re: Nftables + ALG + Linux 6.1.0-10-amd64 …?... is it a kown Problem?
Date: Thu, 3 Aug 2023 15:47:12 +0200	[thread overview]
Message-ID: <20230803134712.GD30550@breakpoint.cc> (raw)
In-Reply-To: <76311f64eb31224c7e750279a62fa8bd8257dba1.camel@mail>

toml <toml@thlu.de> wrote:
> Am Dienstag, dem 01.08.2023 um 22:11 +0200 schrieb Florian Westphal:
> 
> > Sounds about right, helper assignment looks correct to me.
> 
> Unfortunately, the example from my previous post does not work, when I tighten the filter to prevent unwanted traffic. For outgoing FTP I always get the message:
> "Could not open data connection to port nnnnn: Connection refused".

The helper is not active for that connection.

>         chain output {
>                 type filter hook output priority 0; policy accept;
>                 oifname "lo" accept
>                 ct state 0x2,0x4 accept
>                 meta pkttype { 0, 1, 2 } accept
>                 ip protocol 1 accept
>                 ct state 0x8 tcp dport 21 ct helper set "ftp-helper"

adding a 'counter' after set "ftp-helper" will show that its never set.

I suspect packets are eaten by the preceeding pkttype rule.
You can test via

nft insert rule ip filter output tcp flags syn tcp dport 21 meta nftrace set 1

then run 'nft monitor' and try to connect to a tcp server.


      reply	other threads:[~2023-08-03 13:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31  7:57 Nftables + ALG + Linux 6.1.0-10-amd64 …?... is it a kown Problem? toml
2023-07-31 13:36 ` Florian Westphal
2023-08-01 14:20   ` toml
2023-08-01 20:11     ` Florian Westphal
2023-08-02  7:27       ` toml
2023-08-03 12:35       ` toml
2023-08-03 13:47         ` Florian Westphal [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230803134712.GD30550@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=netfilter@vger.kernel.org \
    --cc=toml@thlu.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox