Dears,
Just for the archives: this has been solved by this commit:
https://github.com/pmacct/pmacct/commit/0da36b1aba053128532d6c1342e4f777a46b0041
Cheers,
Paolo
On Sat, Dec 03, 2016 at 01:24:47AM +0200, Сергей Горшков wrote:
> Hi Paolo, thank you for the answer
>
> root@pmacct:/etc/pmacct#
Hi Fabien,
One step back on your question: you refer to the flow records or to the
transport protocol here? You can travel v4 and v6 records within the
same, say, v4 NetFlow/IPFIX/sFlow transport. This is what all exporters
basically do; are you working with an exporter that is behaving in a
diff
Hi Hiep,
Unfortunately this is not possible today nor in the roadmap. The easiest
thing that comes to mind is a two-steps kind of export: you export from
pmacct into a script, running local, that enriches the records with DNS
lookups; from there you ship enriched records to your consumers for
pre
Hi Paolo,
Le 2016-12-07 17:54, Paolo Lucente a écrit :
Hi Fabien,
One step back on your question: you refer to the flow records or to the
transport protocol here? You can travel v4 and v6 records within the
same, say, v4 NetFlow/IPFIX/sFlow transport. This is what all exporters
basically do; ar