So I figured out a standardized way to change the NtopNG version used in the pfSense package. So after investigating further I found out that the 0.8.13_10 package is merely a wrapper that provides the pfSense interface part of having a standard NtopNG install run as a launched process Daemon. Both are buggy as he**, and in dire need of version updates.Īfter a bit of investigation I found out that NtopNG can run both as a Service and as a launched process Daemon - the latter being the way pfSense packages provides "services". The current pfSense NtopNG package (0.8.13_10) contains an old v5.0 NtopNG build for pfSense 2.6/22.01 and a v4.0 build for older pfSense versions and ARM64/aarch64 based appliances.daily publish the current NtopNG build for freeBSD/pfSense to their own repository - AMD64 only, so it's easy to get the most current version for x86-64 based devices.But it relies on installing it as a service which is not supported or maintained across pfSense updates. actually has a guide on how to install a current NtopNG on pfSense.Turned out that was a lot easier than I thought, so I decided to write this short guide to help people get a current NtopNG version on pfSense. after a lot of frustrations with the current - buggy - NtopNG package for pfSense (Which is very seldomly updated), I decided to investigate how NtopNG actually works on pfSense - with the hope of being able to update to a current NtopNG v5.3 build.
0 Comments
Leave a Reply. |