A Guide to current NtopNG on pfSense 2.6/22.01 :-)
-
@netblues said in A Guide to current NtopNG on pfSense 2.6/22.01 :-):
@keyser Well, yes and no
The problem isn't contained to ntopng per se
Pfsense can't update it self properly.
and you end up with a system that misses critical components, such as mpd , needed for pppoe, and if this is your only way to connect, then you are left with no means to manualy fix things.I doubt that disabling ntopng will make the upgrade process work as expected again.
The safe way is to install from scratch and then restore configuration.
22.-5 rc is on ntopng v.5.2.220602 (FreeBSD 12.3)
and since we are approaching release, I doubt it will change.
Same package version (08.13_10) also appears at the 2.7 dev for now.Strange - when I update my test machine it works fine using that process. Are you using AMD64 or ARM64?
Anyhow, IF the included NtopNG version with 22.05/2.7 really is 5.2.220602, then I see no reason for using my hack as it has reached a reasonably mature and stable NtopNG version. I hope that goes for both AMD64 and ARM64.
ARM64 was left behind on a v4.0 release in 22.01/2.6 even though it said 5.0.xxxxx in the package manager.If this is the case I think I will be doing clean install of 22.05 to remove any leftovers from the hacked install.
-
@keyser I'm talking about pf 22.05 rc, upgraded from 22.01 with the ntopng hack, on amd64
And yes, ntopng does seem to work nicely too.
-
@netblues said in A Guide to current NtopNG on pfSense 2.6/22.01 :-):
@keyser I'm talking about pf 22.05 rc, upgraded from 22.01 with the ntopng hack, on amd64
And yes, ntopng does seem to work nicely too.
Okay that’s Nice to know. I will clean install then, restore the config, and after the official NtopNG pf package has installed (5.2.2206), I will restore my “in NtopNG” settings (rules, checks and so forth). No need for for my hack anymore
-
@keyser Ι have restored from ntopng 5.3 to 5.2 and nothing broke.
on 22.05rc after clean install
However not much customisation had been done. -
-
-
-