nethogs VS termshark

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

https://github.com/raboof/nethogs potrebbe fare al caso?

Nethogs!

I use nethogs

Check out https://github.com/raboof/nethogs.

Nethogs or atop with the netatop kernel module.

Ngrep is ok, I just use nethogs, nmap and tcpick, and tcpdump with termshark for most network analysis

Hello command-line colleagues - termshark v2.3 is now up on github. Termshark is a terminal user-interface for tshark that copies the look of Wireshark in 80x32. For this release, I've added configurable columns and a way to transfer the open capture file using magic-wormhole. Termshark can be convenient but for any non-trivial analysis, you need to get the pcap open in Wireshark. If you tend to ssh from within tmux, you can pair termshark with the tmux-wormhole plugin to make things even easier. Here's a demo: https://termshark.io/wormhole-demo. Here's the website: https://termshark.io; and here are the binaries + docs: https://github.com/gcla/termshark. Hope you find it useful :-)