Hi all,
I was running through the pm_pcap_cb code, and it looks like the "req"
passed to exec_plugins(, ); at
https://github.com/pmacct/pmacct/blob/d72440dc9a7d0d0a7ed9502f1dd31b90105b1d95/src/nl.c#L167
and to load_id_file at
nfprobe flow tree does not take interface index into consideration
when searching/aggregating the flow data.
This means that for the case multiple pcap interfaces are being
monitored and same src/dst ip/port traffic pattern is being handled
over several of those interfaces, this will all land in
The pcap direction configuration was explicitly disabled
in 81fe649917036b9ef1ed4b3ea521befcaf36496b,
however even before that commit it apparently did not work,
because the pcap_setdirection must be called after pcap_activate,
not before it.
Introduce a new config variable, pcap_set_direction
to
Hi all,
I had experienced some issues with configuring multiple pcap interfaces with
pmacctd and wanted to clarify them with you and potentially ask for a
better/alternative solution/configuration.
The two patches submitted here actually illustrate the problems I encountered
and the way I had