ntopng Archives - Page 14 of 21

RFC8520 (Manufacturer Usage Description) specifies what is the intended (from the manufacturer standpoint) network behaviour of a network device. Being it defined in JSON format by the device manufacturer, it can be…

ntopng

August 26, 2019

Merging Infrastructure and Traffic Monitoring: Integrating ntopng with Icinga

Icinga2 is an open source monitoring system which checks the availability of hosts and services, notifies users of outages and generates performance data for reporting. Thanks to its scalability and extensibility, it…

n2disk

August 16, 2019

Combining Traffic Recording with Visibility at 100 Gbps

A few months ago, with ntopng 3.8, we introduced support for continuous traffic recording, that allows you to drill down historical data from the timeseries level up to raw packets. This is…

nProbe

August 1, 2019

Containers and Networks Visibility with ntopng and InfluxDB

For a while we have investigated how to combine system and network monitoring in a simple and effective way. In 2014 we have done a few experiments with Sysdig, and recently thanks…

nDPI

May 31, 2019

TLS/SSL Analysis: When Encryption and Safety Are Not Alike

Most people think that SSL means safety. While this is not a false statement, you should not take it for granted. In fact while your web browser warns you when a certain…

News

May 28, 2019

Telemetry Data in ntopng: Giving Back to the Community

The latest ntopng 3.9 dev gives you the possibility to choose whether to send telemetry data back to ntop. We collect and analyze telemetry data to diagnose ntopng issues and make sure…

nProbe

May 18, 2019

Packets vs Flows: Which Option is the Best?

One of the most difficult steps on a monitoring deployment scenario is to choose where is the best point where traffic has to be monitored, and what is the best strategy to…

ntopng

April 6, 2019

Detecting Hidden Hosts and Networks on your (shared) LAN

In theory on switched networks each portion of a LAN is independent. This means that for instance that network 192.168.1.0/24 and 192.168.2.0/24 are using different switch ports that communicate through a router,…

Features

March 19, 2019

How enable DPI-based Traffic Management in pfSense using nEdge

We have been receiving several inquiries from pfSense users who would love to complement the classical firewall-style pfSense features with the inline Layer-7-based traffic policing offered by nEdge. Being able place pfSense…

Announce

March 19, 2019

ntopng Multilanguage Support: EN, IT, DE and JP

We are happy to announce that ntopng has gone fully international! The following languages are now officially supported: English Italian Japanese German Language files are completely opensource, meaning that you can choose…

nEdge

February 22, 2019

How to Track and Fight Malware, Ransomware, Botnets… using ntopng

Malware blacklists are not something new to ntopng. ntopng (including ntopng Edge) has integrated the emerging threats blacklist https://rules.emergingthreats.net for a long time. The 3.6 stable release also introduced some webmining blacklists,…

ntopng

February 9, 2019

Identifying Suspicious Flows: Network Issues or Misbehaving Hosts ?

Starting from the latest 3.9 version, ntopng features and handy dropdown menu that allows you to filter flows on the basis of their current TCP state. Being able to filter flows on…

Using RFC8520 (MUD) to Enforce Hosts Traffic Policies in ntopng

Merging Infrastructure and Traffic Monitoring: Integrating ntopng with Icinga

Combining Traffic Recording with Visibility at 100 Gbps

Containers and Networks Visibility with ntopng and InfluxDB

TLS/SSL Analysis: When Encryption and Safety Are Not Alike

Telemetry Data in ntopng: Giving Back to the Community

Packets vs Flows: Which Option is the Best?

Detecting Hidden Hosts and Networks on your (shared) LAN

How enable DPI-based Traffic Management in pfSense using nEdge

ntopng Multilanguage Support: EN, IT, DE and JP

How to Track and Fight Malware, Ransomware, Botnets… using ntopng

Identifying Suspicious Flows: Network Issues or Misbehaving Hosts ?