

While networks struggle to stay up with the growth of the broader market, the network management software that supports them confronts a similar issue. However, with so many different network monitoring software and tools to choose from, it can be difficult to choose the best one for your needs and budget. I hope you'll find this tool useful, and enjoy using it.Network monitoring is essential for any enterprise for a complete connection. If you have more than one interface card, you may have to try a couple of cards before you find the right one. If you aren't seeing data updating in the interface dashboard, you might need to re-check your interface name, and ensure you typed it correctly into your docker-compose.yml file. Once in the application for the first time, you'll be directed to change those values to something you prefer. Give it about 1 minute, then visit the machine IP (server IP) of your host and the port number you set in the docker-compose.yml file, and use the default login credentials of Now, you're ready to bring up your NTopNG instance with the command: Save the file using CTRL+O and then Enter/Return to confirm the save, then CTRL+X to exit nano.įinally, make a "data" directory for your volume mapping with the command: Additionally, for the part that says enter the port number you prefer to access the interface on (for instance if you want to use 192.168.1.234:21800 - you'd put 21800 for the port number). In the above file, make sure to change the part that says to the actual name of the NIC you made note of earlier. Now, type in the following, or copy / paste it in: version: '3'Ĭommand: -community -d /var/lib/ntopng -i -r -w 0.0.0.0: Next create the new file in edit mode using: Make sure not to copy any extra leading or trailing spaces.įirst make a new directory called "ntopng" to work in using the command: Next we need to create our docker-compose.yml file, or you can copy it from here. Just make a note of the network interface name for use in our command. I used my wired card in the video at the top. If this is always going to be the state of your machine running NTOPNG, then pick whichever NIC you prefer. You may have two different cards if you have both an ethernet port and a wireless connection connected simultaneously. Look for the one with your normal network IP (for home networks often .x or sometimes 10.0.x.x, etc). This will list out all of your network interfaces on the device. In Linux you have a couple of commands that may give you results. So let's go identify our active network device name.
Ntopng generated centreon install#
Not to worry, while most docker containers are "confined" to their container and docker networks, this one is going to be able to access the NIC (Network Interface Card) we specify when running the command to install it and start it up. Now that you've got Docker installed, it's time to get into the NTOPNG installation inside of Docker.


Click the link below, or right click and open it in a new tab or window to reference it as you continue. It's truly basic terminal commands, and should only take 5 or so minutes. I recommend you go back to those posts and get Docker installed at the very least. If you don't have docker setup already, I use Docker_CE (not Docker.io) to run all of my docker containers. I have several posts that go through the steps of installing Docker and Docker-Compose on Ubuntu based systems for 18.04 and 20.04. Installing NTOPNG in Docker Install Docker Whether you're an IT admin, or an at-home self-hoster, viewing, analyzing, and understanding your network traffic patterns can help keep your networks more secure by detecting anomolies and potential intrusion quickly, as well as helping to close security gaps. By setting it up properly, it can scan your entire network and provide analytical data back about traffic patterns adn levels from different machines or sub-networks within your network. NTOPNG (I rponounce it N-Top-N-G) is a browser based server application you can run in Docker.
