New Package: ntopng
-
Thank you Jimp! I was happy with ntop but thank you for creating this add-on…
-
I thought I was happy with ntop, but that was before I saw ntopng. :-)
-
it tried to install 386 on a 64 bit install
-
I pushed a fix for that a bit ago, it'll be OK shortly.
-
Thanks Jimp!
I had a small bounty for this ($50). You want it or want me to donate it?
-
We can't take direct donations anymore. It's not quite enough for a Gold subscription or I'd say just get one of those. But you can pick up some stuff from the pfSense store with that and you'll get some swag out of it on top of us getting a cut. :-)
-
This is fantastic! Thanks for doing this.
-
Thank you so much jimp!
I thought I will never see ntop on pfSense anymore.
I was on 2.2-ALPHA August 9 and it was not showing up under packages then I updated to the latest Aug 15 version and its still not there, any suggestions? -
It won't compile right now on 2.2, the port is broken on FreeBSD 10.x. The ntopng author is working with the port maintainer to get it corrected.
-
I'm trying to get it to compile in various ways but no success yet.
-
Thanks jimp! I appreciate your efforts!
Can't use v2.1.4 on my Shuttle DS437 because nics are not supported.
At least there's some hope :D -
Great an thank you
hope squid3-dev become supported by pfsense and more stable
-
It's live now on 2.2. Works fine on my test VM anyhow. Give it a spin.
-
It does not see my lan nic
-
Interesting. I installed this on a test machine with two physical NICs and the menu options for NTOPNG appeared under my Diagnostics menu. It showed traffic flowing from my internal NIC without any problem. I then installed it on my production system and can't see the ntopng men item under the Diagnostics menu at all! Both machines are running pfSense 2.1.4. The only real difference between both boxes is that my production system is operating a captive portal and my two internal NICs on the production system are set as VLANs sharing the same physical network card. So my first question is why isn't the Diagnostics menu showing the ntopng items? My second query is whether ntopng will work with a VLAN-tagged NIC bound to a physical NIC? I can get the ntopng page to load (port 3000), but it's monitoring only the outside network card and no other NICs are available as options.
I appreciate this is an alpha release, so I won't set my hopes too high that this might be resolved soon.
-
The package work great ,,, the problem was from me
Thanks again
-
In deed this a 800lb Gorilla!
It works and I love it. Only one thing that does not work is a GeoMap it looks like it needs to be compalied with geolocation but that's not a big deal._NOTE
Browser reported home map location [Latitude: xx.3581782, Longitude: -xxx.03674879999998]
In order to visualize maps you must:
Have a working Internet connection.
Have compiled ntopng with geolocation and started with it.
Have active flows between peers with public IP addresses.
HTML browser geolocation is used to place on map hosts based on unknown locations._ -
My geolocation seems to work. It shows everything coming from my city and shows the routes to the major feeds.
this new ntop is visually a complete rewrite and way over the top of what I expected.
-
My geolocation seems to work. It shows everything coming from my city and shows the routes to the major feeds.
this new ntop is visually a complete rewrite and way over the top of what I expected.
I'm assuming for geolocation you didn't need to change anything?
-
I've now re-installed the updated version (1.1v0.1 to 1.1v0.2) on my test machine to see if the problem was with the update. It seems it is! The latest version of this package fails to update the Diagnostics menu on the 64-bit pfsense system I'm running and also breaks the uninstall process as well. I'm going to try to see if I can do a manual uninstallation of the package and see whether I can get the older version of ntop to work any better.
From what I could tell, ntopng looks very good and has huge potential. The package installation needs a bit of tweaking, though.
