I have tested both PAID and opensource netflow collectors. (Traffic Accounting does not have this requirement!) * = both settings i usually have to make ONLY for netflow. Īnd even with (Fast-track disabled + bridge = "use ip firewall")* ive still had issues seeing Nat'd traffic on TrafficFlow collectors (ie seeing 192.168.1.42 -> 17.2.54.1 actual bandwidth usage over time). I have tried netflow for years, and see very poor detail for traffic behind NAT (which is almost always), additionally, it seems that you cant use Fast-Track (understandably) with netflow(trafficFlow), if you wish to capture all private, NAT'd (local) ip addresses. Netflow does not provide the resolution (and accuracy) i have been able to achieve with custom code + mikrotiks, unique, Traffic Accounting feature. (i intentionally use netflow and traffic flow interchangeably below, to distinguish it from Traffic-Accounting, im aware trafficFlow=Netflow):
0 kommentar(er)
