#Ntopng will not start how to#
#Ntopng will not start update#
#Ntopng will not start manual#
#Ntopng will not start Patch#
#Ntopng will not start Offline#

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.

#Ntopng will not start Patch#

No worries, if I find a patch working for myself with ntopng init.d script, or custom boot startup script.

Configuration files as well as option settings can be given as input to the ntopng executable. When starting ntopng it is possible to modify its behavior by customizing one or more of the several optional settings available, using either the command line, or grouping them in a configuration file.

#Ntopng will not start manual#

It means ntopng needs manual start or some customer delayed script when using your licenced package. ntopng can be started from the command line of your favorite Linux, Unix and Windows system. 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.

#Ntopng will not start Offline#

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.

#Ntopng will not start update#

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. This will surely help us classify the network traffic analyzed by nTop in a detailed way.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. For example once for security reasons I had to configure an SSH daemon in order to make it listen on TCP/2222 port instead of TCP/22. # you can see for example we are indicating to nTop that on our network TCP/81 traffic should still be classified as HTTP traffic.Īnd so it becomes a sorting and recognition task for how we can distribute the daemon sockets listening on the systems of our serving hosts. Where the protos.txt file must adhere to the following structure: # Format: Via the configuration file found at the path: This requires adding the following directive to nTop: Here is where the nDPI library with the right instructions allows us, as in this case, to define the classification of the 1.37GB of traffic that in this case is not identified. Here are some examples:īut in the case of a network we are currently analyzing, there were still some applications defined as Unknown: Motivated by these needs, this is where a library such as nDPI enables nTop to recognize many of the most popular applications used today.

Other examples include social networks, geographic maps, video streaming services, in other words, the TCP/80=web equation is no longer valid. Today this is no longer the case, as for example with Skype and other peer-to-peer applications whose traffic is transported over HTTP or HTTPS precisely for the purpose of being able to function even in environments with the presence of packet filtering and firewalling. For example note that years ago not everything was transported over TCP/80 port, which was typically used just for HTTP and related web resources.

In any case the need to classify not only the packet header but also the transport protocol has led to the need for a more detailed classification of network traffic. NTop now uses the nDPI (network deep packet inspection) library to classify packets within network traffic for those protocols that either do not use a standard port (defined as well known ports like and ) or that are dynamically assigned.

#Ntopng will not start how to#

2022 Giovanni Davide Saccá NetEye, Unified Monitoring nTop and nDPI: How to Increase Network Traffic Analysis