From: Jeremy Sowden <jeremy@azazel.net>
To: Sunny73Cr <Sunny73Cr@protonmail.com>
Cc: Florian Westphal <fw@strlen.de>,
"netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: Raw Payload Expressions - out of bounds write?
Date: Tue, 28 Jan 2025 12:02:04 +0000 [thread overview]
Message-ID: <20250128120204.GD485209@celephais.dreamlands> (raw)
In-Reply-To: <KzQMgyTEENAtLkTnyJgmjSJRjhrPRkiRZnDoPpM7P8n7Xs-yWpoBwP_SP12Tmn2ZGkEFLnzRRAOr4BNFwYUCKifrV8lgAtDEfki4KlpDaXU=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 565 bytes --]
On 2025-01-28, at 04:19:55 +0000, Sunny73Cr wrote:
> > Use --debug=netlink
>
> Apologies, I am not sure what this refers to: I assume it is a
> compilation argument; and I cannot recompile NetFilter as of yet.
It's one of nft's command-line arguments. From the man-page:
-d, --debug level
Enable debugging output. The debug level can be any of
scanner, parser, eval, netlink, mnl, proto-ctx, segtree,
all. You can combine more than one by separating by the ,
symbol, for example -d eval,mnl.
J.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 931 bytes --]
next prev parent reply other threads:[~2025-01-28 12:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 3:31 Raw Payload Expressions - out of bounds write? Sunny73Cr
2025-01-26 13:50 ` Florian Westphal
2025-01-26 18:08 ` Sunny73Cr
2025-01-28 0:37 ` Florian Westphal
2025-01-28 4:19 ` Sunny73Cr
2025-01-28 12:02 ` Jeremy Sowden [this message]
2025-01-28 12:12 ` Sunny73Cr
2025-01-28 12:41 ` Pablo Neira Ayuso
2025-01-30 11:27 ` Sunny73Cr
2025-02-08 20:26 ` Sunny73Cr
2025-02-09 1:47 ` Florian Westphal
2025-02-09 3:12 ` Sunny73Cr
2025-02-09 22:23 ` Pablo Neira Ayuso
2025-02-09 22:45 ` Sunny73Cr
2025-12-02 5:22 ` Sunny73Cr
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=20250128120204.GD485209@celephais.dreamlands \
--to=jeremy@azazel.net \
--cc=Sunny73Cr@protonmail.com \
--cc=fw@strlen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.