ferteat.blogg.se - Pfsense ntopng not showing geolocation

#Pfsense ntopng not showing geolocation update#
#Pfsense ntopng not showing geolocation full#
#Pfsense ntopng not showing geolocation password#
#Pfsense ntopng not showing geolocation free#

#Pfsense ntopng not showing geolocation full#

It means that the ntopng hash tables are full and some statistics can be lost For example, if the active hosts ore flows badges are red Red badges are often symptoms of problems.

Gray badge with the number of active flows.

Gray badge with the number of active devices.

Gray badge with the number of active remote hosts.

Green badge with the number of active local hosts.

Red triangle with the Alerted Flows count.

Red triangle with the Engaged alerts count.

Yellow triangle of Degraded performance.

The badges in the above picture have the following meaning (from left to right): The coloured indicate the status of many components in ntopng.

The notifications bell and the user administration menu.

The interface Up/Down throughput chart.

Reply to this email directly, view it on GitHub /issues/297#issuecomment-233402435, or mute the thread.The header bar show the ntopng status information, in particular: Rather than try to keep the pfSense UI in line with the ntopng one as it changes, one option might be just to pare it back and let people configure ntopng directly in its own interface.

#Pfsense ntopng not showing geolocation password#

The most important thing in the pfSense UI is to be able to set the password etc for the ntopng UI. You can switch those to off, or set retention periods. There are various options in the ntopng UI itself (see the preferences) which relate to the storage of RRD data. I think the configuration options in ntopng have moved on quite a bit since the older version on which the pfSense UI was modelled. On a side note, another small issue I noticed was that if using a hostname alias in the pfSense > Advanced Settings it fails to connect to ntopng over http using the alias hostname, it keeps trying to redirect to An https login would be great though! Well, I had already changed the password through the ntopng UI, however I never saw any options for retention settings or a preferences button. Reply to this email directly, view it on GitHub /issues/297#issuecomment-224417857, or mute the thread. You are receiving this because you are subscribed to this thread. On Jun 7, 2016, at 4:19 PM, Renato Botelho please keep track of pfSense changes at

#Pfsense ntopng not showing geolocation free#

I'm not sure if this would be done from your end or from the pfSense devs, feel free to direct me if needed.Ĭould there a way to configure a set amount of usable storage space so that it simply overwrites the oldest data (similar to squid) as needed? I had the "keep historical data" checkbox disabled in the ntopng settings however that did not seem to work. My recent testing rig came to stumbling halt after the HDD filed up with 12gb's of data from ntopng alongside my squid cache.

#Pfsense ntopng not showing geolocation update#

Not sure how many others are testing the ntopng package now that it's available in pfSense 2.3 when using the development update branch. This email has been checked for viruses by Avast antivirus software. Reply to this email directly or view it on GitHub You are receiving this because you commented. Will work but for the integration we need support from the pfSense To integrate ntopng with the pfSense configuration. Subject: Re: Integrate ntopng with pfsense ( We need assistance on how Would that work please? Thanks for all your help and dedication to ntopng. You've already fixed that (per your comment of 18 March). Is completely missing because of the dependency issue but it looks like Package (2.2 presumably) back into pfSense. One option is to leave that feature as part of the ntopng 2.3 releaseīut in the interim reinstate the last stable release of the ntopng In a way that pfSense can subsequently filter) then, as mentioned above, If it's a long way (I can see some complications in marking the packets PfSense can subsequently filter according to its own rules)? How far off true integration are we (i.e.