netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laura Garcia <nevola@gmail.com>
To: Mail List - Netfilter <netfilter@vger.kernel.org>,
	Netfilter Development <netfilter-devel@vger.kernel.org>
Subject: Re: meter in 0.9.1 (nft noob question)
Date: Thu, 22 Aug 2019 13:14:40 +0200	[thread overview]
Message-ID: <CAF90-Wgt9zBSi_as1vOsisegVFYSBHWSQwv5n_cMyEcFx3wcYw@mail.gmail.com> (raw)
In-Reply-To: <20190819040944.GB10803@dimstar.local.net>

Hi Duncan,

On Mon, Aug 19, 2019 at 6:11 AM Duncan Roe <duncan_roe@optusnet.com.au> wrote:
>

[...]

>
> *** I had expected or at least hoped that an element's expiry would revert to
> *** the timeout interval if it was re-added, but this doesn't happen.
>

You'd have to use "element update" instead of "element add", but it's
not supported yet for this case.

> Was that possibility discussed on the list previously? Not having it leads to at
> least 2 undesirable consequences when watching:
>
> 1. Frequently-accessed sites drop off the bottom and re-appear at the top.
>    The lower part of the display would be more stable if expiry times reverted:
>    frequently-accessed sites would stay near the top while others would
>    percolate through.
>
> 2. Counters reset when these elements are destroyed and re-created.
>

As a workaround you can set the expiration time manually until the
"element update" solution is in place.

Cheers.

  reply	other threads:[~2019-08-22 11:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877e7qzhgh.fsf@goll.lan>
     [not found] ` <CAF90-WiPQgD7wftDxz6sT+nfH=bSRZiUJPKqBeUJRXhfPOkYsg@mail.gmail.com>
     [not found]   ` <20190806173745.GA6175@dimstar.local.net>
     [not found]     ` <CAF90-WiOo9wYWxJwAFcyjdU7OB1vgU9e=-QvDZ-vNJ1tcgmraQ@mail.gmail.com>
2019-08-19  4:09       ` meter in 0.9.1 (nft noob question) Duncan Roe
2019-08-22 11:14         ` Laura Garcia [this message]
2019-08-23  2:35           ` Duncan Roe

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=CAF90-Wgt9zBSi_as1vOsisegVFYSBHWSQwv5n_cMyEcFx3wcYw@mail.gmail.com \
    --to=nevola@gmail.com \
    --cc=netfilter-devel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).