Hi Timo,
'ip' is to match the IP address of the sender of the NetFlow/IPFIX packet.
Paolo
On Tue, Mar 07, 2017 at 01:29:11PM +0100, Timo Lindhorst wrote:
> Hi Paolo,
>
> > I would make one exception
> > which did not raise from your email: the potential need for IP addresses
> > (in the IPFIX
Hi Paolo,
> I would make one exception
> which did not raise from your email: the potential need for IP addresses
> (in the IPFIX flow) to be masked with a given netmask for comparison
> against a prefix in the map -
>From browsing the documentation, I assumed that 'ip' as pretag match might
be a
Hi Timo,
Thanks for providing the use-cases, they sound valid to me. Also, you
are right saying it's no big deal to implement these new keys as they
would be mostly similar to the existing ones. I would make one exception
which did not raise from your email: the potential need for IP addresses
(i
Hi Paolo,
thanks for your response.
> All of that should fall in the pre_tag_filter domain but I can
> anticipate you none of the fields you are mentioning (ie.
> post_nat_src_host, src_host_country or nat_event) are currently
> supported. What would be your use-case? Feel free to say here or via
Hi Timo,
All of that should fall in the pre_tag_filter domain but I can
anticipate you none of the fields you are mentioning (ie.
post_nat_src_host, src_host_country or nat_event) are currently
supported. What would be your use-case? Feel free to say here or via
unicast email.
Paolo
On Tue, Feb
Hi,
we're currently digging into pmacct and friends and I'm quite happy
about its feature set and extensibility.
Now, I face a probably not so uncommon use case, which I'm not able
to find a simple solution for:
The `aggregate_filter` key allows to filter flows before passing them
to a plugin. T
