![]() To tell your Mikrotik to analyse all traffic passing through the device.Īt this point you need to start nProbe and ntopng on 192.168.8.20 as follows nprobe -i none -n none -3 2055 -zmq tcp://127.0.0.1:1234 interface bridge settings set use-ip-firewall=yes V9-template-refresh=20 v9-template-timeout=1m Inactive-flow-timeout: > /ip traffic-flow target print detailĠ src-address=0.0.0.0 dst-address=192.168.8.20 port=2055 version=9 That should be reported as > /ip traffic-flow print Or if configured from the command line /ip traffic-flowĪdd dst-address=192.168.8.20 port=2055 v9-template-timeout=1m Suppose that both nProbe and ntopng are running on the same PC active at 192.168.8.20 and suppose that nProbe collect flows at port 2055. The first thing to do is to configure NetFlow (both v5 and v9 are used) on the MikroTik that cane done from the command line or from the GUI. For this reason the workflow is the one depicted below: ![]() With the advent of ntopng, we have decided to avoid natively supporting netflow in ntopng due to the many “dialects” a of the protocol and leave to nProbe the task to do the conversion of flows onto something ntopng can understand. MikroTik routers are pretty popular in particular in the wireless community and many users of the original ntop are familiar with it.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |