From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Kerin Millar <kfm@plushkava.net>
Cc: "Lars Noodén" <lars.nooden@gmx.com>,
"Linux Netfilter Users List" <netfilter@vger.kernel.org>
Subject: Re: Wiki entry on Element timeouts in NFtables
Date: Thu, 12 Sep 2024 12:29:22 +0200 [thread overview]
Message-ID: <ZuLCghrK5pp1kWjL@calendula> (raw)
In-Reply-To: <ZuK1yDMm2tXj7yRm@calendula>
On Thu, Sep 12, 2024 at 11:35:04AM +0200, Pablo Neira Ayuso wrote:
> On Sun, Sep 08, 2024 at 01:07:44AM +0100, Kerin Millar wrote:
> > On Sat, 7 Sep 2024, at 7:23 AM, Lars Noodén wrote:
[...]
> > Thirdly, if the set was specified to support stateful elements but has no defined 'timeout' value, the behaviour will be as if 'expires' had not been specified at all and the element will be added a permanent one, if it did not already exists. I consider this behaviour to be a bug because the outcome does not match the user's intent. I think that the kernel should instead raise EINVAL on the basis that the user is requesting for the element to be ephemeral but the request parameters make the request impossible to satisfy.
>
> flags timeout provides a hint to the kernel that element with timeouts
> are possible, but default behaviour is "element times out" if not
> specified. Forcing the user to provide a timeout does not sound very
> flexible to me.
Sorry, wording is not correct:
... are possible, but default behaviour is "element never times out" if not
specified....
next prev parent reply other threads:[~2024-09-12 10:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-07 6:23 Wiki entry on Element timeouts in NFtables Lars Noodén
2024-09-08 0:07 ` Kerin Millar
2024-09-12 9:35 ` Pablo Neira Ayuso
2024-09-12 10:29 ` Pablo Neira Ayuso [this message]
2024-09-12 9:30 ` Pablo Neira Ayuso
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=ZuLCghrK5pp1kWjL@calendula \
--to=pablo@netfilter.org \
--cc=kfm@plushkava.net \
--cc=lars.nooden@gmx.com \
--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