Hi all,
We've were experimenting with pmacctd/nfacctd-based IP traffic
accounting recently, and have faced some issues with handling small
packet floods by pmacctd/nfacctd in our setup.
Would be great if someone here could suggest us how we could overcome them.
Our goal was actually to precisely
===
set_tag=101
========
Thanks & Regards,
Mikhail
Mikhail Sennikovsky (2):
* pmacctd: allow configuring pcap_setdirection
* nfprobe: per-interface flows
src/cfg.c | 2 ++
src/cfg.h | 2 ++
src/cfg_handlers.c
allow pmacctd do pcap_setdirection.
Signed-off-by: Mikhail Sennikovsky
---
src/cfg.c | 1 +
src/cfg.h | 1 +
src/cfg_handlers.c | 14 ++
src/cfg_handlers.h | 1 +
src/pmacctd.c | 15 +++
5 files changed, 24 insertions(+), 8 deletions(-)
diff
traffic pattern).
Introduce a new nfprobe_per_interface_flows config variable to
allow taking flow interface indexes into consideration when
matching/searching for the FLOW entries in the flow cache tree.
Signed-off-by: Mikhail Sennikovsky
---
src/cfg.c | 1 +
src/cfg.h
Hi all,
I was running through the pm_pcap_cb code, and it looks like the "req"
passed to exec_plugins(&pptrs, &req); at
https://github.com/pmacct/pmacct/blob/d72440dc9a7d0d0a7ed9502f1dd31b90105b1d95/src/nl.c#L167
and to load_id_file at
https://github.com/pmacct/pmacct/blob/d72440dc9a7d0d0a7ed9502f
;
> Hi Mikhail,
>
> If you see all the daemons that make use of the 'req' structure have a
> memset() for 'req' shortly after its declaration. For example here in
> pmacctd: https://github.com/pmacct/pmacct/blob/master/src/pmacctd.c#L360
>
> Paolo
>
&
Hi guys,
Would be great if someone of the maintainers could comment on my
patches, and give some feedback on whether they make sense or propose
and alternative/better configuration to achieve a similar setup.
Thanks a lot,
Mikhail
On Fri, 17 Jan 2020 at 13:02, Mikhail Sennikovsky
wrote:
>
&