Unfortunately always with the same success: ntopng seems to run. Now I have already uninstalled both redis and ntopng plugins several times, additionally manually deleted the residues (conf, db) from the system and reinstalled the plugins. I can't exclude that my (premature) removal of the LAN interface on level OPNsense plugin settings led to this problem. The same is true for http and https ports. When I finally wanted to access ntopng GUI (LAN IP of the OPNsense + port number from the settings), the browser turned only to the timeout. package has been recently removed from the pfSense package list because it will not compile. With this option, you can list your VLAN networks, and ntopng should treat them as local networks. ntopng is computer software for monitoring network traffic. About VLAN traffic, I have not tested yet but ntopng has -m option. ntopng yes, it’s all lowercase provides a intuitive, encrypted. ntopng is based on libpcap / PFRING and it has been written in a portable way in order to virtually run on every Unix platform, MacOS and on Windows as well. Check its status from the Services application. ntopng is the next generation version of the original ntop, a network traffic probe that monitors network usage. Make sure this service is running and auto-started on boot. If there are no errors, then the next step is to enable port 3000 in the firewall. ntopng requires the Redis service to be up and running or it will not start. If you want to check the status, remember that you can do it with the following command: sudo systemctl status ntopng. The script can be executed, with root privileges, from the command line. Linux-based distributions are also shipped with an automatic configuration script ntopng-config that provides a graphical way to modify the configuration file. Ntopng will see it as your local network. To apply the changes, just restart the service. The configuration file can be edited manually with any text editor. Then I pressed Save button and restarted the ntopng service. To monitor public IP Address, you can fill this line -local-network yourpublicipaddress on your ntopng.start file. The service became green.īefore accessing the GUI of ntopng I first looked at the settings of ntopng in the OPNsense GUI and saw under Advanced that you can remove the default value of LAN if you want to configure the interfaces later in ntopng. The installation of os-ntopng went normally. Redis had been installed for a while on my current OPNsense system (OPNsense 20.7.7_1-amd64) and was running fine. So not the newly offered one from ntopng itself. I do really like your product and followed the open source version a long time.I tried installing the os-ntopng plugin from OPNsense yesterday. I perfectly understand where your focus need to go. I am not fulltime developer to do pull request. I will share results via blog/issues git to help others. No worries, if I find a patch working for myself with ntopng init.d script, or custom boot startup script. It means ntopng needs manual start or some customer delayed script when using your licenced package. It is an ntopng embedded/ARM ntog init.d script oversight/issue, as this package/licenced version is geared to raspberry pi without hardware clock. This impacts where I also use the ntopng bridged modes to employ filtering, which case the site goes offline until manually restarted. In other words, out of the box after installing and running embedded version on factory Raspberry Pi (Jessie) - ntopng never successfully auto starts (or stays started) after a reboot. Those errors are fine, until clock gets updated, but b) it seems ntop stops/crashes when the time gets updated after ntopng has started – and nothing in any logs to reason why. Your init script starts ntopng embedded version straight away… which a) starts to fails RRD updates since time insert is before last update time of RRD file. Raspberry Pi basically gets it correct time on every boot from NTP So it’s not a matter of just ‘setting the time’ once. Raspberry does have hardware clock, unless you buy/add module. I think I solved my issue adding ntp-wait to /etc/init.d/ntopng Firstly the RRD inserts fails being earlier than last update (before boot) as seen above.īut it seams ntopg process also stops also when the time gets updated on the fly, but I cant confirm different logs. Apr 24 02:18:56 pi systemd: Started LSB: Start/stop ntopng web.Īpr 24 02:18:56 pi ntopng: WARNING: Script failure Īpr 24 02:18:57 pi ntopng: WARNING: Script failure Īpr 24 02:18:58 pi ntopng: WARNING: Script failure Īpr 24 02:31:07 cognitive systemd: Time has been changedīecause Rasberry doesn't come with hardward clock by default, it takes a while for NTP to come into sync from factory default old date.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |