Hi Fanen,
This is still not possible. probably more than aggregate_filter, which
uses tcpdump syntax (with its benefits and limitations), this feature
could go in a pre_tag_map, issuing a tag or a label, then matching it
(to pass or discard) in the config with a pre_tag_filter /
pre_tag_label_filter as a complement to existing src_net, dst_net keywords.
Would you mind opening an issue on GitHub (*), i will then mark it as
Enhancement and keep it on my radar; executing this via the pre_tag_map
would not be a big dev and i could converge on it in relatively soon time.
Paolo
(*) https://github.com/pmacct/pmacct/issues
On 30/6/24 15:17, Fanen Ahua wrote:
Hi,
I came across this thread:
https://pmacct-discussion.pmacct.narkive.com/kpyxCIue/filtering-flows
<https://pmacct-discussion.pmacct.narkive.com/kpyxCIue/filtering-flows>
having faced the same issue.
aggregate_filter[in]: dst net 192.168.1.0/24 <http://192.168.1.0/24> or
dst net 2a12:xxxx:zzzz::/48
I've configured nfacctd to receive flow information from mikrotik, and I
observe that only IPv6 traffic is matching on the inbound filter.
I wonder if support for aggregate filter on post-nat source address is
now possible?
Thanks in advance,
Fanen.
_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists
_______________________________________________
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists
