Bug#994273: More info

2021-10-07 Thread Harry STARR
> The bug that I believe is responsible is in this if-block: > > https://git.netfilter.org/nftables/tree/src/rule.c#n372 > >When listing a set, nft will set the `stateless` flag in order to >suppress the state of any counters it defines. However, it doesn't keep >track of whether the flag was

Bug#994273: More info

2021-10-07 Thread Harry STARR
> I'll send a patch upstream. > > J. I have noticed that on Gentoo and Arch this seems to be resolved. They are using a version > 1.0.x Maybe already fixed upstream... H.

Bug#994273: Follow-up example

2021-10-06 Thread Harry STARR
Here is my-nftables (used to instantiate the ruleset): nft -f my-nftables >>> my-nftables flush ruleset table ip filter { set bad_guys { type ipv4_addr size 65535 timeout 31m counter elements = {

Bug#994273: nftables: nft -s does NOT suppress stateful output

2021-09-14 Thread Harry STARR
Package: nftables Version: 0.9.8-3.1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgrade to bullseye * What exactly did you do (or not do) that was effective (or ineffective)? nft