netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: toml <toml@thlu.de>
To: netfilter@vger.kernel.org
Subject: Incomprehensible behavior
Date: Thu, 03 Aug 2023 16:43:45 +0200	[thread overview]
Message-ID: <0d41d9238002f90a1c5a2c7702f675ccd17736bb.camel@mail> (raw)

(I'm so sorry... my previous post is in failed format... please ignore)

Hello @ all

I'm still struggling anymore with the new syntax at
ApplicationLayerGateway/FTP and testing with smallest steps. In doing
so I have now come across the following effect. I have 2 test-rules
here, both of which i expected to completely block any outgoing
traffic.

But as you can see from the second example in the counter, only here is
blocked. The first example has no effect at all, everything works as if
it was not blocked.

# nft list ruleset
table ip filter {
 chain output {
 type filter hook output priority 0; policy drop;
 meta pkttype { 0, 1, 2 } accept
 counter packets 0 bytes 0 reject with icmp 13
 }
}

# nft list ruleset
table ip filter {
 chain output {
 type filter hook output priority 0; policy drop;
 meta pkttype { 1, 2 } accept
 counter packets 1858 bytes 165434 reject with icmp 13
 }
}

Is this a desired behavior, when a unicast-accept virtually neutralizes
the complete filter? How do I deal with this problem?

Best Regards
Thomas


             reply	other threads:[~2023-08-03 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03 14:43 toml [this message]
2023-08-03 15:04 ` Incomprehensible behavior Florian Westphal
2023-08-03 15:59   ` toml
  -- strict thread matches above, loose matches on Subject: below --
2023-08-03 14:37 toml

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=0d41d9238002f90a1c5a2c7702f675ccd17736bb.camel@mail \
    --to=toml@thlu.de \
    --cc=netfilter@vger.kernel.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).