From: trentbuck@gmail.com (Trent W. Buck)
To: netfilter@vger.kernel.org
Subject: Re: Named sets with timeout
Date: Wed, 30 Oct 2019 12:12:57 +1100 [thread overview]
Message-ID: <878sp3nihy.fsf@goll.lan> (raw)
In-Reply-To: CAF90-WiguQF4PfU=8jGBSeC+PrbizWj8hXNAUQUkzOpsoLcYjA@mail.gmail.com
Laura Garcia <nevola@gmail.com> writes:
> On Tue, Oct 29, 2019 at 8:00 AM Trent W. Buck <trentbuck@gmail.com> wrote:
>> I think you are right, but see [...]
>> https://git.netfilter.org/nftables/commit/?id=24f33c7
>> ...which sounds like there is a new (as-yet-undocumented?) keyword for
>> changing (as opposed to initializing) the timeout of a set element.
>
> No new or undocumented keyword, [...]
> "update" is what you're looking for. [....]
> [2] https://wiki.nftables.org/wiki-nftables/index.php/Updating_sets_from_the_packet_path
Thanks!
I apologize for my wrong & misleading answer. :-{
next prev parent reply other threads:[~2019-10-30 1:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 20:25 Named sets with timeout Matt
2019-10-29 0:23 ` Trent W. Buck
2019-10-29 1:35 ` Duncan Roe
2019-10-29 8:00 ` Laura Garcia
2019-10-30 1:12 ` Trent W. Buck [this message]
2019-10-30 8:06 ` Laura Garcia
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=878sp3nihy.fsf@goll.lan \
--to=trentbuck@gmail.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