The Mako Group accepts no liability for any damage caused by any virus transmitted by this email. Finally, the recipient should check this email and any attachments for the presence of viruses. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action with respect to the contents of this information is strictly prohibited. Most of the data and information shown in ntopng web GUI is related to the currently selected interface.
![ntopng not showing new interface ntopng not showing new interface](https://weberblog.net/wp-content/uploads/2016/08/Wireshark-NetFlow-v9-01-Template-150x150.png)
A special interface is always present in ntopng, the System Interface. Among all interfaces listed, one has a check mark that indicates the interface is currently selected. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the Mako Group. The Interfaces dropdown menu entry in the top toolbar contains lists all the interfaces that are currently monitored by ntopng. If you have received this email in error please notify the sender immediately by email and delete this e-mail from your system. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. You are receiving this because you authored the thread.Message ID: MAKO. Triage notifications on the go with GitHub Mobile for iOS or Android. Reply to this email directly, view it on GitHub, or unsubscribe.
NTOPNG NOT SHOWING NEW INTERFACE UPDATE
To: ntop/ntopng *** Tung Ho Wong *** *** Re: MAC address based traffic direction not working following the yum update to ntop v.29 ( #5941)Ĭan you please check if this is solved in the latest build? I’m running the dev release and it’s still showing traffic in one direction only.įrom: Simone Mainardi *** Saturday, 25 December 2021 2:44 AM The 20s gap was due to the downtime of ntopng during the package upgrade. Timestamp (utc) before bytes-sent has been 'back' to zero > select * from "iface:traffic_rxtx" where ifid='4' and bytes_sent!=0 and time > now()-7d order by time desc limit 10 Timestemp (utc) since bytes_sent has been 'back' to zero > select * from "iface:traffic_rxtx" where ifid='4' and bytes_sent=0 and time > now()-7d order by time asc limit 10 I tried to use the MAC address of the local WAN interface in the field and then restarted ntopng but the TX & RX traffic wasn't seggregated. The MAC address of the remote-end wasn't changed before and after the package upgrade. The System Interface has menu entries which are different from the other interfaces.Įach individual menu bar entry will be discussed below.Not working means both TX & RX traffic is now combined into RX series. ( here can be found more information on this topic).Ī menu bar is always available on the left to navigate across ntopng pages.Įntries in the menu bar change depending on the currently selected interface.
NTOPNG NOT SHOWING NEW INTERFACE 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.
![ntopng not showing new interface ntopng not showing new interface](https://i.redd.it/cfkb9zg8hl741.jpg)
![ntopng not showing new interface ntopng not showing new interface](https://weberblog.net/wp-content/uploads/2016/08/Wireshark-NetFlow-v9-01-Template.png)
The header bar show the ntopng status information, in particular: