Hi @bui & @shivam2001 , I was thinking about the PR115. Now it fetches the `nftables` sets' current state in every loop. It can be tens or hundreds of thousands of set elements fetched every `10 sec` (default). It may not be such a big performance issue, but it feels bit an overkill. What if `nftables.go` would keep the state updated in `nft struct` (e.g. `setElems4`) and this would get synced every predefined period (e.g. every `10 min` / `1h`). It is highly unlikely that the set would be completely off all the time. It does not consume any more memory since we would fetch the set on every update otherwise.