Hi Paolo,
I've been experimenting with the new json output - nice addition. One
thing I ran into was that the iface value was wrong. For example here's
the csv output compared with the json output:
root@ubnt-SJ:/etc/pmacct# pmacct -p /tmp/uacctd-e.pipe -s -T bytes -O csv
TAG,IN_IFACE,OUT_IFACE,
Hi Mario,
Thanks for bringing this up, as you are scratching on a limbo
situation which is good to iron out. My take on src_as_path,
src_local_pref, src_std_comms, etc. is that they are all evil
since are based on reverse BGP lookups. Hence i've removed
mentions from official docs and stopped impl
Hi Nick,
Thanks for your patches. Most of the minor issues were already fixed in
the CVS code; i've fixed the couple remaining. The memory leak is not a
"real" one: some structures are not free'd up in amqp_cache_purge() but
such function is called in a writer, ephemeral processes spawned each
amq
Hi,
the print plugin doesn't output src_as_path (tested with 1.5.0rc2).
I verified a similar setup with the memory plugin successfully and checked the
source code, src/print_plugin.c misses src_as_path. Duplicating the lines for
as_path and updating them to reflect src_as_path worked for me.
Re
Hi,
For our own use case of pmacct, I have added durable message support to
the amqp plugin. I have formatted this change into a set of Quilt
patches, so I can easily compile my changes into a proper Debian package.
The patches introduce a new config variable for the amqp plugin called
'amqp_pers