Hi Rajesh,
Nice labels worked for you.
Clarify me one thing: the output you did show, with zeroed peer_src_ip
(and exporteripv4address, engineid, enginetype), is the one from
pmacctd, right? Not nfacctd. In that case the output is expected.
In fact in nfacctd it should not be possible to get a
Hi Paolo,
Thanks for the fix and suggestion. I'll try tag and label primitives and
see if they match my requirements.
On Tue, Dec 25, 2018 at 10:49 PM Paolo Lucente wrote:
>
> Hi Rajesh,
>
> You are right, there was a bug in the serialize_bin() func that was
> making it work good only for the f
Hi Rajesh,
You are right, there was a bug in the serialize_bin() func that was
making it work good only for the first byte. This is now resolved:
https://github.com/pmacct/pmacct/commit/1076ff3529f439133357176e4c1260cfcdcef56e
I've read your question about metadata and was wondering: would tag
Hi Rajesh,
Thanks for bringing this further point up. While all was working with
hex and u_int semantics, there was an issue with the raw one - which was
important to fix since it's a very generic transport for any kind of
info. Here is the commit:
https://github.com/pmacct/pmacct/commit/e1206a
Hi Paolo,
Thanks for the help and suggestion ,
Custom primitives works for me with the latest code:) . I'm able to read a
field from packet and export as custom template and I can see those
templates in netflow messages also.
I'll continue with viewing the flows in a collector, I'm using Elastiflo
Hi Rajesh,
Thanks for pointing this out. I've committed some code to unlock
field_type also for uacctd/pmacctd daemons precisely for the use case
you mentioned. Here the details:
https://github.com/pmacct/pmacct/commit/87ebf3a9f907c331f752c96a76ea247e77f99107
You can back port this patch to la
