Download
NetHogs is a small 'net top' tool. Instead of breaking the traffic down per protocol or per subnet, like most tools do, it groups bandwidth by process. NetHogs does not rely on a special kernel module to be loaded.
Categories
Network MonitoringLicense
GNU General Public License version 2.0 (GPLv2)Follow NetHogs - 'net top' per process
Other Useful Business Software
AI-generated apps that pass security review
Retool lets you generate dashboards, admin panels, and workflows directly on your data. Type something like “Build me a revenue dashboard on my Stripe data” and get a working app with security, permissions, and compliance built in from day one. Whether on our cloud or self-hosted, create the internal software your team needs without compromising enterprise standards or control.
Rate This Project
Login To Rate This Project
User Reviews
-
Really appreciated. Please keep up-to-update.
-
NetHogs is incredibly useful for curious users such as myself. Whenever my network usage spikes, I like to know what is causing it. NetHogs makes this task trivial, especially when paired with a bash alias (nio) so I don't have to type 'sudo nethogs enp4s0' all the time. Thank you for your hard work on this program!
-
An excellent one command tool, that breaks up the whole bandwidth usage per process. A must have for Linux users!
-
very useful and simple! can be started with -t option and the log be captured and reused! (I just miss it be updated on ppa as big max_pid reqs cvs download)
-
Pretty useful tool. However, I could not get the trace mode work. However I was able to find a fix. Since I could not create ta bug, I'm adding the details here hoping that it would be useful to others. The trace mode is not working in version 0.8.0, but is is working in 0.7.0 #sudo nethogs -t em1 Adding local address: 192.168.1.101 Ethernet link detected Waiting for first packet to arrive (see sourceforge.net bug 1019381) The program does not report any data. A gdb session revealed that the getmaxyx () call in do_refresh () of cui.cpp is was returning -1 and causing the do_refresh() return without reporting any data. Moving the getmaxyx () and few subsequent statements to the else part of "if (DEBUG || tracemode)" solved the problem for me.
