From: "Kevin P. Fleming" <lists.netfilter@kevin.km6g.us>
To: netfilter@vger.kernel.org
Subject: Re: Problems understanding nftables part 2
Date: Fri, 31 May 2024 11:19:12 -0400 [thread overview]
Message-ID: <c0a93cb6-5a99-4d5b-ba30-e55c418b403f@app.fastmail.com> (raw)
In-Reply-To: <1393698327.20240531171132@WKraft.org>
On Fri, May 31, 2024, at 11:11, Wolfgang wrote:
>> It's not clear that you understand that the value of nftrace doesn't quietly reset itself to 0 between hooks, however.
>
> Can you explain this further? Which value of nftrace? What shall reset itself?
It appears you misunderstood the statement.
The point being made here is that once 'nftrace' has been set to '1' on a packet, it will stay '1' for the entire lifetime of that packet through the netfilter subsystem. It will go back to zero, or any other value, and there is no need to set it to '1' again in a later hook or chain. If you set it to '1' in a very early part of the netfilter lifecycle, you'll be able to use 'nft monitor' to see the handling of that packet through the remainder of the lifecycle.
Thus, if you are setting it to '1' in 'ingress', for example, there is no need have rules to set it to '1' in any other tables or hooks or chains (unless there are different conditions applied on those rules).
next prev parent reply other threads:[~2024-05-31 15:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 15:46 Problems understanding nftables part 2 Wolfgang
2024-05-29 22:31 ` Kerin Millar
[not found] ` <305618533.20240530185617@WKraft.org>
2024-05-31 1:46 ` Kerin Millar
2024-05-31 15:11 ` Wolfgang
2024-05-31 15:19 ` Kevin P. Fleming [this message]
2024-05-31 15:34 ` Wolfgang
2024-05-31 16:26 ` Kerin Millar
2024-05-31 16:06 ` Kerin Millar
2024-05-31 19:31 ` Wolfgang
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=c0a93cb6-5a99-4d5b-ba30-e55c418b403f@app.fastmail.com \
--to=lists.netfilter@kevin.km6g.us \
--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