Might have been unclear, sorry.Exporting flows to nTop \ , at 12:45, Oscar Carlstedt wrote:Hi,Yes, I \ "Simplicity is the ultimate sophistication" - Leonardo da Vinci# \ Nprobe configuration.Yuri #Yuri Francalacci \ > listening on ens160, link-type EN10MB (Ethernet), capture size 65535
Ntopng server probing suppress full#
> tcpdump: verbose output suppressed, use -v or -vv for full protocol > ~]# tcpdump -i ens160 udp dst port 2055 > 18/Sep/2015 17:41:17 Succesfully created ZMQ endpoint > /usr/share/ntopng/httpdocs/geoip/GeoIPASNumv6.dat > /usr/share/ntopng/httpdocs/geoip/GeoIPASNum.dat > 18/Sep/2015 17:41:17 Running on CentOS Linux release > ($Revision: 4468 $) for x86_64-unknown-linux-gnu with native PF_RING > to 0: did you forget to use -u perhaps ? > set to 0: did you forget to use -Q perhaps ? > 18/Sep/2015 17:41:17 WARNING: The output interfaceId is > I'm having trouble configuring nProbe as a NetFlow-collector and then > "Simplicity is the ultimate sophistication" - Leonardo da Vinci > ntopng is configured in the right way, you will see traffic from ntopng to > So, you will not see any packet exported on port 2055 for sure, but if > nProbe acts as server instead of client in this case). > in this scenario ntopng will connect to port 5556 of nprobe (note that > On Fri, Septem11:12 am, Yuri Francalacci wrote: But nProbe doesn't seem to be collecting. > I'm sending NetFlow data to port 2055 on the nProbe/nTop host. > It's the NetFlow part that I can't get to work (-collector-port 2055). > I can see statistics in nTop and the flows are exported through the zeromq "Simplicity is the ultimate sophistication" - Leonardo da Vinci Try adding a -n none to the nprobe configuration.
0 kommentar(er)
