OPNsense Forum

Archive => 21.1 Legacy Series => Topic started by: danderson on January 28, 2021, 07:53:54 pm

Title: ntopng & ndpi
Post by: danderson on January 28, 2021, 07:53:54 pm
so in 20.7.8 ntopng shows v4.x and in 21.1 it shows 3.4.0

but in the packages it says 4.2 for ntopng and 3.4 for ndpi.

am i seeing it incorrectly and it is current? or why does the interface say there is a newer version than installed and it showed 4.x in 20.7.8 and in 21.1 it is older 3.4.x

ntopng -V
v.3.4.0 [Community build]
GIT rev:        :4.2.210125

Title: Re: ntopng & ndpi
Post by: aimdev on February 11, 2021, 09:01:13 am
As an aside, see
https://github.com/ntop/ntopng/issues/5021#issuecomment-777244471
and

Ntop removed due to high cpu and high cpu tempertures aftere upgrade to
OPNsense 21.1.1-amd64
FreeBSD 12.1-RELEASE-p13-HBSD
Title: Re: ntopng & ndpi
Post by: franco on February 11, 2021, 09:06:02 am
We use whatever ntopng/ndpi version is in FreeBSD ports. NTOP people want to ship newer binaries, but this will always create side effects during updates and upgrades so be aware of this when adding third party repositories...


Cheers,
Franco
Title: Re: ntopng & ndpi
Post by: aimdev on February 11, 2021, 04:29:55 pm
I mentioned my reluctance re updating from a non opnsense source to ntop.
The current Freebsd release is ntopng-4.2.d20210122,1

The opnsense maintainers email address m.muenz@gmail.com bounced when I tried to contact him.
The main issue was the update available message that would not go away, hence the github issue.
Anyway after the latest update 21.1.1 my fanless box got rather hot, cpu normally below 50C, but it was flat out 100%cpu, 56C so, top revealed it was ntopng so it got terminated.
Strangely it did not do this on the 20.7 or 21.1 versions.
I will try it when opnsense release a new version, it is not vital, just nice to have.
Title: Re: ntopng & ndpi
Post by: danderson on February 11, 2021, 09:18:00 pm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252935

Looks like Franco found an issue, i see progress and maybe this maintainer madpilot/Guido Falsi seems more responsive than Michael Muenz <m.muenz@gmail.com> with a DOA email addr

Thanks Franco