<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - nft reset quotas does not reset anonymous quotas"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1314#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - nft reset quotas does not reset anonymous quotas"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1314">bug 1314</a>
from <span class="vcard"><a class="email" href="mailto:kfm@plushkava.net" title="kfm@plushkava.net">kfm@plushkava.net</a>
</span></b>
<pre>(In reply to Pablo Neira Ayuso from <a href="show_bug.cgi?id=1314#c4">comment #4</a>)
<span class="quote">> They question is if we want to have a fine grain to reset anonymous stateful
> information, or just 'nft reset ruleset' to reset all stateful information
> (including quotas and counters) is fine.
>
> What would you prefer?</span >
Personally, I'd like for it to be as granular as is reasonably possible i.e.
more or less achieving feature parity with iptables -Z. I go into specific
detail in the other bug, including some suggestions as to how the nft syntax
could look for granular reset actions.
That said, I appreciate that this might not be trivial to implement or that it
cannot necessarily be considered as a development priority. As the first course
of action, if both of "nft reset quotas" and "nft reset counters" were to cover
all anonymous instances, that would address this bug, along with one of the
requests that I made in <a class="bz_bug_link
bz_status_NEW "
title="NEW - Discretely resetting anonymous counters is impossible"
href="show_bug.cgi?id=1401">bug 1401</a>. In and as of itself, that would be a nice
improvement.
If anyone can figure out how to support granular actions thereafter, then so
much the better.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>