LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Phil Sutter <firstname.lastname@example.org>
To: Alex Forster <email@example.com>
Cc: Pablo Neira Ayuso <firstname.lastname@example.org>,
Network Development <email@example.com>,
Kyle Bowman <firstname.lastname@example.org>,
Jozsef Kadlecsik <email@example.com>,
Jakub Kicinski <firstname.lastname@example.org>,
"David S. Miller" <email@example.com>
Subject: Re: [netfilter-core] [PATCH] netfilter: xt_NFLOG: allow 128 character log prefixes
Date: Wed, 28 Jul 2021 03:43:47 +0200 [thread overview]
Message-ID: <20210728014347.GM3673@orbyte.nwl.cc> (raw)
On Tue, Jul 27, 2021 at 05:45:09PM -0500, Alex Forster via netfilter-core wrote:
> > Yes, you can update iptables-nft to use nft_log instead of xt_LOG,
> > that requires no kernel upgrades and it will work with older kernels.
> I've always been under the impression that mixing xtables and nftables
> was impossible. Forgive me, but I just want to clarify one more time:
> you're saying we should be able to modify iptables-nft such that the
> following rule will use xt_bpf to match a packet and then nft_log to
> log it, rather than xt_log as it does today?
iptables-nft is free to use either xtables extensions or native nftables
expressions and it may mix them within the same rule. Internally, this
is all nftables but calling xtables extensions via a compat expression.
You might want to check iptables commit ccf154d7420c0 ("xtables: Don't
use native nftables comments") for reference, it does the opposite of
what you want to do.
> iptables-nft -A test-chain -d 184.108.40.206/32 -m bpf --bytecode
> "1,6 0 0 65536" -j NFLOG --nflog-prefix
Keep in mind though, you may end with rulesets an older iptables(-nft)
will reject. I've seen people running into such compat issues when using
containers for things they shouldn't, but that's a different story.
> We had some unexplained performance loss when we were evaluating
> switching to iptables-nft, but if this sort of mixing is possible then
> it is certainly worth reevaluating.
There were some significant performance improvements in the near past.
Repeating the check might yield better results in this aspect, too.
next prev parent reply other threads:[~2021-07-28 1:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 19:00 Kyle Bowman
2021-07-27 19:54 ` Pablo Neira Ayuso
2021-07-27 20:06 ` Alex Forster
2021-07-27 21:10 ` Pablo Neira Ayuso
2021-07-27 21:22 ` Alex Forster
2021-07-27 21:27 ` Pablo Neira Ayuso
2021-07-27 21:44 ` Alex Forster
2021-07-27 21:52 ` Pablo Neira Ayuso
2021-07-27 22:45 ` Alex Forster
2021-07-27 23:02 ` Pablo Neira Ayuso
2021-07-28 1:43 ` Phil Sutter [this message]
2021-07-30 18:27 ` [netfilter-core] " Kyle Bowman
2021-08-01 14:14 ` Jeremy Sowden
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: [netfilter-core] [PATCH] netfilter: xt_NFLOG: allow 128 character log prefixes' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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 NNTP newsgroup(s).