On 08/04/2009 03:26:03 PM, Paolo Lucente wrote:
> Things get tricky for the output interface instead - as that
> can change dynamically, given that multiple interfaces are
> available. Two approaches come to my mind at these regards:
> Anybody interested willing to comment? Any third way i might
Hi Paolo,
Thanks for the quick response. I just downloaded the code and it looks
like it would be fairly easy for me to add the input interface into the
netflow record. I'll let you know if I get it working.
The output interface would be nice too, but I know that a lot more
complicated to get a
Hi Stig,
As of now, there is no way to populate the input interface field
in the NetFlow record. Of course, this can be easily implemented
as pmacctd can listen on only one interface at time (whereas if
nfprobe is re-exporting something received from sFlow or NetFlow
the input interface informatio
I've been searching the mail archives for info on this topic and found a
thread suggesting to running an instance of pmacctd per interface (using
the ifindex as the engine_id) and use the nfprobe plugin to export all
instances to nfacctd on localhost. Then in nfacctd I added a pre_tag_map
to map t
