Closed nqb closed 4 years ago
Netflow is used internally for inline bandwidth accounting. The NetFlow traffic for pfacct is from the NetFlow kernel module that is configured to send the traffic to localhost:2056 https://github.com/inverse-inc/packetfence/blob/devel/packetfence.modprobe . In order not to conflict with the fingerbank-collector, we listen internally to localhost:2056. This does not seem to be a bug.
Thanks for you clarification.
Describe the bug If I send NetFlow traffic on management IP of my PacketFence server, I didn't see anything created in
bandwidth_accounting
table in DB.To Reproduce Steps to reproduce the behavior:
fingerbank-collector
(to have a process that listen onudp/2055
(NetFlow port) on all interfaces)udp/2055
with:
scapy
is installed=> I didn't see anything in logs or in DB.
Expected behavior Have a log or a row created in DB.
Additional context Maybe nothing is handled because packet sent using
scapy
is not created with correct values in headers, see full packet header below: