GitHub - soarpenguin/nethogs: nethogs from http://nethogs.sf.net

Branches Tags

Name		Name	Last commit message	Last commit date
Latest commit History 11 Commits
debian		debian
.gitignore		.gitignore
Changelog		Changelog
DESIGN		DESIGN
INSTALL		INSTALL
Makefile		Makefile
README		README
README.decpcap.txt		README.decpcap.txt
connection.cpp		connection.cpp
connection.h		connection.h
conninode.cpp		conninode.cpp
conninode.h		conninode.h
cui.cpp		cui.cpp
cui.h		cui.h
decpcap.c		decpcap.c
decpcap.h		decpcap.h
decpcap_test.cpp		decpcap_test.cpp
devices.cpp		devices.cpp
devices.h		devices.h
inode2prog.cpp		inode2prog.cpp
inode2prog.h		inode2prog.h
nethogs.8		nethogs.8
nethogs.cpp		nethogs.cpp
nethogs.h		nethogs.h
packet.cpp		packet.cpp
packet.h		packet.h
process.cpp		process.cpp
process.h		process.h
refresh.cpp		refresh.cpp
refresh.h		refresh.h

Repository files navigation

= NETHOGS =

http://nethogs.sf.net

== INTRODUCTION ==

NetHogs is a small 'net top' tool. Instead of breaking the traffic down per protocol or per subnet, like most tools do, it groups bandwidth by process. NetHogs does not rely on a special kernel module to be loaded. If there's suddenly a lot of network traffic, you can fire up NetHogs and immediately see which PID is causing this. This makes it easy to indentify programs that have gone wild and are suddenly taking up your bandwidth.

Since NetHogs heavily relies on /proc, it currently runs on Linux only. 

== STATUS ==

Ideas/ToDo for new releases:

* Only IPv4 TCP is currently supported
* Sort the output by other values than network usage
* Monitor specific processes
* Make it work correctly on machines with multiple IP addresses
* Integrate into another tool?? 

== LICENSE ==

GPL.