On May 17, 2018, at 9:03 AM, Simone Mainardi 
<<>> wrote:

On 17 May 2018, at 14:30, Gerhard Mourani 
<<>> wrote:

Hi Simone,

Here the ntopng and nNrobe configuration used.

--interface eth0
--interface tcp://
--user ntopng
--pid /var/run/ntopng/
--http-port 0
--https-port :3001
--data-dir /var/lib/nst/ntopng
--dns-mode 1
--disable-login 0
--sticky-hosts none
--http-prefix /ntopng
--ndpi-protocols /etc/ntopng/protos.txt

/usr/local/bin/nprobe -i none -n none --zmq tcp://*:5556 -b 2 -3 6343 
--city-list=/usr/share/ntopng/httpdocs/geoip/GeoLiteCity.dat -G --pid-file 
/var/run/nprobe/ -V 9 --disable-cache --zmq-disable-buffering

I don't know if I can attach pictures to this message to explain what I mean by 
saying that my collector ntopng return sflow to the remote Meraki device.

Traffic from my collector IP is almost 100% sent and when I check the Protocol 
detail, it show that it's sFlow (Sent 100%) to my remote Meraki device under 
the Peers tab!

Are you sure you have selected  interface tcp:// from the ntopng 
interfaces dropdown menu?


On May 17, 2018, at 3:53 AM, Simone Mainardi 
<<>> wrote:


Can you enclose nProbe and ntopng configurations used as well as an example of 
what you mean with 'my collector return the flow to the Meraki device'?

Thank you

On 16 May 2018, at 19:59, Gerhard Mourani 
<<>> wrote:


I've activated Netflow v9 on Cisco Meraki and receive flow on nProbe (v 
8.2.171206-5975) correctly. The problem is that my collector (ntopng v 3.2) 
return the flow to the Meraki device and I don't understand why? This generate 
lot of data in our case ~1TB per hour for sflow!.

Ntop mailing list<>

Ntop mailing list<>

Ntop mailing list<>

Ntop mailing list<>

Ntop mailing list

Reply via email to