The only configuration of fprobe is command line switches. I need to correct my sentence above, where I said I used fprobe as a collector, which is not correct if you use the netflow jargon strictly. Last time I checked, netflow data was coming through well enough to be useful. It's realy bad symptom and I agree traffic flow is broken on CCR with 6.13 and should be repairįirst off, I need to say that RouterOS traffic-flow was fixed after I raised the issue. Helps turn off traffic flow, change interface, turn on traffic flow. The symptom was that temporarily flow was not sending to collector Trafic flow was configured on wan port only with version 5.Ĭollector flow-tools 0.68.5.1 was on freebsd 9.2 It's was configured 2 bridge/vlan/IP with 5 port join per bridge and 1 port wan. Is there any benefit from trying older firmware? Are there any settings which aren't documented in. The flow numbers tick over when > ip traffic-flow monĬuriously captures of the UDP port 2100 packets show data gets sent in chunks at between 4 and 5 minute intervals (when they get sent at all) while my fprobe collector sends netflow data nearly continuously. I have also tried Netflow version 5 and get similar results. The ip traffic-flow setup is so simple I can't see where it can be done wrong. My existing netflow collectors are based on fprobe running on Linux sending to pmacct, which works for me so far. At this level of operation I can't use it. sometimes reports nothing at all) and results in values maybe one tenth of the expected throughput when it is running. I am finding that netflow output is both intermittent (i.e.
Under test conditions the router is passing less than 10 Mbit/sec and there is no problem with system load.
When first installed I had version 6.12 of the firmware, now I have also tested with version 6.13. Now I am testing and find that netflow is broken. I have purchased a CCR1036 specifically for connecting to an upstream provider and need to capture netflow data in order to be able to account for customer data usage.
0 kommentar(er)
