From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Alex Forster <aforster@cloudflare.com>
Cc: Kyle Bowman <kbowman@cloudflare.com>,
kernel-team <kernel-team@cloudflare.com>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
linux-kernel@vger.kernel.org,
Network Development <netdev@vger.kernel.org>
Subject: Re: [PATCH] netfilter: xt_NFLOG: allow 128 character log prefixes
Date: Tue, 27 Jul 2021 23:52:40 +0200 [thread overview]
Message-ID: <20210727215240.GA25043@salvia> (raw)
In-Reply-To: <CAKxSbF3ZLjFo2TaWATCA8L-xQOEppUOhveybgtQrma=SjVoCeg@mail.gmail.com>
On Tue, Jul 27, 2021 at 04:44:42PM -0500, Alex Forster wrote:
> > I'm not refering to nftables, I'm refering to iptables-nft.
>
> Possibly I'm misunderstanding. Here's a realistic-ish example of a
> rule we might install:
>
> iptables -A INPUT -d 11.22.33.44/32 -m bpf --bytecode "43,0 0 0
> 0,48 0 0 0,...sic..." -m statistic --mode random --probability 0.0001
> -j NFLOG --nflog-prefix "drop 10000 c37904a83b344404
> e4ec6050966d4d2f9952745de09d1308"
>
> Is there a way to install such a rule with an nflog prefix that is >63 chars?
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.
next prev parent reply other threads:[~2021-07-27 21:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 19:00 [PATCH] netfilter: xt_NFLOG: allow 128 character log prefixes 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 [this message]
2021-07-27 22:45 ` Alex Forster
2021-07-27 23:02 ` Pablo Neira Ayuso
2021-07-28 1:43 ` [netfilter-core] " Phil Sutter
2021-07-30 18:27 ` Kyle Bowman
2021-08-01 14:14 ` Jeremy Sowden
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=20210727215240.GA25043@salvia \
--to=pablo@netfilter.org \
--cc=aforster@cloudflare.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=kbowman@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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 NNTP newsgroup(s).