Nethogs VS vnStat

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 / 7 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

For more information about vnStat use "man vnstat" or visit: Http://humdi.net/vnstat/. Source: about 1 year ago

Something similar to vnstat (which monitor the bandwidth usage): https://humdi.net/vnstat/. This tool doesn't necessarily take into account only the ports 80 and 443, it can be generalized to all the traffic flow, but that would be a great if it does. Source: about 1 year ago

Take a look at https://humdi.net/vnstat/ - it should work on *BSD and I think there's a package for pfSense (and by extension should be there for OPNSense as well). Otherwise it's not too hard to setup to run at start up as well. Source: over 2 years ago

If you don't want to run a stack can try something simple and lightweight like vnstat (https://humdi.net/vnstat/). Source: almost 3 years ago