All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel@vger.kernel.org, phil@nwl.cc, eric@garver.life
Subject: Re: [nftables PATCH v3] tools: add a systemd unit for static rulesets
Date: Wed, 20 Aug 2025 15:06:31 +0200	[thread overview]
Message-ID: <aKXIV7dEmZUfXE5O@calendula> (raw)
In-Reply-To: <20250417145055.2700920-1-jengelh@inai.de>

On Thu, Apr 17, 2025 at 04:48:33PM +0200, Jan Engelhardt wrote:
> There is a customer request (bugreport) for wanting to trivially load a ruleset
> from a well-known location on boot, forwarded to me by M. Gerstner. A systemd
> service unit is hereby added to provide that functionality. This is based on
> various distributions attempting to do same, for example,
> 
> https://src.fedoraproject.org/rpms/nftables/tree/rawhide
> https://gitlab.alpinelinux.org/alpine/aports/-/blob/master/main/nftables/nftables.initd
> https://gitlab.archlinux.org/archlinux/packaging/packages/nftables
> 
> ---
> v2->v3:
>  * ExecStart uses `nft flush ruleset`
>  * flush command thus no longer needed in the .nft file,
>    which allows for just redirecting `nft list` output
>  * Manpage mentions `nft list ... >main.nft`

Applied, thanks.

I made a small change to display ${unitdir} path in the ./configure
log, to provide a hint to users that systemd unit file is being added.

      parent reply	other threads:[~2025-08-20 13:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 14:48 [nftables PATCH v3] tools: add a systemd unit for static rulesets Jan Engelhardt
2025-04-17 18:21 ` Eric Garver
2025-08-20 13:06 ` Pablo Neira Ayuso [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=aKXIV7dEmZUfXE5O@calendula \
    --to=pablo@netfilter.org \
    --cc=eric@garver.life \
    --cc=jengelh@inai.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=phil@nwl.cc \
    /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.