Nethogs VS darkstat

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

I have a Ubiquiti Ethenret and WiFi network and their software will give me the discovery capabilities, and my custom OpenBSD router gives me the traffic inspection features (using Darkstat). Source: about 2 years ago

A friend of mine is a tech wizard, and he hooked me up with a home built router that uses pfSense, which comes with a program that does what you're asking for - darkstat. Source: about 3 years ago

I do have darkstat monitoring traffic on my egress interface. I also block access to UDP port 53 from untrusted hosts (I will change it to silently redirect to my official unbound DNS servers later). Source: about 3 years ago