From: Florian Westphal <fw@strlen.de>
To: Subham Pal <subhampal789@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Atomic ruleset update through libnftables
Date: Tue, 24 Feb 2026 13:57:51 +0100 [thread overview]
Message-ID: <aZ2gT3iiXfxZT2en@strlen.de> (raw)
In-Reply-To: <CAHeizqEqDQYVs6mBOC4GPhBT6h9ikfkhYD455jUDXvjfQQ-ZRA@mail.gmail.com>
Subham Pal <subhampal789@gmail.com> wrote:
> I am writing a firewall program and intending to configure nftables
> using libnftables userspace library. The plan is to use
> nft_run_cmd_from_buffer function call, passing JSOn input to its
> buffer.
>
> If I provide a set of rule updates to this function, will they be
> applied atomically? The manpage does not seem to elaborate on this.
Yes, its applied atomically. You can validate by running 'nft monitor'
on another terminal, this will show you when a new generation/config
arrives, and what was added/removed as part of the update.
prev parent reply other threads:[~2026-02-24 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 10:54 Atomic ruleset update through libnftables Subham Pal
2026-02-24 12:57 ` Florian Westphal [this message]
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=aZ2gT3iiXfxZT2en@strlen.de \
--to=fw@strlen.de \
--cc=netfilter@vger.kernel.org \
--cc=subhampal789@gmail.com \
/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