Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nprobe flows not showing in ntopng flows live #637

Open
dannyveals opened this issue Oct 31, 2024 · 11 comments
Open

nprobe flows not showing in ntopng flows live #637

dannyveals opened this issue Oct 31, 2024 · 11 comments

Comments

@dannyveals
Copy link

Hello and good day! Starting new with ntop and nprobe; both are licensed and operational:
/usr/bin/ntopng -e -i eth0 -i lo -i= zmq://127.0.0.1:5556c -w 3000 -n 1
/usr/bin/nprobe -n none -T "@NTOPNG@" --ntopng zmq://127.0.0.1:5556c --zmq-probe-mode

Both are licensed and operational but:

  1. ntopng desktop show active flows (see attached desktop-active-flows)
    desktop-active-flows
  2. nprobe flows not showing in ntopng flows live (see attached flow-live-nprobe.png)
    flow-live-nprobe
  3. showing flow exports (see attached flow-exports-nprobe.png)
    flow-exports-nprobe
  4. showing flow traffic (see attached flow-traffic-nprobe.png)
    flow-traffic-nprobe

Did I miss a step? What's required to see nprobe flows in the ntopng live flows section?

Thanks. Danny.

@marcoeg
Copy link

marcoeg commented Nov 1, 2024

The equal sign and the "c" suffix in the nprobe port may not be correct.

Try something like:
/usr/bin/ntopng -e -i eth0 -i lo -i zmq://127.0.0.1:5556c -w 3000 -n 1
/usr/bin/nprobe -n none -T "@NTOPNG@" --ntopng zmq://127.0.0.1:5556 --zmq-probe-mode

~

@dannyveals
Copy link
Author

dannyveals commented Nov 1, 2024 via email

@dkggpeters
Copy link

You did not specify -i eth0 for nprobe and it is connected to the lo interface as it is the default interface. Is that what you want?

Also, remove the c in zmq://127.0.0.1:5556c to zmq://127.0.0.1:5556.
/usr/bin/nprobe -n none -T "@NTOPNG@" --ntopng zmq://127.0.0.1:5556c --zmq-probe-mode

@dannyveals
Copy link
Author

dannyveals commented Nov 1, 2024 via email

@dkggpeters
Copy link

Not sure on the capabilities of NProbe Embedded but I believe you can only use it as a collector or proxy. You most likely need to use PFlow with PFSense (only plus has this option) to pass Netflow/IPFIX data to nprobe or port mirroring to the nprobe.

Another option to try is use the ip address:5556 of the raspberry pi rather then 127.0.0.1 and *.5556c on ntopng since it appears to reside on the pi as well. The attached blog has 2 parts in which nprobe is running on a raspberry pi although data is being fed in via port mirroring on a switch. https://brezular.com/2019/04/01/part1-monitoring-network-traffic-with-ntopng-and-nprobe/

Outside of that if it does not work, I would email support.

@marcoeg
Copy link

marcoeg commented Nov 1, 2024

Hi Danny,

I am setting up a RPI for a very similar use case and I am interested in knowing why you are setting up ntopng in probe mode. I am imagine because it is behind a firewall even though from your description it is not completely clear.

Also, what you are referring to as "ntopng embedded" is this perhaps ntopng edge?

I am waiting for a dual Ethernet shield for my compute module to setup the RPI in a very similar configuration to run nprobe on it.

Best.

@dannyveals
Copy link
Author

dannyveals commented Nov 2, 2024 via email

@dannyveals
Copy link
Author

dannyveals commented Nov 2, 2024 via email

@marcoeg
Copy link

marcoeg commented Nov 3, 2024

Hi Danny,

Check this blog as well:
https://www.ntop.org/nprobe/howto-configure-flow-collection-in-nprobe-and-ntopng/

Also, support is certainly included with the professional license. They people at ntop the company are very good at what they do.

I have a TP-Link TL-SG105E switch with the router traffic mirrored to another port where I intend to connect a RPI to monitor the traffic with nprobe. I just got my hardware, based actually on a Compute Module and a carrier board from Waveshare with two Ethernet. I will report back my experience in terms of performance but I am not worried based on my previous experience in an enterprise network with nprobe albeit on a much more powerful hardware.

From your description I don't understand how you determined you need to use nprobe in probe because if your setup is like the one in the article you provided, unless ntopng is on a remote host, you should be able to use nprobe in collector mode. Check the blog I suggested for a good definition of the two modes.

Best,

-Marco G.

@dannyveals
Copy link
Author

dannyveals commented Nov 3, 2024 via email

@marcoeg
Copy link

marcoeg commented Nov 3, 2024

Hi Danny,

I wanted to get back to you to report that I have installed the RPI with nprobe, configured ntopng on a linux machine and that everything is working as expected.

My configuration is with the RPI running nprobe with two Ethernet. One (eth1) is tapping behind the firewall the traffic on the WAN connection and the other (eth0) is inside the firewall on the same LAN where the linux machine with ntopng in configured collector mode.

I am including the configuration files for both nprobe and ntopng. The RPI eth0 is configured with IP 192.168.50.186. The linux server running ntopng is at IP 192.168.50. 17.

Hope this helps.

-Marco G.
ntop.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants