Nethogs VS wavemon

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

Wavemon is a Linux wireless-network monitoring tool for watching signal and noise levels, packet statistics, device configuration and network parameters. The ncurses-based application is designed to work with all devices supported by the Linux kernel. Appreciation for the suggestion goes to sliddis. Source: over 1 year ago

Yeah, I'd be interested in seeing just what something like wavemon says about the signal strength. Source: about 2 years ago