I'm not sure how it works beyond that it reads /proc, but whatever it does it uses a whole lot more compute than nethogs does (which also displays per process and also uses /proc as the information source). This is fine for most of my machines, but for lower-specced machines I'll probably have to stick with nethogs[1] [1]: https://github.com/raboof/nethogs. - Source: Hacker News / 6 months ago
Nethogs(rpm) is a much simpler solution. It's also available on the repos. Source: over 1 year ago
Ngrep is ok, I just use nethogs, nmap and tcpick, and tcpdump with termshark for most network analysis. Source: over 1 year ago
Hello. I'm running linux mint at the moment. And I use a program that check the network sometimes that's called nethogs. https://github.com/raboof/nethogs. Source: almost 3 years ago
I think nethogs might do this if I'm looking at the screenshot properly. Bandwhich appears to show what's being connected to on a per-process basis. Source: about 3 years ago
Do you know an article comparing Nethogs to other products?
Suggest a link to a post with product alternatives.
This is an informative page about Nethogs. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.