disable-login disables the login for the web UI. interface 1 tells ntopng which interface to listen on for flows. local-networks defines which IP subnet is local, everything else will be categorized as remote. I think starting with version 1.1 nTopNG starts automatically with the machine and uses the config from /etc/ntopng/ntopng.start - this is my ntopng.start file: -local-networks "192.168.30.0/24" However it does retain host history so you can see a summation of the data sent/received and who its been talking too, etc.Īs far as configuration goes I have two NICs in a desktop machine with ntopng installed eth0 is the management NIC, ie the NIC I access the web UI with and then I mirror the interface connected to my internet connection to eth1. I guess my other issue is that there aren't really any line graphs, it would be nice if you could focus on a host and see its bandwidth usage over time, etc. Maybe there's a way to script it but I haven't looked into it yet. As example see protos.txt -disable-host-persistency -P Disable host persistency -redis-r Species the redis database host and port. I've been using nTopNG for a little while now and it's neat, but not particularly useful for me mainly because, AFAIK, it doesn't have any built-in alerting or reporting capabilities. host:'' where string is part of an host name.I have a feeling i had some issues with the different syntax between starting the ntopng executable and running it as a daemon, but I won't know unitil I gain access to the machine in a couple of weeks. So essentially, I just wanted to check whether anyone is successfully using ntopng, and retaining host history, ie, you logon and it retains all flows and host history since the service has been started. In any case, I wasn't successful in getting the history to stick before I lost it. ntopng-docker Install & Run docker run -nethost -t ppcelery/ntopng-docker \\ -http-port 0.0.0.0:3000 \\ -redis REDISHOST:REDISPORT \\ Or run via docker. In the process of configuring it, I borked the machine and lost access. I was configuring a machine remotely with ntopng, attempting to set up sticky hosts so I could retain history and set up an overview of daily usage, just like I did with ntop. It certainly has a better interface, even though it is definitely lacking some of the features of ntop. Now being that ntop has been superseded by ntopng, i though I would give this a go. With the end of support for 13.10, I updated one machine to 14.04, which introduced a slightly newer ntop version, but this has a glitch in the host detail screen, it sort of freezes, in any case it's a problem. I have been using Ubuntu 13.10 server for a while, as this had the latest version of ntop in the repositories, and it takes only minutes to configure. This way, I can easily get a snapshot of bandwidth usage, and a lot of other useful information. Essentially, I just run it on an a spare machine, set up sticky hosts, and set the machine to reboot everyday. I have been using using ntop at smaller deployments for years as a general troubleshooting and reference tool for bandwith usage and network analysis.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |