Hi, It seems to be working now, thanks a lot! I was running on 9996 before trying 2055 but I must have made some other error.
/Oscar On Fri, September 18, 2015 12:13 pm, Frederic Hermann wrote: > > Hello Oscar, > > Try to use the '-n none' flag to disable the collector, as you are not > redirecting the flow to another collector, but instead using zmq. > > > nprobe -n none -g /var/run/nprobe.pid --collector-port=2055 --zmq > "tcp://*:5556" > > The default value of -n is localhost:2055, which is probably conflicting > with the collector-port in your case. > > > ----- Mail original ----- >> De: "Oscar Carlstedt" <[email protected]> >> À: [email protected] >> Envoyé: Vendredi 18 Septembre 2015 12:45:20 >> Objet: Re: [Ntop] nProbe as NetFlow collector >> >> Hi, >> >> Yes, I might have been unclear, sorry. >> >> Exporting flows to nTop works fine. If i run nProbe with the -i eth0 >> flag >> I can see statistics in nTop and the flows are exported through the >> zeromq >> socket. >> >> It's the NetFlow part that I can't get to work (--collector-port >> 2055). >> I'm sending NetFlow data to port 2055 on the nProbe/nTop host. The >> port is >> open i the CentOS-firewall. But nProbe doesn't seem to be collecting. >> >> I'm concerned about these errors: >> >> 18/Sep/2015 17:41:17 [collect.c:51] ERROR: Bad configuration: flows >> will >> be sent to the collection port >> 18/Sep/2015 17:41:17 [collect.c:52] ERROR: causing a waterfall >> effect: >> flow collection will be disabled >> > /Oscar _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
